Developer
For the product only you run.
Most support questions in a software business are about your own product, and your own product is not on any integration list. A documented API and a few events usually close that gap in an afternoon.
What connects
A scoped REST API over cases, customers, knowledge and health, plus webhooks for the events worth reacting to.
What crosses the boundary
- Read: cases, their state, customers, knowledge articles and health, within the token's scope.
- Events: case created, case resolved, incident declared, promise due, health changed.
- Write: create a case, add a message, attach context to an existing case.
- Never exposed: sensitive-marked cases are excluded from the API regardless of scope.
What this lets you do
- Raise a case automatically when your product detects a failure for a customer.
- Attach product state to a case so the agent does not have to ask.
- Trigger your own workflow when an incident is declared.
- Export cases and resolutions into your own reporting.
Setting it up
- 1Create a token and choose its scopes — narrow, ideally one per integration.
- 2Subscribe only to the events you need.
- 3Verify the signature on delivered events.
- 4Test against a sandbox organization before production.
Permissions
Scoped tokens, narrowest first. Cases marked sensitive are not reachable through the API under any scope — there is no token that returns them.
What you can ask once this is connected
- “Raise a case when our product detects this error.”
- “Export this month's resolutions.”
- “Notify our system when an incident is declared.”
Where it stops
The API creates and reads; it does not approve, refund, or send customer-facing replies on your behalf. An automated integration replying to a customer unattended is exactly what this product is built to avoid.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]