Skip to main content
POST
Create Note
Use the Cobalt appointment_id. The appointment_id parameter should be the Cobalt appointment ID returned from API responses or GET endpoints, not the EHR appointment ID.

Formatting Note Content

When providing the note content, it’s important to use \n for line breaks if you want those line breaks to be reflected in the EMR. For example, if you want the note to appear in the EMR as:
You should send the following in the note field:

Note Content Formats

The note parameter accepts two different formats depending on your EMR integration:
  1. String format (default): A single text string with \n line breaks
  2. Structured object format (eClinicalWorks): An object with separate fields for clinical documentation, along with optional ICD-10 and CPT codes

Example Request (String Format)

Example Request (Structured Format for eClinicalWorks)

Example Response

Webhook Notifications

When the note processing is complete, we will send a webhook to your registered endpoint. Here are examples of what those webhook payloads will look like: See the Webhook Events reference for the full field breakdown and error codes.

Success

Failure

Authorizations

client_id
string
header
required
client_secret
string
header
required
access_token
string
header
required

Body

application/json
appointment_id
string
required

The id of the appointment. This is the id included in the response to GET /appointments.

note
required

The data for the note. Can be either a string or structured object depending on EMR integration.

icd_10_codes
string[]

Optional ICD-10 diagnosis codes (only used with structured note format)

cpt_codes
string[]

Optional CPT procedure codes (only used with structured note format)

Response

200 - application/json

Successful response

success
boolean
message
string