Record Conversion
API Reference
Record Conversion
Records the outcome of a conversation for analytics and conversion tracking. The session_id must match the value used when calling /v1/next-questions. The Idempotency-Key header is required — replaying the same key for the same conversation is a no-op, making the call safe to retry.
POST
Record Conversion
Authorizations
Pass your NBQ API key in the Authorization header: Bearer nbq_live_xxx
Headers
A client-generated unique key (UUID recommended). Safe to retry with the same key.
Path Parameters
The session ID used when calling /v1/next-questions.
Body
application/json