REST API
RevDesk API
Connect RevDesk calls, messaging, phone numbers, contacts, tasks, usage, and webhooks to the rest of your revenue workflow with the public v1 REST API and OpenAPI 3.1 contract.
What it is
The RevDesk API is the direct integration surface for software and agents that need typed, organization-scoped access to RevDesk. The public OpenAPI 3.1 document describes paths, request and response schemas, security requirements, operation identifiers, rate-limit conventions, and deprecation signals. Use the official TypeScript SDK when you want generated types and common retry or pagination behavior, or call the JSON API directly from any language.
When to use RevDesk API
- Create an integration that manages RevDesk contacts, phone numbers, calls, messages, tasks, or usage.
- Generate a typed client or agent tool from a stable OpenAPI contract.
- Automate an operation that is not exposed by the smaller RevDesk MCP tool set.
Recommended workflow
- 1Inspect the OpenAPI operation and its required scope.
- 2Start with the zero-auth synthetic sandbox, then create a separate least-privilege organization key.
- 3Use idempotency keys where supported, honor rate-limit responses, and prefer webhooks for long-running outcomes.
Safety and approval boundaries
- Public schema discovery does not expose organization data.
- Calls, messages, purchases, configuration changes, and other external effects require authenticated permission and user approval.
- Production telephony reaches real carrier networks; use approved destinations and explicit spend limits while testing.
