API
Send conversations in, and read the scores back out. Two surfaces, one key format.
Everything is on one host. Writes live under /ingest, reads under /v1, and both take the same Authorization: Bearer header.
Send conversations in
Three ways, and you only need one. Most people use a platform webhook, because it needs no code at all.
Webhook endpointPaste one URL into your platform. No key and no code.Send eventsPOST conversations from a stack of your own.Backfill historyUpload an export so a score has history behind it.Event payload referenceThe shape to send. Required fields, accepted fields, and what happens to the rest.
Read results back out
Seven read endpoints, all GET, for pulling our verdicts into your own warehouse or dashboard.
ConversationsList conversations, and open one with its turns and evidence.Scores and findingsThe number, and which rule broke on which turn.MetricsBucketed readings, so you can chart quality beside your own numbers.
Before you start
AuthenticationThe two scopes, what each reaches, and how to revoke a key.ConnectionsWhat a connection carries, and why an API key cannot create one.Errors and status codesEvery status both surfaces return, and what each one means.
The read surface is deliberately narrow: conversations, metrics, findings and scores. Nothing else is reachable with a key, and nothing else is documented.
Read next
- Authentication and API keys · The two scopes, what each one reaches, and how to replace a key.
- Webhook endpoint · The one URL a platform posts finished conversations to.
- Send events · POST finished conversations from a stack of your own.