Skip to content

API reference

Webhook events

What NezerCare sends to your endpoints.

Events NezerCare sends to your endpoints. Add an endpoint in the dashboard under Integrations → Notifications; its signing secret is shown once. An endpoint is a POST address of your own: https on a public DNS name (not an IP address, localhost or a .local name), up to 10 for a workspace.

Verify x-nezer-signature against the raw request bytes before parsing JSON. Compute the lowercase hexadecimal HMAC-SHA256 of <x-nezer-timestamp>.<raw-body> (the timestamp is in seconds since the epoch) using the endpoint signing secret and compare it to the value after v1= using a constant-time comparison. Reject a timestamp more than five minutes from now, and deduplicate by x-nezer-event-id.

Delivery. Each request carries content-type: application/json, user-agent: NezerHealth-Webhooks/1.0 and the headers listed on each event. Answer with any 2xx within 5 seconds, once the event is stored durably: any other status, a redirect (NezerCare doesn't follow redirects), a connection failure or no answer in time fails the attempt. A failed delivery is retried after 2, 4, 8 … seconds, doubling up to about 17 minutes, and stops after 12 attempts (about 51 minutes after the first); a team member can send it again from the dashboard. Every retry reuses the event's x-nezer-event-id and is signed afresh, with a new timestamp. An address that gives no answer in time on 10 attempts in a row, over at least 10 minutes, is paused: nothing more is sent to it until someone in the dashboard presses Resume, and what waited is sent then. An endpoint can also be set to send an Authorization header (bearer or basic) or a header of your choosing with each request.

Workflow calls to your own systems (Destinations) are signed too, with your workspace's widget signing secret: x-nezer-signature is the HMAC-SHA256 of <x-nezer-timestamp>.<METHOD> <path and query>\n<raw body>. order_lookup.requested below is the order lookup contract an "Order status and tracking" workflow holds your order system to, and patient_search.requested is the patients_v1 call @Nezer makes to find who a group message in Slack is for, signed the same way.

The event catalog is the clinical-case events, the two portal conversation events, patient.deleted and two account events, billing.usage_threshold_reached and subscription.updated, sent to every endpoint subscribed to them. billing.usage_threshold_reached is sent once each as use reaches 80%, 95% and 100% of the month's credits, with unit: "credits", threshold, creditsUsed, monthlyCredits, remaining and paused (an older plan with a monthly active-patient limit sends unit: "active_patients", activePatients and activePatientLimit instead). Subscription updates carry status (trialing, active, past_due, grace_period, restricted, canceled or enterprise), plan, reason, recovered and invoicePastDue; grace expiry uses reason PAYMENT_GRACE_PERIOD_EXPIRED, and a paid invoice that follows a failed payment carries recovered: true (a first or ordinary monthly charge has false). An Enterprise subscription invoiced by NezerCare reports enterprise, with invoicePastDue: true while an invoice is overdue: the plan's own, or the invoice for a credit top-up (an update is sent when a top-up invoice becomes overdue, and when it's paid or voided after that). Clinical event bodies may contain protected health information and must not be written to ordinary logs.

Until the organization signs its BAA, every event that is about patients (the clinical-case events, the portal conversation events and patient.deleted) is held (not dropped, and no attempt is used) and goes out once it's signed. billing.usage_threshold_reached and subscription.updated are about your account and carry no patient data, so they're never held for the BAA.

order_lookup.requested

POSTto your endpoint

Sent by an active "Order status and tracking" workflow when a signed-in patient asks where their order is (English or Spanish), to your connection's address + the step's path (POST /orders/lookup in the template). Never sent for an anonymous visitor, a health question or an emergency, and never contains what the patient typed. One attempt; NezerCare waits up to 5 seconds (less if the connection says so). Answer 200 with an orders array, empty when there are none. Anything else (a status that isn't 2xx, a redirect, which isn't followed, no answer in time, or an answer that breaks the contract) makes the workflow say it couldn't check and offer the team; nothing is guessed.

Verify x-nezer-signature with your workspace's widget signing secret: the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<METHOD> <path and query>\n<raw body>, compared after v1= in constant time. Reject a timestamp more than five minutes from now.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-timestampRequiredheader · stringUnix seconds.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1=<hex HMAC-SHA256 of timestamp + '.' + METHOD + ' ' + path and query + '\n' + raw body>, keyed with the widget signing secret.Matches ^v1=[a-f0-9]{64}$.
x-nezer-testheader · stringPresent on calls for a made-up test patient while NezerCare sets your workspace up (its test run). Don't change real orders or accounts for such a call; answer as you would in a test or sandbox.One of true.

Payload

FieldTypeDescription
versionRequiredintegerOne of 1.
typeRequiredstringOne of order_lookup.requested.
requestIdRequiredstringThe workflow run's id; the same for every call in one run.
patientRequiredobject
patient.externalIdRequiredstringExample: test-patient-1.
Example payload
{
  "version": 1,
  "type": "order_lookup.requested",
  "requestId": "0f2c9a4e-3d7b-4c1e-9a55-000000000000",
  "patient": {
    "externalId": "test-patient-1"
  }
}

Your response

StatusMeaning
200The patient's orders (latest first, or with placedAt on each). At most three are shown.

200 body

FieldTypeDescription
ordersRequiredarray of objectsUp to 50 items.
orders[].idRequiredstringYour order number, as the patient knows it. A string (not a number).1–64 characters.
orders[].statusRequiredstringOne of processing, shipped, delivered, delayed, cancelled.
orders[].statusLabelstring or nullShown instead of the widget's own word for the status, as written. An empty string makes the whole answer invalid: leave the field out, or send null, when there is none.1–80 characters.
orders[].carrierstring or nullAn empty string makes the whole answer invalid: leave the field out, or send null, when there is none.1–60 characters.
orders[].trackingUrlstring or nullShown as a Track package link only when it's https (and has no user name or password); otherwise dropped.1–2000 characters.
orders[].estimatedDeliverystring or nullYYYY-MM-DD, or an ISO 8601 date-time with a time zone.
orders[].placedAtstring or nullYYYY-MM-DD or ISO 8601. When every order has it, the widget sorts latest first; otherwise it keeps your order.
orders[].itemsarray of objects or nullUp to 20 items.
orders[].items[].nameRequiredstring1–120 characters.
orders[].items[].quantityRequiredinteger1 to 999.
200: Orders found
{
  "orders": [
    {
      "id": "TEST-1003",
      "status": "shipped",
      "statusLabel": "On its way",
      "carrier": "UPS",
      "trackingUrl": "https://www.ups.com/track?tracknum=1Z0000000000000000",
      "estimatedDelivery": "2026-10-02",
      "placedAt": "2026-09-25T15:04:00Z",
      "items": [
        {
          "name": "Test Product A",
          "quantity": 1
        }
      ]
    },
    {
      "id": "TEST-1001",
      "status": "delivered",
      "carrier": "USPS",
      "placedAt": "2026-08-28T12:00:00Z"
    }
  ]
}
200: No orders for this patient
{
  "orders": []
}

patient_search.requested

POSTto your endpoint

Sent when a teammate asks @Nezer in your Slack channel to message a group of patients described in words ("everyone whose UPS order shipped from Dallas last week"), and to test a search from the staff app, to your connection's address + the search's path. It carries only the filters your search declares, as checked by NezerCare: choice values you set up, dates (YYYY-MM-DD), date ranges (both days included, at most 93 days, within 366 days back and 92 days ahead of today in the clinic's time zone) and codes. Never patient data, and never anything a teammate typed. One attempt per page; NezerCare waits up to 5 seconds, reads at most 4 pages, and stops once it has more than 50 different patients' IDs (one message's limit). Answer 200 with the patients' IDs. Anything else (a status that isn't 2xx, a redirect, which isn't followed, no answer in time, or an answer that breaks the contract) makes @Nezer say it couldn't search; nothing is sent to anyone.

Every call is signed: a search can't be tested or turned on until the workspace has a widget signing secret. Verify x-nezer-signature with that widget signing secret, exactly as for a workflow call: the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<METHOD> <path and query>\n<raw body>, compared after v1= in constant time. Reject a timestamp more than five minutes from now.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-timestampRequiredheader · stringUnix seconds.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1=<hex HMAC-SHA256 of timestamp + '.' + METHOD + ' ' + path and query + '\n' + raw body>, keyed with the widget signing secret.Matches ^v1=[a-f0-9]{64}$.
x-nezer-testheader · stringPresent on a test from the staff app (and NezerCare setup's). Answer as you would for real: the test shows the counts and how many of your IDs are patients in Nezer.One of true.

Payload

FieldTypeDescription
versionRequiredintegerOne of 1.
typeRequiredstringOne of patient_search.requested.
requestIdRequiredstring (uuid)The same for every page of one search.
searchKeyRequiredstringWhich of your searches this is, as set up in the staff app.Matches ^[a-z][a-z0-9_]{1,39}$.
filtersRequiredobjectBy filter key. A filter that isn't required may be absent.
limitRequiredintegerSend at most this many patients per page.One of 50.
cursorRequiredstring or nullYour previous page's nextCursor; null for the first page.Up to 500 characters.
Example payload
{
  "version": 1,
  "type": "patient_search.requested",
  "requestId": "0f2c9a4e-3d7b-4c1e-9a55-000000000000",
  "searchKey": "orders_shipped",
  "filters": {
    "carrier": "ups",
    "warehouse": "dallas",
    "shippedOn": {
      "from": "2026-09-28",
      "to": "2026-10-04"
    }
  },
  "limit": 50,
  "cursor": null
}

Your response

StatusMeaning
200The patients found: their IDs only, a total, and a cursor for the next page.

200 body

FieldTypeDescription
patientsRequiredarray of objectsUp to 50 items.
patients[].idRequiredstringThe patient's ID in your system (their external patient ID), with no spaces.1–80 characters.Matches ^[\p{L}\p{N}][\p{L}\p{N}._:@+/#-]{0,79}$.
totalRequiredintegerHow many patients match in all, at least the number sent. When NezerCare stops before the last page it's the number shown: over 50, @Nezer asks the team to narrow the search. Once every page is read, NezerCare counts the distinct IDs instead, so a patient sent twice (one per order) counts once.0 to 1000000.
nextCursorstring or nullPresent when there's another page; NezerCare sends it back as cursor.Up to 500 characters.
200: Patients found
{
  "patients": [
    {
      "id": "TEST-1001"
    },
    {
      "id": "TEST-1002"
    }
  ],
  "total": 2,
  "nextCursor": null
}
200: More on the next page
{
  "patients": [
    {
      "id": "TEST-1001"
    }
  ],
  "total": 63,
  "nextCursor": "page-2"
}
200: No one found
{
  "patients": [],
  "total": 0
}

conversation.message_created

POSTto your endpoint

One message was added to a portal conversation: the patient's own, NezerCare's reply (an answer, a hand-off, a notice, an emergency notice) or the care team's.

Sent to the endpoint you subscribed in Integrations, Notifications, signed and retried like every other event (return 2xx after durable receipt; verify the raw-body signature and deduplicate by x-nezer-event-id and by the message's id). The body holds patient messages: keep it out of ordinary application logs. Until the organization has signed its BAA these wait, and go out once it signs.

Webhooks are for speed; the feed is the truth. Delivery is at least once, in parallel, with no promised order, and a delivery gives up after 12 attempts. Apply messages by sequence, not by arrival. When a message's sequence is more than one above the last you have, or when a conversation opens, read GET /v1/patients/{patientId}/conversations/{conversationId}/messages?afterSequence=<the last you have> and apply what it returns.

Internal notes, resolution notes and everything staff-only are never in an event. A patient's own messages and NezerCare's replies to them are sent too (tagged with causedByRequestId), so a second device or tab sees them: drop the ones you already have.

An `emergency` message must be shown at once, in full, in these words, like the one in the response of the call that caused it. The webhook is never the only way you hear of it: the response to the patient's call carries it first.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways conversation.message_created.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject
data.conversationIdRequiredstring (uuid)
data.externalConversationIdRequiredstring or nullYour own ID for the conversation, if you sent one.
data.patientIdRequiredstring (uuid)
data.externalPatientIdRequiredstring or nullYour own ID for the patient, as you sent it to identify.
data.sequenceRequiredintegerThe message's position in the conversation. Apply messages by this, not by arrival.At least 1.
data.messageRequiredobjectOne message of a conversation. text is always the words to show; the rest depends on kind.
data.conversationRequiredobjectThe conversation as it stands when the event is sent, which can be newer than the message.
data.conversation.statusRequiredstringOne of open, closed.
data.conversation.careStatusRequiredobject
data.conversation.careStatus.codeRequiredstringOne of received, in_progress, replied, scheduled, closed.
data.conversation.careStatus.labelRequiredstring
data.conversation.showCall911Requiredboolean
data.conversation.versionRequiredintegerAt least 1.
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
answerIdRequiredstring (uuid)
sourcesRequiredarray of objectsWhere the answer came from. Show them.
sources[].titleRequiredstring
sources[].urlRequiredstring (uri) or null
actionsRequiredarray of objectsAt most a Book button, with an https address on the clinic's site. Never a contact button for a signed-in patient.
actions[].kindRequiredstringOne of book.
actions[].urlRequiredstring (uri)
actions[].labelstringOne of demo, appointment, consultation, call.
choicesRequiredarray of objectsThe buttons under the answer: send the id as choiceId.
choices[].idRequiredstringOne of helpful, talk_to_team.
choices[].labelRequiredstring
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
purposeRequiredstringOne of safety_check, intake, team_chat, workflow.
inputRequiredobjectchoice: pick one of choices. text: answer in words (up to maxLength). attachments: add photos with the attachments call, then press done (or skip).
input.typeRequiredstringOne of choice, text, attachments.
input.maxLengthintegerExample: 2000.
input.choicesarray of objects
input.choices[].idRequiredstringSend it as choiceId.One of helpful, talk_to_team, yes, no, unsure, send, send_now, done, skip.
input.choices[].labelRequiredstringThe words on the button, in the message's language.
choicesarray of objectsShortcuts beside the question: send_now ("Send to my care team now", for an urgent concern, at any point) or done and skip for photos.
choices[].idRequiredstringSend it as choiceId.One of helpful, talk_to_team, yes, no, unsure, send, send_now, done, skip.
choices[].labelRequiredstringThe words on the button, in the message's language.
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
statusRequiredstringOne of ready, urgent.
summaryRequiredstring
choicesRequiredarray of objects
choices[].idRequiredstringSend it as choiceId.One of helpful, talk_to_team, yes, no, unsure, send, send_now, done, skip.
choices[].labelRequiredstringThe words on the button, in the message's language.
inputRequiredobject
input.typestringOne of text.
input.maxLengthinteger
input.hintstringExample: Need to change something?.
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
ordersRequiredarray of objects
orders[].idRequiredstring
orders[].statusRequiredstringOne of processing, shipped, delivered, delayed, cancelled.
orders[].statusLabelstring or null
orders[].carrierstring or null
orders[].trackingUrlstring (uri) or null
orders[].estimatedDeliverystring or null
orders[].placedAtstring or null
orders[].itemsRequiredarray of objects
orders[].items[].nameRequiredstring
orders[].items[].quantityRequiredinteger
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
emergencyRequiredobject
emergency.linesRequiredarray of objectsThe ways to call. Thoughts of self-harm add 988.
emergency.lines[].labelRequiredstringExample: Call 911.
emergency.lines[].telRequiredstringExample: tel:911.
emergency.sentToCareTeamRequiredbooleanWhether it reached the care team (an emergency case, or the clinical conversation). false means NezerCare could not file it yet and keeps trying until it does; the notice is shown either way, in the same words.
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
handoffRequiredobject
handoff.referenceRequiredstringSomething the patient and the team can both quote.Matches ^NC-[0-9A-F]{8}$.
handoff.teamRequiredstringOne of clinical, billing, scheduling, fulfillment, support.
handoff.urgencyRequiredstringOne of routine, urgent.
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
noticeRequiredobject
notice.codeRequiredstringOne of paused.
FieldTypeDescription
idRequiredstring (uuid)For the patient's own message, the requestId they sent.
sequenceRequiredintegerPosition in the conversation: 1, 2, 3 with no gaps. Order by this.At least 1.
kindRequiredstringOne of text, answer, question, review, emergency, handoff, notice, orders, closed.
fromRequiredobject
from.kindRequiredstringnezer is the assistant and NezerCare's fixed notices; care_team is a person on the clinic's team, or the clinic's own system posting a reply.One of patient, nezer, care_team, system.
from.labelRequiredstringThe words to show: "You", "NezerCare", "Care team" (Spanish "Usted", "NezerCare", "Equipo médico"). Staff names are never sent.
priorityRequiredstringOne of normal, emergency.
languageRequiredstringThe language of text.One of en, es.
textRequiredstringAlways present: the words to show. A portal that renders nothing else can print text and stay correct. Never rewrite it.
causedByRequestIdstring (uuid)The patient request this message answers, when it answers one.
attachmentsarray of objectsOn a patient's message: the files they listed with it, as metadata (never the contents).
attachments[].idRequiredstring (uuid)
attachments[].fileNameRequiredstring
attachments[].contentTypeRequiredstringOne of image/jpeg, image/png, image/webp, image/heic, application/pdf.
attachments[].sizeBytesRequiredinteger
createdAtRequiredstring (date-time)
closedRequiredobject
closed.reasonRequiredstringOne of closed.
The care team replied
{
  "id": "5f0c1d7e-3a5b-4c6d-9e8f-0a1b2c3d4e5f",
  "type": "conversation.message_created",
  "createdAt": "2026-10-18T16:21:45.000Z",
  "data": {
    "conversationId": "4a1c8e90-2b7d-4f36-9c05-7d3e1a6b8f12",
    "externalConversationId": "portal-thread-991",
    "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
    "externalPatientId": "pt_48213",
    "sequence": 3,
    "message": {
      "id": "e5f6a7b8-c9d0-4e1f-8a3b-4c5d6e7f8091",
      "sequence": 3,
      "kind": "text",
      "from": {
        "kind": "care_team",
        "label": "Care team"
      },
      "priority": "normal",
      "language": "en",
      "text": "Please keep the spot clean and dry. A nurse will call you today.",
      "createdAt": "2026-10-18T16:21:44.000Z"
    },
    "conversation": {
      "status": "open",
      "careStatus": {
        "code": "replied",
        "label": "New reply from your care team"
      },
      "showCall911": false,
      "version": 7
    }
  }
}
An emergency notice
{
  "id": "5f0c1d7e-3a5b-4c6d-9e8f-0a1b2c3d4e5f",
  "type": "conversation.message_created",
  "createdAt": "2026-10-18T16:21:45.000Z",
  "data": {
    "conversationId": "4a1c8e90-2b7d-4f36-9c05-7d3e1a6b8f12",
    "externalConversationId": "portal-thread-991",
    "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
    "externalPatientId": "pt_48213",
    "sequence": 2,
    "message": {
      "id": "d4e5f6a7-b8c9-4d0e-9f2a-3b4c5d6e7f80",
      "sequence": 2,
      "kind": "emergency",
      "from": {
        "kind": "nezer",
        "label": "NezerCare"
      },
      "priority": "emergency",
      "language": "en",
      "text": "Call 911 now. What you described can need emergency care. Do not wait for your care team to reply.",
      "emergency": {
        "lines": [
          {
            "label": "Call 911",
            "tel": "tel:911"
          }
        ],
        "sentToCareTeam": true
      },
      "causedByRequestId": "9d1f7a52-3c6e-4b85-8f0a-5b2c1d7e9a30",
      "createdAt": "2026-10-18T15:09:30.000Z"
    },
    "conversation": {
      "status": "open",
      "careStatus": {
        "code": "received",
        "label": "Received"
      },
      "showCall911": true,
      "version": 7
    }
  }
}
The conversation closed
{
  "id": "5f0c1d7e-3a5b-4c6d-9e8f-0a1b2c3d4e5f",
  "type": "conversation.message_created",
  "createdAt": "2026-10-18T16:21:45.000Z",
  "data": {
    "conversationId": "4a1c8e90-2b7d-4f36-9c05-7d3e1a6b8f12",
    "externalConversationId": "portal-thread-991",
    "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
    "externalPatientId": "pt_48213",
    "sequence": 4,
    "message": {
      "id": "f6a7b8c9-d0e1-4f2a-9b4c-5d6e7f809102",
      "sequence": 4,
      "kind": "closed",
      "from": {
        "kind": "nezer",
        "label": "NezerCare"
      },
      "priority": "normal",
      "language": "en",
      "text": "Closed",
      "closed": {
        "reason": "closed"
      },
      "createdAt": "2026-10-18T17:02:00.000Z"
    },
    "conversation": {
      "status": "closed",
      "careStatus": {
        "code": "closed",
        "label": "Closed"
      },
      "showCall911": false,
      "version": 9
    }
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

conversation.updated

POSTto your endpoint

A portal conversation's state changed with no message to carry the change: its status, careStatus (a teammate acknowledged the case: "Your care team is on it"), appointment (booked, moved or cancelled), showCall911 or what it is awaiting. The body is the conversation as GET /v1/patients/{patientId}/conversations/{conversationId} returns it, except that appointment has only scheduledFor: a webhook never carries the visit link. A change that comes with a message arrives in that message's conversation.message_created instead, though one can still follow a message's event right away with the same version (applying it again changes nothing). Compare conversation.version with the one you hold and keep the higher.

Sent to the endpoint you subscribed in Integrations, Notifications, signed and retried like every other event (return 2xx after durable receipt; verify the raw-body signature and deduplicate by x-nezer-event-id and by the message's id). The body holds patient messages: keep it out of ordinary application logs. Until the organization has signed its BAA these wait, and go out once it signs.

Webhooks are for speed; the feed is the truth. Delivery is at least once, in parallel, with no promised order, and a delivery gives up after 12 attempts. Apply messages by sequence, not by arrival. When a message's sequence is more than one above the last you have, or when a conversation opens, read GET /v1/patients/{patientId}/conversations/{conversationId}/messages?afterSequence=<the last you have> and apply what it returns.

Internal notes, resolution notes and everything staff-only are never in an event. A patient's own messages and NezerCare's replies to them are sent too (tagged with causedByRequestId), so a second device or tab sees them: drop the ones you already have.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways conversation.updated.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject
data.conversationIdRequiredstring (uuid)
data.externalConversationIdRequiredstring or nullYour own ID for the conversation, if you sent one.
data.patientIdRequiredstring (uuid)
data.externalPatientIdRequiredstring or nullYour own ID for the patient, as you sent it to identify.
data.conversationRequiredobject
data.conversation.idRequiredstring (uuid)
data.conversation.patientIdRequiredstring (uuid)
data.conversation.externalConversationIdstring or null
data.conversation.channelRequiredstringOne of portal_api.
data.conversation.statusRequiredstringOne of open, closed.
data.conversation.careStatusRequiredobjectWhere the conversation stands, in the widget's own words only.
data.conversation.careStatus.codeRequiredstringOne of received, in_progress, replied, scheduled, closed.
data.conversation.careStatus.labelRequiredstringExample: New reply from your care team.
data.conversation.appointmentRequiredobjectThe appointment of the case this conversation is linked to, for your portal to show its patient, or null. It is there from booking until an hour after the start, and not once the case is closed or the appointment cancelled. In a response it carries visitUrl, the link that opens the visit; a webhook's `appointment` never does: read the conversation for it. The link lets whoever has it join the visit: show it to this patient only, and don't log it or put it in a URL. How an appointment is booked is in the Clinical cases operation updateClinicalCase.
data.conversation.showCall911RequiredbooleanTrue while an emergency conversation is open: keep the 911 guidance in view.
data.conversation.awaitingRequiredobjectA hint for the composer, never a lock: free text is always accepted.
data.conversation.awaiting.typeRequiredstringWhat the latest message from NezerCare waits for: one of its buttons, words (with choices as shortcuts, if any), or photos (then done or skip).One of none, choice, text, attachments.
data.conversation.awaiting.messageIdstring (uuid)
data.conversation.awaiting.choicesarray of strings
data.conversation.lastSequenceRequiredintegerAt least 0.
data.conversation.versionRequiredintegerIncreases whenever the conversation changes.At least 1.
data.conversation.languageRequiredstringOne of en, es.
data.conversation.safetyRequiredobjectThe exact approved 911 line to print at all times where a patient can write or read messages, and the ways to call. Use these words rather than your own.
data.conversation.safety.languageRequiredstringOne of en, es.
data.conversation.safety.emergencyLineRequiredstringExample: If this is a medical emergency, call 911..
data.conversation.safety.linesRequiredarray of objects
data.conversation.safety.lines[].labelRequiredstringExample: Call 911.
data.conversation.safety.lines[].telRequiredstringExample: tel:911.
data.conversation.createdAtRequiredstring (date-time)
data.conversation.updatedAtRequiredstring (date-time)
FieldTypeDescription
scheduledForRequiredstring (date-time)The start, in UTC (show it in the patient's own time zone).
visitUrlstring (uri) or nullThe link to join the visit; null for an appointment booked before links were required; absent in a webhook.
Example payload
{
  "id": "5f0c1d7e-3a5b-4c6d-9e8f-0a1b2c3d4e5f",
  "type": "conversation.updated",
  "createdAt": "2026-10-18T16:21:45.000Z",
  "data": {
    "conversationId": "4a1c8e90-2b7d-4f36-9c05-7d3e1a6b8f12",
    "externalConversationId": "portal-thread-991",
    "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
    "externalPatientId": "pt_48213",
    "conversation": {
      "id": "4a1c8e90-2b7d-4f36-9c05-7d3e1a6b8f12",
      "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
      "externalConversationId": "portal-thread-991",
      "channel": "portal_api",
      "status": "open",
      "careStatus": {
        "code": "in_progress",
        "label": "Your care team is on it"
      },
      "appointment": null,
      "showCall911": false,
      "awaiting": {
        "type": "none"
      },
      "lastSequence": 2,
      "version": 4,
      "language": "en",
      "safety": {
        "language": "en",
        "emergencyLine": "If this is a medical emergency, call 911.",
        "lines": [
          {
            "label": "Call 911",
            "tel": "tel:911"
          }
        ]
      },
      "createdAt": "2026-10-18T15:02:11.000Z",
      "updatedAt": "2026-10-18T15:02:13.000Z"
    }
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

clinical_case.opened

POSTto your endpoint

Return 2xx after durable receipt. Verify the raw-body signature and deduplicate by x-nezer-event-id before creating or associating a provider workflow. The handoff paths are the API's own paths and start with /api/v1/...; on https://api.nezercare.com call them without the /api (/v1/clinical-cases/{caseId}/updates). No API key is sent in the webhook. data.intake holds the questions NezerCare asked the patient and their answers, so your system gets them with the case (the escalation to a Destination carries the same). One emergency is one event: a further emergency from the same patient within 15 minutes of an unresolved emergency case is added to that case and arrives as clinical_case.patient_message_created, not as a second clinical_case.opened.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways clinical_case.opened.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject
data.caseIdRequiredstring (uuid)
data.checkInIdstring (uuid)The ID of the record the case was opened from. The name dates from check-ins, which NezerCare no longer sends; follow the case by caseId.
data.patientIdRequiredstring (uuid)
data.priorityRequiredstringemergency when NezerCare's emergency rule, or one of your extra emergency phrases, matched what the patient wrote in the widget, including a reply in a case or conversation they already had (it opens a new emergency case for the patient, unless the patient already has an unresolved emergency case from the last 15 minutes: then the message is added to that case and delivered as clinical_case.patient_message_created, with no second clinical_case.opened). routine when the only red flags asked for a routine follow-up (for example, a medicine that isn't working). urgent also when a patient wrote about their health in a reply in a thread that isn't a health one (an order, a bill, a booking): nothing triaged it, so it is filed for urgent review, with their words as the case's first message. A staff_slack case is urgent, or emergency when the teammate's request used NezerCare's emergency words.One of emergency, urgent, routine.
data.sourcestringWhere the case came from: patient_concern, a concern a signed-in patient raised in the widget (or the emergency case opened for an emergency in a reply they sent in an existing thread, or the case opened for a health detail they wrote in a reply in an order, billing or booking thread, which never goes to your Slack), or staff_slack, a clinical request a teammate made of @Nezer in your Slack channel. A staff_slack case is raised by staff, not reported by the patient: patientNotes is empty and the teammate's words stay in NezerCare as an internal note on the case.One of patient_concern, staff_slack.
data.patientNotesstring or nullWhat the patient wrote. Empty for a staff_slack case.
data.symptomScoresobjectAlways {}. Kept so receivers written when NezerCare sent check-ins keep working.
data.matchedRulesarray of stringsEvery red flag that matched, not only the worst: ai_intake:<concern key> for the Health concern the patient's words matched, deterministic_safety:<rule> when one of NezerCare's own safety rules matched them, health_concerns_phrase when one of the extra emergency phrases on your Health concerns matched (the rule names no phrase and holds no patient text), configured_safety_question when an answer to one of your safety questions asked for an urgent review, emergency_terms:<kind> for NezerCare's emergency words in a teammate's request, and staff_request:slack on every case raised from Slack.
data.healthConcernsobject or nullFor a concern the patient raised in the widget: the version of your workspace's Health concerns it was triaged on. Version 0 is the NezerCare defaults, which run until a clinician on your team approves your own. null otherwise.
data.healthConcerns.versionintegerAt least 0.
data.healthConcerns.labelstring
data.statusstringThe case's status when the event was built: open for a new case. Your processed and other updates don't change it; only a team member acknowledging or resolving it in NezerCare, or a resolved update, does.One of open, acknowledged, resolved.
data.resolutionOutcomestring or nullNull until the case is resolved.
data.resolutionNotestring or nullNull until the case is resolved.
data.dispositionstringWhat the triage decided, in the older vocabulary: emergency, clinical_escalation or self_care. priority is the field to read.One of emergency, clinical_escalation, self_care.
data.submittedAtstring (date-time)When the concern the case was opened from was recorded.
data.intakeobjectThe intake the patient went through before their concern became a case: the questions NezerCare asked and the patient's answers, in the order they were asked, so your system has what the care team sees in the conversation. Only what the patient saw and replied to: the words of your approved questions and safety checks as they read them, and what they sent back. Never the guide's summary or notes, the care team's messages or internal notes, another conversation, or anything after the case opened: a retry or a later event sends the same intake. For an emergency it holds what was asked before the emergency, if anything. It can hold protected health information: keep it out of ordinary logs. A case with no intake behind it (one a teammate raised from Slack, or one opened before October 24, 2026) has language: null and no questions.
data.intake.languageRequiredstring or nullThe language of the questions and answers: the language the patient used the widget in. null when NezerCare has no record of an intake for the case.One of en, es, null.
data.intake.questionsRequiredarray of objectsUp to 50 items.
data.intake.questions[].kindRequiredstringfollow_up: one of your concern type's approved questions, or the closing "anything else" line. safety: one of its safety checks, a question with Yes, No and Not sure buttons.One of follow_up, safety.
data.intake.questions[].questionRequiredstringThe question as the patient read it, in their language.Up to 600 characters.
data.intake.questions[].answerRequiredstring or nullWhat the patient replied, as they sent it: the button's label on a safety check ("Yes", "No", "Sí"), or their own words. null when the case was sent before they answered this question (they sent it early, or NezerCare filed an urgent case for them after ten minutes without a reply). An answer longer than 1,000 characters is cut and ends with … [truncated]; the whole reply stays in the case's conversation in NezerCare.Up to 1000 characters.
data.intake.questions[].choicestringOnly on a safety check the patient answered with its Yes, No or Not sure button: which one, whatever the language. Left out when they typed an answer instead.One of yes, no, unsure.
data.intake.omittedQuestionsRequiredintegerHow many questions beyond the first 50 were left out. 0 in practice: an intake asks far fewer.At least 0.
data.handoffRequiredobjectWhere to report back. The paths are the API's own and start with /api/v1/...: on https://api.nezercare.com call them without the /api. No API key is in the webhook.
data.handoff.caseIdstring (uuid)
data.handoff.progressPathstringGET: read the case's progress.
data.handoff.updatesPathstringPOST: report progress.
data.handoff.messagesPathstringPOST: write to the patient.
data.handoff.firstStatusstringThe first update must have this status.Always processed.
data.handoff.firstSequenceintegerThe first update must have this sequence.Always 1.
data.handoff.transportReceiptIsClinicalAcceptancebooleanAlways false: a 2xx answer to this event confirms transport only.Always false.
A concern raised in the widget, triaged on your Health concerns
{
  "id": "5f0c1d7e-3a5b-4c6d-9e8f-0a1b2c3d4e5f",
  "type": "clinical_case.opened",
  "createdAt": "2026-10-11T14:05:00.000Z",
  "data": {
    "caseId": "8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d",
    "checkInId": "1b2c3d4e-5f60-4a7b-8c9d-0e1f2a3b4c5d",
    "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
    "priority": "urgent",
    "status": "open",
    "resolutionOutcome": null,
    "resolutionNote": null,
    "disposition": "clinical_escalation",
    "source": "patient_concern",
    "patientNotes": "Injection site reaction\n\nThere's a reddish spot where I injected and it's spreading.",
    "intake": {
      "language": "en",
      "questions": [
        {
          "kind": "safety",
          "question": "Is the redness spreading quickly, or do you have a fever?",
          "answer": "No",
          "choice": "no"
        },
        {
          "kind": "follow_up",
          "question": "When did you first notice it?",
          "answer": "Two days ago, the evening after my Sunday dose."
        },
        {
          "kind": "follow_up",
          "question": "Is it getting better, worse or staying the same?",
          "answer": "Worse. It's about the size of a coin now and warm to the touch."
        }
      ],
      "omittedQuestions": 0
    },
    "symptomScores": {},
    "matchedRules": [
      "ai_intake:injection_site_reaction"
    ],
    "healthConcerns": {
      "version": 3,
      "label": "Health concerns v3"
    },
    "submittedAt": "2026-10-11T14:05:00.000Z",
    "handoff": {
      "caseId": "8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d",
      "updatesPath": "/api/v1/clinical-cases/8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d/updates",
      "progressPath": "/api/v1/clinical-cases/8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d/progress",
      "messagesPath": "/api/v1/clinical-cases/8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d/messages",
      "firstStatus": "processed",
      "firstSequence": 1,
      "transportReceiptIsClinicalAcceptance": false
    }
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

Escalation to a Destination

POSTto your endpoint

The other way a case reaches your system. When a concern type in your Health concerns has a Destination ("Also send to"), NezerCare also sends each case of that type, as it opens, to that Destination's address: a POST of the JSON below, authenticated with the credentials you set on the Destination (a bearer token, basic credentials or your API-key header; with "API key in request body" your key is instead an extra top-level apiKey field of the JSON, never a header). It is not signed: there is no x-nezer-signature or timestamp, and the Destination's own credentials are what it proves itself with. caseId and handoff are how your system reports back on the case, as for clinical_case.opened; intake is the same as there. Verify the credentials you set, deduplicate on the Idempotency-Key (the case's submission ID, checkInId: a retry sends the same payload with the same key) and return 2xx after durable receipt. A 2xx is a receipt only, never a clinician's acceptance. A network error, a timeout, 408, 429 or 5xx is retried, up to eight attempts with a wait that doubles up to an hour; any other answer fails the send, and redirects are not followed. It can hold protected health information: keep it out of ordinary logs. A test patient's case is never sent.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
Idempotency-KeyRequiredheader · string (uuid)The case's submission ID, the same as checkInId. A retry reuses it: deduplicate on it.
X-Nezer-Submission-IdRequiredheader · string (uuid)NezerCare's ID for this send. The same on every attempt.

Payload

FieldTypeDescription
patientIdRequiredstring (uuid)
checkInIdRequiredstring (uuid)The submission's ID, the same as the Idempotency-Key. The name dates from check-ins; follow the case by caseId.
caseIdstring (uuid)The case's own ID, for the calls below. Absent from an escalation queued before October 24, 2026.
dispositionRequiredstringThe older vocabulary; priority is the field to read.One of emergency, clinical_escalation, self_care.
matchedRulesRequiredarray of stringsEvery red flag that matched, as on clinical_case.opened.
notesRequiredstringWhat the patient wrote: the concern type's name, a blank line and their first message. The same as patientNotes on clinical_case.opened.
intakeobjectThe intake the patient went through before their concern became a case: the questions NezerCare asked and the patient's answers, in the order they were asked, so your system has what the care team sees in the conversation. Only what the patient saw and replied to: the words of your approved questions and safety checks as they read them, and what they sent back. Never the guide's summary or notes, the care team's messages or internal notes, another conversation, or anything after the case opened: a retry or a later event sends the same intake. For an emergency it holds what was asked before the emergency, if anything. It can hold protected health information: keep it out of ordinary logs. A case with no intake behind it (one a teammate raised from Slack, or one opened before October 24, 2026) has language: null and no questions.
intake.languageRequiredstring or nullThe language of the questions and answers: the language the patient used the widget in. null when NezerCare has no record of an intake for the case.One of en, es, null.
intake.questionsRequiredarray of objectsUp to 50 items.
intake.questions[].kindRequiredstringfollow_up: one of your concern type's approved questions, or the closing "anything else" line. safety: one of its safety checks, a question with Yes, No and Not sure buttons.One of follow_up, safety.
intake.questions[].questionRequiredstringThe question as the patient read it, in their language.Up to 600 characters.
intake.questions[].answerRequiredstring or nullWhat the patient replied, as they sent it: the button's label on a safety check ("Yes", "No", "Sí"), or their own words. null when the case was sent before they answered this question (they sent it early, or NezerCare filed an urgent case for them after ten minutes without a reply). An answer longer than 1,000 characters is cut and ends with … [truncated]; the whole reply stays in the case's conversation in NezerCare.Up to 1000 characters.
intake.questions[].choicestringOnly on a safety check the patient answered with its Yes, No or Not sure button: which one, whatever the language. Left out when they typed an answer instead.One of yes, no, unsure.
intake.omittedQuestionsRequiredintegerHow many questions beyond the first 50 were left out. 0 in practice: an intake asks far fewer.At least 0.
priorityRequiredstringOne of emergency, urgent, routine.
handoffobjectWhere to report back. The paths are the API's own and start with /api/v1/...: on https://api.nezercare.com call them without the /api. No API key is in the webhook.
handoff.caseIdstring (uuid)
handoff.progressPathstringGET: read the case's progress.
handoff.updatesPathstringPOST: report progress.
handoff.messagesPathstringPOST: write to the patient.
handoff.firstStatusstringThe first update must have this status.Always processed.
handoff.firstSequenceintegerThe first update must have this sequence.Always 1.
handoff.transportReceiptIsClinicalAcceptancebooleanAlways false: a 2xx answer to this event confirms transport only.Always false.
apiKeystringOnly when the Destination's authentication is "API key in request body": the key you saved on the Destination, added to every send (and retry) as this top-level field in place of a header. Absent for every other authentication. It is your own credential: verify it and keep it out of ordinary logs.
A concern raised in the widget, sent to your Destination
{
  "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
  "checkInId": "1b2c3d4e-5f60-4a7b-8c9d-0e1f2a3b4c5d",
  "caseId": "8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d",
  "disposition": "clinical_escalation",
  "matchedRules": [
    "ai_intake:injection_site_reaction"
  ],
  "notes": "Injection site reaction\n\nThere's a reddish spot where I injected and it's spreading.",
  "intake": {
    "language": "en",
    "questions": [
      {
        "kind": "safety",
        "question": "Is the redness spreading quickly, or do you have a fever?",
        "answer": "No",
        "choice": "no"
      },
      {
        "kind": "follow_up",
        "question": "When did you first notice it?",
        "answer": "Two days ago, the evening after my Sunday dose."
      },
      {
        "kind": "follow_up",
        "question": "Is it getting better, worse or staying the same?",
        "answer": "Worse. It's about the size of a coin now and warm to the touch."
      }
    ],
    "omittedQuestions": 0
  },
  "priority": "urgent",
  "handoff": {
    "caseId": "8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d",
    "updatesPath": "/api/v1/clinical-cases/8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d/updates",
    "progressPath": "/api/v1/clinical-cases/8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d/progress",
    "messagesPath": "/api/v1/clinical-cases/8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d/messages",
    "firstStatus": "processed",
    "firstSequence": 1,
    "transportReceiptIsClinicalAcceptance": false
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; the retries above follow anything else.

clinical_case.patient_message_created

POSTto your endpoint

Contains patient-authored clinical content. Verify, deduplicate, and route it without placing the body in ordinary application logs. It is also how a patient's further emergency message arrives: within 15 minutes of an unresolved emergency case for the same patient it is added to that case, with this event on that case's caseId and no second clinical_case.opened. Do not treat it as a new emergency case.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways clinical_case.patient_message_created.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject
data.caseIdRequiredstring (uuid)
data.messageIdRequiredstring (uuid)
data.patientIdRequiredstring (uuid)
data.senderstringAlways patient.
data.messageRequiredstring
data.sentAtRequiredstring (date-time)
data.replyPathstringPOST: where to answer, the case's messages path (/api/v1/clinical-cases/{caseId}/messages; leave the /api off on https://api.nezercare.com).
Example payload
{
  "id": "ec6bf514-a01d-4406-8b76-6b1bb841617a",
  "type": "clinical_case.patient_message_created",
  "createdAt": "2026-10-21T04:34:54.527Z",
  "data": {
    "caseId": "8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d",
    "messageId": "154d8b33-fb89-494f-b61b-705dc800dbcc",
    "patientId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
    "sender": "patient",
    "message": "The redness has spread since this morning.",
    "sentAt": "2026-10-21T04:34:54.527Z",
    "replyPath": "/api/v1/clinical-cases/8a7b6c5d-4e3f-4a2b-9c1d-0e9f8a7b6c5d/messages"
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

clinical_case.acknowledged

POSTto your endpoint

Sent when a team member acknowledges the case in NezerCare. It isn't the same as your processed case update. The body is the same as clinical_case.opened, with the case's status.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringOne of clinical_case.acknowledged, clinical_case.resolved.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobjectThe same body as clinical_case.opened (patient notes, the intake's questions and answers, matched rules, handoff and the rest), with the case's status now. It can hold protected health information.
data.caseIdRequiredstring (uuid)
data.patientIdRequiredstring (uuid)
data.statusRequiredstringThe case's status when the event was built: normally acknowledged for clinical_case.acknowledged and resolved for clinical_case.resolved, but a late delivery shows where the case is by then.One of open, acknowledged, resolved.
data.resolutionOutcomestring or nullSet on clinical_case.resolved; null otherwise.
data.resolutionNotestring or nullThe team member's note, set on clinical_case.resolved; null otherwise.

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

clinical_case.resolved

POSTto your endpoint

Sent when a team member resolves the case in NezerCare. A resolution your own system reports with a resolved case update does not send it (you already know). The body is the same as clinical_case.opened, with the case's status and its resolutionOutcome and resolutionNote. A late delivery can describe a case your integration has already processed; deduplicate by event ID.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringOne of clinical_case.acknowledged, clinical_case.resolved.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobjectThe same body as clinical_case.opened (patient notes, the intake's questions and answers, matched rules, handoff and the rest), with the case's status now. It can hold protected health information.
data.caseIdRequiredstring (uuid)
data.patientIdRequiredstring (uuid)
data.statusRequiredstringThe case's status when the event was built: normally acknowledged for clinical_case.acknowledged and resolved for clinical_case.resolved, but a late delivery shows where the case is by then.One of open, acknowledged, resolved.
data.resolutionOutcomestring or nullSet on clinical_case.resolved; null otherwise.
data.resolutionNotestring or nullThe team member's note, set on clinical_case.resolved; null otherwise.

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

patient.deleted

POSTto your endpoint

Emitted when the clinic deletes a patient's data in NezerCare (an owner or administrator, from the patient's page). Carries no health information: the patient's ID, the workspace ID (environmentId), a reason code and the time. Delete or close your copy of the record as your own policy requires; the patient's earlier events refer to IDs that no longer exist in NezerCare.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways patient.deleted.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject
data.patientIdRequiredstring (uuid)
data.environmentIdRequiredstring (uuid)
data.reasonstring or nullOne of patient_request, duplicate_record, entered_in_error, test_record, clinic_policy, null.
data.deletedAtRequiredstring (date-time)
Example payload
{
  "id": "9b1f2c3d-4e5f-4a6b-8c7d-0e1f2a3b4c5d",
  "type": "patient.deleted",
  "createdAt": "2026-10-01T15:04:05.000Z",
  "data": {
    "patientId": "6cb4ccfc-2f1e-4d3a-9b8c-7d6e5f4a3b2c",
    "environmentId": "1d2c3b4a-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
    "reason": "patient_request",
    "deletedAt": "2026-10-01T15:04:05.000Z"
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

billing.usage_threshold_reached

POSTto your endpoint

An account event: use reached 80%, 95% or 100% of the month's credits, sent once each per month. No patient data, and never held for the BAA. An organization still on an older plan with a monthly active-patient limit gets it at 80% and 100% of that limit, with unit: "active_patients".

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways billing.usage_threshold_reached.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject

data with unit credits

FieldTypeDescription
unitRequiredstringAlways credits.
thresholdRequiredintegerOne of 80, 95, 100.
creditsUsedRequiredinteger
monthlyCreditsRequiredinteger
remainingRequiredintegerCredits left, top-ups included.
pausedRequiredbooleanWhether Nezer's work that uses credits is paused when the event is sent.

data with unit active_patients

FieldTypeDescription
unitRequiredstringAlways active_patients.
thresholdRequiredintegerOne of 80, 100.
activePatientsRequiredinteger
activePatientLimitRequiredinteger
Example payload
{
  "id": "3f6c1b2a-8d4e-4f5a-9b6c-7d8e9f0a1b2c",
  "type": "billing.usage_threshold_reached",
  "createdAt": "2026-10-01T15:04:05.000Z",
  "data": {
    "unit": "credits",
    "threshold": 80,
    "creditsUsed": 2400,
    "monthlyCredits": 3000,
    "remaining": 600,
    "paused": false
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

subscription.updated

POSTto your endpoint

An account event: your subscription changed state (a payment, a failed payment, grace-period expiry, a cancellation, a first payment, or an Enterprise invoice paid or overdue). No patient data, and never held for the BAA.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways subscription.updated.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject
data.statusRequiredstringOne of trialing, active, past_due, grace_period, restricted, canceled, enterprise.
data.planRequiredstring or nullThe plan's code (for example starter, practice, growth or enterprise), or null when the change doesn't say.
data.reasonRequiredstring or nullOne of PAYMENT_GRACE_PERIOD_EXPIRED, null.
data.recoveredRequiredbooleanTrue only for a paid invoice that follows a failed payment.
data.invoicePastDueRequiredbooleanTrue while an Enterprise invoice is overdue: the plan's own or a credit top-up's.
Example payload
{
  "id": "7a8b9c0d-1e2f-4a3b-8c4d-5e6f7a8b9c0d",
  "type": "subscription.updated",
  "createdAt": "2026-10-01T15:04:05.000Z",
  "data": {
    "status": "restricted",
    "plan": null,
    "reason": "PAYMENT_GRACE_PERIOD_EXPIRED",
    "recovered": false,
    "invoicePastDue": false
  }
}

Your response

StatusMeaning
200Durably received. Any 2xx status counts; anything else is retried.

integration.test

POSTto your endpoint

Sent only when someone on your team presses Test connection beside your address in Integrations → Connection health. You can't subscribe to it. It is built and signed exactly like a real event: the same headers, the signature from this address's own signing secret, and the address's login (an Authorization or API-key header) when it has one, so a receiver that verifies the signature or the login sees what a delivery would show it. It says it is a test (data.test is true and the x-nezer-test header is true), carries no patient data and creates nothing in NezerCare. Answer with any 2xx and do nothing else with it; a 401 means your receiver didn't accept the signature or the login. It is sent once, never retried, to the public address only, and a redirect is not followed. Your team sees the answer's status in Connection health.

Signed by NezerCare. Check x-nezer-signature before you trust the body: Verify webhooks.

Headers

FieldTypeDescription
x-nezer-event-idRequiredheader · string (uuid)The event's ID, the same as the body's id. A retry of the delivery reuses it: deduplicate on it.
x-nezer-event-typeRequiredheader · stringThe event's name, such as clinical_case.opened.
x-nezer-timestampRequiredheader · stringWhen this attempt was signed, in seconds since the epoch. A retry is signed afresh.Matches ^[0-9]+$.
x-nezer-signatureRequiredheader · stringv1= and the lowercase hex HMAC-SHA256 of <x-nezer-timestamp>.<raw request body>, keyed with the endpoint's signing secret.Matches ^v1=[a-f0-9]{64}$.
idempotency-keyRequiredheader · string (uuid)The same value as x-nezer-event-id.
x-nezer-testRequiredheader · stringAlways true on this event, so a receiver can tell a test from a delivery.Always true.

Payload

FieldTypeDescription
idRequiredstring (uuid)The event's ID, the same as the x-nezer-event-id header. Deduplicate on it.
typeRequiredstringAlways integration.test.
createdAtRequiredstring (date-time)When NezerCare queued this delivery to your endpoint.
dataRequiredobject
data.testRequiredbooleanAlways true.
data.probeIdRequiredstring (uuid)This test's own ID, the same as the body's id and x-nezer-event-id.
data.environmentIdRequiredstring (uuid)
data.sentAtRequiredstring (date-time)
data.messageRequiredstring
Example payload
{
  "id": "0c9f6a41-2b7d-4e58-9a13-6f8d2c4b7e10",
  "type": "integration.test",
  "createdAt": "2026-10-24T14:05:00.000Z",
  "data": {
    "test": true,
    "probeId": "0c9f6a41-2b7d-4e58-9a13-6f8d2c4b7e10",
    "environmentId": "1d2c3b4a-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
    "sentAt": "2026-10-24T14:05:00.000Z",
    "message": "This is a test from NezerCare's Test connection. It carries no patient data. Answer with any 2xx and do nothing else with it."
  }
}

Your response

StatusMeaning
200Any 2xx status counts as reachable. Anything else is shown to your team as the answer your system gave.