Get every call into the tools you already use, with the Ajora API and webhooks

What is the difference between the API and webhooks?

A webhook pushes, an API pulls. With a webhook, Ajora sends you the summary on its own as soon as the call is done. With the API you ask for it yourself, whenever it suits you.

For most people the webhook is the one you want. You set it up once and after that it happens by itself. The API is there for looking back: pulling every call with a particular customer, say, or fetching an older summary again.

What can you actually do with it?

Everything you currently retype by hand after a call. The summary on the right customer in the CRM, the action items in your task list, a nudge in Slack when something important came up.

Do you need to be able to code for this?

Not necessarily. With Zapier or Make you click the integration together without a line of code: you paste the webhook address they give you into Ajora, then pick in Zapier or Make where it should go.

If you have a developer, or you are one, you work with the API and the webhooks directly. That saves a middleman and keeps your data in your own hands. The full technical reference is at debrief.ajora.io/docs/developer; below is what you need to decide whether it fits.

What exactly does Ajora send?

As soon as a debrief is ready, we send the details of the call and the content of the summary to the address you gave us. The transcript is never part of that; you fetch it separately through the API.

• The call itself: when, how long, which channel, and the phone numbers and names on both ends
• The title and the summary of the conversation
• The action items, as separate points
• The decisions that were made
• The sentiment of the conversation
• A direct link to the debrief in Ajora

What belongs in those notes and how they come about is in AI note taker for phone calls.

There are two moments at which we send something: debrief.completed when the summary is first ready, and debrief.updated when you edit it in Ajora afterwards. That keeps the note in your own system correct when you improve something later.

Setting up a webhook

1. 1

   Make sure you have an address to send to

   That is a web address that can receive messages from us. Using Zapier or Make, you get that address there with a copy button. Building it yourself, it is an endpoint on your own server. It has to be https.

2. 2

   Go to Settings → Developer

   In the Ajora dashboard at debrief.ajora.io you will find the section for webhooks and API keys there.

3. 3

   Create the webhook

   Paste the address, pick which events we may send on, and save. You then see a signing secret once, which lets you check that a message really comes from us. It starts with dbf_whsec_live_. Store it immediately, because we will not show it again.

4. 4

   Make a call and check it arrives

   Run a short test call. As soon as the debrief is ready, the message should come in at the address you gave. If nothing arrives, open the Delivery log on the webhook. It shows what your address sent back for each attempt.

Creating an API key

You use the API to fetch data yourself. You create the key in the same place, under Settings → Developer.

1. 1

   Create the key

   Give it a name that tells you later what it is for, for example the name of the system using it. You see the key once; it starts with dbf_live_. Put it straight into your password manager or your secrets.

2. 2

   Choose what the key may do

   By default a key may read your calls and debriefs and manage webhooks. Access to the word-for-word transcripts is a separate permission you add deliberately.

3. 3

   Use it on the back end only

   A key belongs in your server or your secrets manager, never in an app or a website where a visitor can pull it out of the code. And never in a Claude or ChatGPT chat window: the MCP connection is for that.

What you can fetch afterwards: your calls in a list, one specific call, the debrief for that call, and every call with a given phone number. That last one is the handiest in practice, because it pulls a customer’s entire history in one go. Every address starts with https://debrief.ajora.io/api, and you write the phone number in international format, so +31612345678.

What should you watch out for?

Three things: you see keys only once, transcripts are deliberately fenced off, and there is a limit of 120 calls per minute per key. You will not notice that last one in normal use.

• Per account you can have up to five active keys and ten webhooks. Enough for a few integrations side by side, and it keeps things tidy.
• A key or a signing secret is shown only at the moment you create it. Lost is lost: you then create a new one and replace the old.
• Transcripts sit behind a separate permission, because they contain literally what was said. The summary is enough for almost everything.
• The integration is part of a paid plan and does not work during the free trial.
• On Teams, an admin can create keys and webhooks that cover the whole team’s calls. Every team member can also create a key of their own for their own calls.

What happens to the data itself does not change: we delete the audio once it has been transcribed, within 24 hours at the latest, and your calls and debriefs are stored encrypted in Germany. Once you forward the summaries into your own system, your own agreements apply from that point on. More about this on security and in the data processing agreement.

Back to all articles