Connect Rinkel to your CRM, helpdesk, Slack or a custom-built tool. With Rinkel's API and webhooks, your call data lands exactly where you need it — and a whole lot of manual work takes care of itself.
Good to know❗
The API and webhooks are available on Professional and Expert plans (webhooks were previously Expert-only — now available on Professional too). This is technical work: a developer or IT person will have it sorted in no time, but you can also work through it yourself if you don't mind rolling up your sleeves.
All technical documentation is at developers.rinkel.com (in English). Looking for inspiration? Check out the integrations page for real-world examples.
What is an API key and what do you need it for?
An API key is a unique code — similar to a password — that gives your system access to your Rinkel account data. No key, no access.
You create an API key in MyRinkel (here).
Please note ❗ Treat your API key like a password. Don't share it publicly and don't put it in code you push to a public repo.
Getting started with the Rinkel API
The API is REST-based and you'll find all endpoints, parameters and examples at developers.rinkel.com.
Working with webhooks
A webhook automatically sends a message to your system whenever something happens in Rinkel. For example: incoming call arrives? Open a ticket. Call ends? Update the customer record in your CRM.
Setting up a webhook
Go to this page in MyRinkel.
Choose the webhook you want to set up and enter your endpoint URL (it must be able to receive POST requests).
Which events can you use?
Incoming call — a call comes in (not yet answered). Sends id, datetime, to and from.
Outgoing call — you're making an outbound call (not yet answered). Same fields as above.
Call start — the call has been answered. Sends id, datetime, answeredBy and the call menu option selected, if any.
Call end — the call has finished. Sends id, datetime and cause (six possible reasons: unanswered, answered, blocked, voicemail, call queue, outside business hours).
Got AI Insights? You can also use the Call insights event to push summaries, sentiment and topics to your own system. Link it to a call using the same id.
Exact payload fields are available at developers.rinkel.com.
Security
All webhook traffic runs over HTTPS and the payload is JSON. On your side, only accept requests from the Rinkel domain.
Webhook not working?
Run through these checks:
Is your endpoint URL correct and reachable from the internet?
Does your endpoint accept POST requests?
Does your application return a 200 OK on receipt?
Are you allowing requests from the Rinkel domain?
Still stuck? Send the error message to [email protected]— we'll help you sort it out.
FAQs
Which plans support the API and webhooks?
Professional and Expert.
Can I push AI Insights to my CRM?
Yes, via the Call insights webhook event. Link it to other webhook events using the same call id if you also need phone numbers.
I want to see the caller's name live in my CRM during an incoming call — is that possible?
Yes. Use the incoming call webhook to push the data to your CRM the moment the call arrives.
Does Rinkel work with Zapier, Make or Integrately?
The direct Zapier integration has been discontinued. With webhooks, you can connect Rinkel yourself to any platform that receives webhooks—Zapier, Make and Integrately all work great.