Build on top of Talvo with a REST API and outbound webhooks.
API keys
- Go to Settings → Developers → API keys and create a key.
- Copy it once — it is shown only at creation and stored as a hash.
- Authenticate with a bearer token:
Authorization: Bearer talvo_sk_your_key_here
See the dedicated article on managing API keys for rotation and revocation.
What you can do
- Create a conversation —
POST /v1/conversationswith an email and a message. Talvo creates or matches the contact, opens the conversation, applies your routing rules, and lets the AI agent answer, exactly as if the message had arrived through the messenger. - Set customer traits —
POST /v1/identify. - Record product events —
POST /v1/track. - Read back contacts, conversations and published help articles.
A key is scoped to the workspace that issued it and cannot reach another workspace's data.
Webhooks
Subscribe to events such as conversation.created, message.created and conversation.resolved. Talvo POSTs the event to your endpoint as it happens.
Shown with our demo workspace.
Every delivery is signed with an HMAC-SHA256 signature in the X-Talvo-Signature header — verify it before acting on the payload. See the article on verifying webhook signatures.
Deliveries are best-effort with a short timeout, and each attempt is logged in Settings → Developers with the response your endpoint returned. Return a 2xx quickly and do slow work asynchronously.
Practical notes
- Requests and responses are plain JSON.
- Make webhook handlers idempotent — treat a repeated event as a no-op.
- Never put a key in front-end code.
