Does Trace have an API for developers?

Trace has an API for sending data in, and one for erasing a visitor. It does not yet have a public API for reading your results or journeys.

What you can use today

• Send orders, refunds and events. Your server sends an order to POST /v1/event/purchase, a refund to POST /v1/event/refund and any other event to POST /v1/event. The address is https://app.usetrace.io/api-proxy. How server side tracking works in Trace explains what each route does, how an order joins a visitor’s journey and where consent applies.
• Erase a visitor. POST https://app.usetrace.io/api-proxy/sites/<siteId>/privacy/erase deletes everything Trace holds for one visitor on one site. Privacy erasure request (DSAR) API has the request and the response.

How you sign in to it

• The sending routes take your site’s tracking key in the x-trace-api-key header. It is the key in your tracking snippet. It is public, because it is in your page source, so it is used to send data and not to read your results. The routes are rate limited.
• The erasure route does not take the tracking key. It needs a signed in Trace session for a user who is an owner or admin of the site.

Reading your data

There is no public API for reading your journeys, conversions or reports yet. To ask about access, or to tell us what you would build with it, email support@usetrace.io.