Endpoints
Tranthor’s REST interface uses the same schema as Segment’s HTTP API./api/public/apps/identify/api/public/apps/track/api/public/apps/page/api/public/apps/screen/api/public/apps/batch, to send several of these in one request
Authentication
Tranthor’s REST API authenticates using Write Keys. Find yours in the dashboard at/dashboard/settings#write-key.
Include write keys as an HTTP Authorization: Basic <base64(secretId:secret)> header in your requests. Copy the full value,
including Basic , from the dashboard. It’s safe to include this write key in your client (e.g. your web client javascript payload).
For example, you can use the following to submit an identify request to our demo workspace:
Deduplication and backfills
messageIdis the idempotency key. An event whosemessageIdwas already received for the same user is discarded rather than stored a second time, for every call type, so a retry or a repeated sync is safe. The request is still accepted with204; the response carriesx-tranthor-deduplicated-eventswith the number of events discarded this way. Requests that discard nothing omit the header.- The deduplication window is 30 days, the same as Customer.io’s. A
messageIdreceived more than 30 days ago is treated as new: the event is stored again and, unless it is a backfill, can start its journeys again. Give a record that changes amessageIdthat carries its version, rather than relying on the window. - To replay historical events, for example a store’s history import, set
"backfill": trueon each event. A backfilled event is stored and deduplicated like any other and is visible to segments and analytics, but it never starts a journey. Events without the field are live events.
Limits
- A request body may be up to 1 MiB on the wire. Send
Content-Encoding: gzipto compress it; the decompressed body may be up to 5 MiB. /api/public/apps/batchaccepts at most 2500 items. A larger batch is rejected with413and a JSONmessage.- A single event may be up to 64 KB of JSON. Larger events are dropped and the rest of the request is accepted with
204. When a request drops events, the response carriesx-tranthor-dropped-eventswith the number discarded, so a204is never silent about data loss. Requests that drop nothing omit the header. - Requests over the rate limit get
429with aRetry-Afterheader (seconds). Retry after that delay.

