Call tracking API
Read your calls, leads and call reports from your own code, write back what happened on each call, and set up numbers, sources and workflows at scale.
Call tracking API
What is Nimbata's call tracking API?
Nimbata's call tracking API is a REST API at api.nimbata.com that gives your own code the same calls, leads, forms and reports you see in Nimbata, as JSON, with each call's source, campaign and AI summary, and lets you change them too.
Create a personal API token in your Nimbata profile and send it as a Bearer token. Start with GET /users/me for your organization's ID, then work with the data your user can reach: list calls by source, campaign, outcome or date, read a call's AI summary, transcription and recording, follow a lead from its first visit to its latest call, or set a call's value, rating and tags. Every operation, with its fields and a way to try it, is in the API reference. To have calls pushed to you as they happen instead, use webhooks; for no-code apps, Zapier.
From Nimbata
Into your code
- Calls
Caller, outcome and duration, Transcription and AI summary, Recording URL
- Leads
First and last source, Calls, forms and visits
- Reports
Trends and totals, Calls by source, Caller journeys
Lead timelineapi.nimbata.com · JSON
200 OKCall
- call_outcome
- Answered
- call_duration
- 00:04:12
Lead
- first_source
- first_campaign
- Brand_Search
Report
- trends
- Calls by day
In your code
Every call and lead, one request away
The API reference at developers.nimbata.com, with a lead's timeline open. Everything numbered is what your code gets.
Nimbata APIapi.nimbata.comv2.0
- GETList project calls2
- GETRead a call summary
- GETRead a transcription
- GETRead a lead timeline
- PUTSet a call's call value3
- PUTSet a call's rating
- POSTAdd tags to a call
- GETRead dashboard trends
Request
GET/orgs/{orgId}/projects/{projectId}/leads/{leadId}/timeline
Authorization: Bearer YOUR_API_TOKEN
Response 200 OK
{
"lead": {
"name": "Jordan Lee",
"phone": "+13125550148",
"first_source": "google",
1
"first_medium": "cpc",
"first_campaign": "Brand_Search",
"last_interaction_at": "2026-10-05T13:30:58Z"
},
"pages": [ … ],
"calls": [ … ],
"forms": [ … ]
}
1Leads
Every lead, with its source
Read a lead with its first and last source, medium and campaign, and the page visits, calls and forms behind it.
2Calls
Every call, in full
List calls by source, campaign, outcome, first-time caller or date, and read each one's transcription, AI summary and recording.
3Write back
Tell Nimbata what happened
Set a call's value, rating, tags, comments and custom fields from your own systems, so your reports and integrations use them.
What you can build with the API
More than two hundred operations across calls, leads, reports and setup. A few of the things you can build on them.
01Calls in your own reports
Pull calls into your warehouse or BI tool, filtered by source, campaign, outcome or date, a page at a time.
02What was said, as text
Read each call's transcription and AI summary, and a link to its recording, for your own review or AI tools.
03Outcomes from your CRM or back office
When a deal closes or a job is booked, set the call's value, rating and tags, and your reports and ad platform integrations use them.
04A lead's whole journey
Follow one lead from its first page visit to its latest call and form, with the source, medium and campaign it first came from and last came from.
How it works
Make your first request in three steps
A token, your organization's ID, then any call you want.
Create a token
In Nimbata, open My Profile, then API, then Personal Auth Tokens, and create a token. It acts with your user's permissions, and you can revoke it at any time.
1Connect
Find your organization
Call GET /users/me with your token. The org_id it returns goes in every organization and project URL.
2Find
Read and write your data
List calls, read leads and reports, or set a call's value and tags. Try each request in the API reference at developers.nimbata.com first, with sample data if your project is new.
3Build
Customers
Trusted by marketers who need better attribution
Teams use Nimbata to see which calls make money and to settle questions about lead quality.
50%More conversionsnovi.digital
“With Nimbata, we can see which phone calls make money and reinvest away from the ones that don’t.”
4.5xGrowthService24
“Before Nimbata, everything was manual CPC. Every day was a new battle. Now, the algorithm knows exactly which jobs bring more money.”
200+Phone conversions a monthSkyleads
“When clients question lead quality, I just play the call recording. No more debate.”
Everything you need to know about the Nimbata API
Does Nimbata have an API?
Yes. Nimbata's Web API is a REST API at https://api.nimbata.com that sends and takes JSON. Its reference, where you can try each request, is at developers.nimbata.com, and its OpenAPI document is at https://api.nimbata.com/openapi.json.
How do I authenticate?
Create a personal API token in Nimbata under My Profile, then API, then Personal Auth Tokens, and send it in the Authorization header as Bearer and the token. A request without valid credentials gets a 401. You can revoke a token at any time, and any tool using it loses access at once.
What can I do with the API?
Read and change most of what the Nimbata app shows. Calls (with their transcription, AI summary, recording, tags, value, rating and custom fields), leads and their timelines, forms and submissions, texts, call reports, tracking numbers and sources, call flows, tags, custom fields, workflows, webhooks, email and Slack alerts, and integration delivery logs.
Can I get each call's source and campaign?
Yes. List calls filtered by UTM source, medium or campaign, outcome, tracking number, first-time callers or date range, and read a lead with the first and last source, medium and campaign it came from.
Can I read call recordings and transcriptions?
Yes, with permission to the call's media. One request returns a signed URL for the recording, another the transcription, and another the conversation with its AI summary. Without that permission, transcript text comes back empty and no recording URL is included.
Can I send data back to Nimbata?
Yes. Set a call's value, rating, tags, comments, follow-up date, caller name and custom fields, so your CRM or back office can mark the calls that became sales. Values you set are what Nimbata's reports and integrations, such as Google Ads, use.
What permissions does a token have?
The same as the user who created it. Each operation in the reference names the permission it needs, so a token can only reach the organizations and projects, and do the things, its user can.
How do I start if my project has no calls yet?
Endpoints that support it return sample data when you add dummy=on, so you can build against realistic responses before your first call. Without it, they return your real data.
How does paging work?
Lists are paged with a cursor. Each page includes page.next, a relative URL that keeps your filters; follow it until it is null.
Still unsure? Talk to a human
Your calls, in your code.
Start a free trial, create a token and make your first request in minutes.
- 14-day free trial, no credit card
- Billed per answered call
- 24/7 expert support
- No long-term contracts