SupportHub API and webhooks
The core of an operator's work is available through the API: creating tickets, replying to customers, working with contacts and files. Events arrive by webhook or through long polling, so SupportHub fits into your CRM, your billing system or a channel of your own.
POST /tickets — “Error 500 when paying for a plan”
We found the cause. Please try the payment again.
message.created → https://crm.example.com/hooks/supporthub
REST API
Tickets, messages, contacts, ticket history, ratings and files. Access works through tokens with permissions, which you can revoke and reissue.
Events: webhooks or long polling
Webhooks reach your URL right after an event, with a signature that's easy to verify and retries on errors. If you don't have a public address, you fetch events with a /updates request, like getUpdates for Telegram bots.
Python SDK
The official client, with typed models, request retries, sync and async modes and built-in long polling. For other languages there are examples in cURL and Node.
Your own channel
Through the API you can plug in any source of requests, such as a mobile app, your own messenger or a bot, and handle it in the same queue as Telegram or email.
How to connect
FAQ
Are there request limits?
Yes. Limits and error codes are described in the docs, along with the recommended retry strategy.
How do I check that a webhook came from SupportHub?
Every request is signed with a secret you get when you create the subscription.
See also
- BILLmanager
BILLmanager 6 tickets from ISPsystem, with replies, attachments, ratings and closing kept in sync.
- Email
Customer emails as tickets, with replies from your address over IMAP and SMTP.
- Telegram
A support bot with menus and buttons, answered by operators from a shared queue.
Connect your channels and try it on real conversations
The Starter plan is free, and you can try a paid plan for 14 days. Setup takes a few minutes.