Skip to main content
POST
Create a note

Authorizations

x-arms-api-key
string
header
required
x-arms-assume-user
string
header
required

Headers

Carrier
string
required

Carrier ID the request is scoped to. Notes are isolated per carrier.

Body

application/json
content
string

Markdown body. Embed @-mentions as inline reference tokens of the form <<ref:{entity_type}:{entity_id}:{display_text}>> and pass a matching entry in references for each one.

Example:

entity_id
string

Entity ID as a string. UUID for shipment/work_order/etc., or a stringified int64 for equipment/waybill/invoice/charge.

entity_type
string

Entity type to attach the note to. Must be a registered type (e.g. shipment, equipment, waybill, work_order, invoice, charge).

references
object[]

Sidecar reference rows for every <<ref:...>> token in content. Used for reverse-lookup queries and stale-entity detection. Maximum 100 references per note. Use SearchReferences to look up the entity_type/entity_id/display_text triples to insert here.

Example for the content above:

uploads
object[]

Reserved for future inline upload support; currently a no-op. Use UploadNoteAttachment after the note is created to attach files.

Response

A successful response.

note
object

A single note in a thread. Threaded notes are anchored to an (entity_type, entity_id) pair and ordered by created_at.