Server Events Overview

in addition to client events, customers may send server events to chord these events will be processed by the chord cdp and forwarded onto connected destinations, just like client events server events provide an http endpoint for backend systems to send ad hoc events or webhooks the examples below show the data required for each event to be correctly processed by chord customers using shopify or chord oms have their server events automatically routed to chord cdp these documents are for customers using a non shopify/non chord oms or want to customize the data sent to chord endpoint the url to send server events to depends on the type of event being sent track https //production cdp ingest chord co/api/track identify https //production cdp ingest chord co/api/identify authorization requests sent to chord use an api key for authorization there are multiple options for providing the api key in the request customers may choose the version that is most compatible with their source system chord recommends that, where possible, customers use http header x write key writekey query parameter (note all characters are lowercase) writekey property in the request body (note the uppercase k ) chord recommends customers use the x write key header for authorization where possible automatic properties when an event is ingested, the properties below are added automatically to the payload there is no need for customers to include these values, however they can be overridden by equivalent properties in the request payload if required { , "timestamp" "2024 01 01t00 00 00 000z", "requestip" "2604 3d09 1180 1581 3c4a\ bc9d 8027\ a450", "context" { }, "receivedat" "2025 09 12t19 04 50 541z", "messageid" "0c43c13c 692b 46c6 9152 3962871b1009" } event types docid\ z57epqmjdr7cj3wq1jxdo