Using the API and Webhooks on a Trial Account
Your Click2Call trial includes the full API and webhooks, with no trial limits, from the day you sign up. This guide covers setting up a webhook, the events and fields it sends, how to check one fired, the usual reasons one does not arrive, and what to send support if you are still stuck.
Last reviewed: October 2026
Who this guide is for
Developers and businesses testing an integration during the 7-day free trial — a CRM hook, an automation in Zapier or Make, or your own app that reacts to calls. API and webhook configuration is self-service: Click2Call supports the platform and its documentation, but not your integration code.
What is available during the 7-day free trial?
The API and webhooks are fully featured during the trial, with no trial-specific limits. Everything is available from the moment the account is created:
- •API access — the full JSON REST API. See the full API documentation in the client portal.
- •Webhooks — every call state, including the
aianalysisevent that carries the transcript and AI call summary. - •$11 of trial credit — enough to activate one local number ($10) and make a few test calls. Inbound calls are free, so you can test incoming-call webhooks for the whole trial.
What the trial does not include: help configuring the API, webhooks or a third-party integration (configuration is self-service), and Microsoft Teams Direct Routing.
How do I set up a webhook?
Webhooks are set up in the client portal. The webhook documentation explains where to add your webhook URL, the payload format and every field. You can set a webhook on one number or across every number on the account.
Each webhook is an HTTP POST with Content-Type: application/json and your secret token in the Authorization header. You can change that header to a custom header name of your choosing.
Which webhook events can I receive?
Every webhook carries a state field that tells you what happened:
| Call direction | States |
|---|---|
| Received (incoming) | ringing, answered, ended, missed (an incoming call that was not picked up) |
| Dialed (outgoing) | ringing, answered, ended, and when the call does not connect: busy, invalid, rejected, notavailable, blocked, noanswer |
| AI analysis | aianalysis — the transcript and AI call summary are ready |
Fields worth knowing
| Field | What it is |
|---|---|
id | Unique identifier for this call. Use it to match a webhook to a call and to ignore duplicates. |
originid | The call this one came from. Same as id for the first call in a sequence; different for a transferred or forwarded leg. |
type | received (incoming) or dialed (outgoing). |
from, to | Calling and called numbers. |
start_time | UTC, YYYY-MM-DD HH:MM:SS. Sent only on ended or missed/failed events. |
duration | Call length in seconds. Sent only on a successful ended event. |
voiceuri | Link to the recording. Sent only on a successful ended event, and only when call recording is enabled. |
aiuri, transcript, callsummary | Sent only on the aianalysis event, and only when AI transcription is enabled. callsummary includes a short and full summary, categories, names mentioned and scores such as sentiment. |
How do I check whether a webhook fired?
Work from the call outward: first prove the call happened, then whether your endpoint received the event.
Make a test call you can identify
Call your Click2Call number from another phone and note the time, the number you called from and whether the call was answered. An answered call and a missed call produce different states, so decide which one you are testing.
Confirm the call reached your number
In the portal, open Account → Records and find the call by time and caller. If it is not there, the problem is the call, not the webhook — see the reasons below.
Check your endpoint's logs
Look for a POST at the time of the call. Your server's access log is the best evidence of delivery. Log the state and id of every webhook you receive so you can see exactly which events arrived.
Match events by call ID
All the events for one call share its id, so you can follow a call from ringing to ended, and to aianalysis afterwards. Build your receiver to tolerate the same event arriving more than once — skip any id and state pair you have already processed. For retry behaviour on failed deliveries, see the webhook documentation.
Still nothing? Ask us to check
If the call is in Records but your endpoint received nothing, contact support and we'll check for you whether the webhook was sent from our side.
Why didn't my webhook arrive?
Your endpoint is not reachable from the internet
Click2Call posts from the internet, so localhost, a private IP address, a machine behind a firewall or a development server that is switched off will never receive it. Use a public address, or a tunnelling tool while you develop. For endpoint requirements, see the full API documentation.
The URL is wrong, or set on a different number
Check for typos, http versus https, the path and a trailing slash. If the webhook is set on one number, calls to a different number — or to an extension — will not trigger it. Set it across all numbers while testing if you are unsure.
Your endpoint rejected it
If your receiver checks the Authorization header (or the custom header you chose), make sure it compares against the same secret token you set. Return a 2xx status quickly and do slow work afterwards; a receiver that times out looks like a failure.
No aianalysis event, transcript or recording link
The aianalysis event, with aiuri, transcript and callsummary, is sent only when AI transcription is enabled. voiceuri is sent only when call recording is enabled. Expect aianalysis a little after the call ends, not during it.
The trial credit has run out
Inbound calls are free, but outgoing calls use credit. Check the balance on the portal Summary page and see Adding Account Credit.
The account has gone past its $5 IOU limit
Every account can run a small negative balance — an IOU of up to $5. Once the balance goes past −$5, outgoing calls are blocked automatically, and anyone trying to call out hears a message that outgoing calls can't be made. A blocked call never connects, so it produces no answered or ended events. Topping up releases the block automatically.
The account is not active yet
New accounts are activated within 24 hours of signup, and identity verification usually takes a few hours. Until the account and number are active, test calls will not connect.
What should I send support if it still isn't working?
Email [email protected] with:
- •Your account number and the Click2Call number you called
- •The date and time of the test call (AEST), and the number you called from
- •The state you expected (for example
answered,missedoraianalysis) - •The call
idfrom any webhook that did arrive for that call - •Your endpoint URL — never your API token or the webhook secret
- •What your endpoint logged at that time: the status code it returned, or that it received nothing
Support can check whether Click2Call sent the event. Debugging your integration code is not included in support.
Still need help?
Our Australian support team is available to assist you.