Call Analysis API: Connect Any Phone System or CRM to AI Analysis
Any system that can send an HTTP request can send calls to TalkWiz: a phone system, a dialer, a CRM, your own code or an automation tool such as n8n, Make and Zapier. The analysis comes back to you through the API or a signed webhook, automatically after every call.
Updated
What you can connect
TalkWiz's direct connection is to CallMarker. Any other system connects through the open API:
- A phone system, dialer or CRM that can send an HTTP request when a call ends.
- No-code automation tools: n8n, Make and Zapier. Set up a step that sends the call to TalkWiz, without writing a line of code.
- Your own code, in any language.
No way to send calls automatically? You can also upload recordings and transcript files.
What the API does
- Send a call for analysis: a
POSTrequest to/api/v1/callswith the transcript and the call details. You can send one call or up to 100 calls per request. The response returns right away, and the analysis runs in the background. - Call details: the transcript is the only required field. You can add a call ID, time, duration, direction, agent, customer and phone, campaign and outcome. A new agent is created automatically, and Israeli numbers are converted to international format.
- No duplicates: sending again with the same
external_call_iddoes not create a duplicate call. - A recording instead of a transcript: register the recording, upload the file to a signed address returned by the API, and complete. TalkWiz transcribes in Hebrew, separates the agent from the customer and analyzes. Formats: mp3, m4a, mp4, wav, webm, ogg, flac, up to 25MB per file.
- Read results:
GET /api/v1/calls/{id}returns the call's state, andGET /api/v1/calls/{id}/analysisreturns the analysis.
All the fields, copy-ready examples and a full OpenAPI specification are in the API documentation.
The analysis comes back to you: a signed webhook
After a call is analyzed, TalkWiz can send the analysis to any address you choose, as JSON. The summary and outcome reach your CRM, monday.com through Make or Zapier, or any system that accepts a webhook.
- Choose what to send: a short summary, the call outcome, score, next steps, a suggested follow-up message, the status the agent marked versus the call, extracted data, objections and a link to the call in TalkWiz.
- Choose when: automatically after every analysis, or only with a click on the call page.
- Every request is signed in the
X-TalkWiz-Signatureheader: an HMAC-SHA256 of the request body with a signing key shown to you once. Your system knows the request really came from TalkWiz. - A delivery log shows what was sent, what failed and why, and a button sends the latest call as a test.
Setup, step by step
- Create an API key: an admin of your organization creates a key in settings, under "API keys". Keep it somewhere safe.
- Send a call: from your system, or from an HTTP step in n8n, Make or Zapier, send a
POSTto/api/v1/callswith theAuthorization: Bearerheader and the key. The example in the documentation works as is. - Check that the call arrived: it appears in the calls list, and shortly after, its analysis too.
- Send the analysis back (optional): in settings, under "Send data back", add a webhook with an https address, choose fields and when to send, and save the signing key. Send a test call and check in the log that it arrived.
What it costs in tokens
A token is one minute of analysis:
- A call sent as a transcript: one token per started minute of call.
- A call sent as a recording: 2 more tokens per minute for transcription, so 3 tokens a minute in total.
- A call with no real conversation, such as a hang-up right after answering: not analyzed and not charged for analysis.
- Sending the analysis back by webhook: no tokens.
Plans and prices are on the pricing page.
Privacy, security and limits
- API keys are created only by admins, shown once and stored only as a hash. You can create a new one at any time.
- Sensitive details such as credit card, ID and bank account numbers are hidden automatically before storage, and transcripts are stored encrypted.
- Your webhook details, the address and the signing key, are stored encrypted. TalkWiz sends only to public https addresses.
- Limits: up to 60 requests a minute per key, a request body up to 1MB and a transcript up to 200,000 characters.
Want to see what comes back from every call? Take a look at a sample analysis. The analysis powers call quality assurance and sales coaching, and if you have not chosen a connection yet, all the options are on the integrations page. For background on what the analysis checks, read the AI call analysis guide.
Frequently asked questions
Do you have a built-in connection to our phone system or dialer?
The only direct connection today is CallMarker. Any other system connects through the API, through an automation tool such as n8n, Make or Zapier, or by uploading recordings and files.
Do we need a developer to connect?
Not necessarily. In n8n, Make and Zapier you set up a step that sends an HTTP request to /api/v1/calls with the API key in the header. The documentation has a complete example you can copy.
What happens if the same call is sent twice?
If you send external_call_id, the call ID in your system, sending again with the same ID does not create a duplicate call.
Can we send a recording instead of a transcript?
Yes. You register the recording, upload the file to a signed address returned by the API, and complete. TalkWiz transcribes the recording, separates the agent from the customer and analyzes it like any call.
How do we know the webhook really came from TalkWiz?
Every request is signed in the X-TalkWiz-Signature header: an HMAC-SHA256 of the request body with a signing key shown to you once during setup. Your system computes the signature and compares.