Creates a new threaded note on an entity (shipment, equipment, waybill, etc.). The caller’s verified identity (from JWT or assumed user) becomes the note author. Reference tokens (<<ref:type:id:displayText>>) embedded in content should also be supplied as structured references for reverse-lookup.
Documentation Index
Fetch the complete documentation index at: https://docs.cedarai.com/llms.txt
Use this file to discover all available pages before exploring further.
Carrier ID the request is scoped to. Notes are isolated per carrier.
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:
"Held at <<ref:equipment:54321:BNSF 54321>> waiting on clearance."Entity ID as a string. UUID for shipment/work_order/etc., or a
stringified int64 for equipment/waybill/invoice/charge.
Entity type to attach the note to. Must be a registered type (e.g.
shipment, equipment, waybill, work_order, invoice, charge).
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:
[
{ "entity_type": "equipment", "entity_id": "54321",
"display_text": "BNSF 54321" }
]Reserved for future inline upload support; currently a no-op. Use
UploadNoteAttachment after the note is created to attach files.
A successful response.
A single note in a thread. Threaded notes are anchored to an
(entity_type, entity_id) pair and ordered by created_at.