Deskwoot for API
Customer support API for custom integrations and channels
The Deskwoot customer support API exposes everything: conversations, contacts, messages, agents, tags, custom fields. Build custom channels, in-app chat, IoT alert routing, or full white-label support flows.
Most helpdesks treat the API as an afterthought, gated behind enterprise plans and missing the endpoints you actually need. Deskwoot's customer support API is included on every plan including the free tier.
REST + webhooks: every entity (conversations, contacts, messages, agents, tags, custom fields) has a full CRUD interface. Webhooks fire on every state change so your integration code stays event-driven instead of poll-based.
Authentication: OAuth 2.0 for end-user contexts (build a 'Sign in with Deskwoot' flow into your own app), static API tokens for service-to-service. Per-token scopes let you grant read-only or limited permissions to specific integrations.
Custom channels: tag every conversation with a custom 'source' identifier so you can route, filter, or report on it separately. Useful for in-app chat, IoT alert ingestion, or any non-standard channel that isn't covered by the built-in inboxes.
Common API-first customer support patterns we see: 1) In-app chat from a mobile app, where the SDK posts to the API directly, 2) Form-to-ticket workflows where a contact form on your site creates a Deskwoot ticket via webhook, 3) IoT device support where a Raspberry Pi or industrial sensor pings the API on error, 4) White-label support widgets where a SaaS resells Deskwoot under their brand.
What you get with API support
REST + Webhooks
Send messages in, get callbacks for replies. Both directions documented. Event-driven architecture out of the box.
Per-conversation source tagging
Tag every conversation with a custom source identifier so you can route or filter custom channels separately.
OAuth and API tokens
Use OAuth for end-user contexts or static API tokens for service-to-service. Per-token scopes for granular access.
SDK support
Official SDKs for Node.js, Python, and a JavaScript widget SDK for in-app chat. Community SDKs for Ruby, PHP, and Go.
Idempotency keys
Every write endpoint accepts an idempotency key so retries are safe. Critical for unreliable network conditions.
Setup takes minutes
Connect API in 3 steps. No code required.
- 1Get your API token from Settings → API.
- 2POST to /api/v1/conversations to create a conversation.
- 3Set up a webhook URL to receive replies.
API customer support FAQ
- What is the best customer support API for custom integrations?
- For custom-channel and white-label use cases, the customer support API needs: full CRUD on conversations and contacts, webhooks for events, OAuth and token auth, idempotency keys, and good docs. Deskwoot covers all of these. Zendesk and Intercom also have strong APIs but are typically gated behind premium plans.
- What is an API-first customer support software?
- API-first customer support software exposes its full feature set via the API, not just a subset. Every UI action (assigning tickets, sending messages, updating contacts) has a corresponding API endpoint. Deskwoot is API-first; the API came before the UI in our build process.
- Where are the customer support API docs?
- The full API reference is at /docs/api. SDKs for Node.js and Python are linked from there. OpenAPI spec is published for tools like Postman and Insomnia.
- How do I build a custom channel with the API?
- POST to /api/v1/conversations with your custom 'source' identifier. Set up a webhook to receive agent replies. Your custom channel (in-app chat, IoT, etc) sends and receives via your own integration code; Deskwoot handles inbox semantics, AI, SLA, and reporting.
- Are there rate limits on the customer support API?
- Yes. Default 1000 requests per minute per token. Higher limits available on paid plans or by request. 429 responses include Retry-After headers.
- Does the API support webhooks for every event?
- Yes. Conversation created, resolved, reopened, message received, contact updated, tag added, status changed. Webhook delivery is at-least-once with retries on 5xx responses.
- Can I use the API to migrate from another helpdesk?
- Yes. The bulk-import endpoint accepts contacts, conversations, and messages in one call. We have prebuilt migration scripts for Zendesk, Intercom, Help Scout, Front, and Chatwoot.