Resolve API and webhooks
Prebuilt integrations cover the common cases, and the API and webhooks cover everything else. They exist so your systems can create tickets in Resolve, read what Reva resolved, and react in realtime to the events that matter, with full precision and no polling.
What the API and webhooks do
- REST API to create and read tickets, resolutions, and knowledge base content programmatically.
- Webhooks that push events to your endpoint the moment they happen: ticket.created, resolution.sent, escalation.created, and kb.gap.logged.
- Realtime and precise, faster and more reliable than a no-code poll for high volume.
What you can build with Reva events
- Open a Resolve ticket automatically when your app detects a failure, so Reva can pick it up.
- Trigger downstream systems the instant Reva escalates, for example paging a specialist or logging to a data warehouse.
- Feed resolution and reopen data into your own analytics to track verified resolution over time.
One design principle runs through every integration: ground or refuse. Reva only acts on data it actually retrieved, business math is computed in code rather than written by the model, and anything risky, moving money, changing an account, an angry customer, routes to a human decision card instead of an autonomous action.
Every fire-and-forget endpoint on the Resolve side persists its outcome, so an event either lands or reports why it did not. You are not left guessing whether a webhook fired.
Setup, in plain language
- Generate an API key in Settings, then Integrations, under Developer.
- Register a webhook URL and pick the events you care about.
- Verify the signature on your endpoint and start receiving events.
A real use case
A SaaS company wants every escalated bug to reach their data warehouse and their on-call tool instantly. They subscribe to the escalation.created webhook, and on each event they write a row for analytics and page the on-call engineer. Reva keeps escalating bug tickets as designed, and the company's own systems react in realtime without polling an API.
Frequently asked
What events can I subscribe to?
The common ones are ticket.created, resolution.sent, escalation.created, and kb.gap.logged, so you can react to both resolutions and handoffs.
Is the API better than Zapier?
For high volume, realtime needs, or custom logic, yes. Zapier is best for quick no-code breadth, the API and webhooks for depth, speed, and reliability.
How do I know a webhook actually fired?
Resolve persists the outcome of every event-driven action, so deliveries are logged and failures are reported rather than silently dropped.