Developers
Written By Maruf Ansari
Last updated 12 days ago
The Developers module is where your agency connects Kickcall to your own systems. It has two sections: API Keys (for authenticating requests you make to Kickcall) and Webhook (for receiving real-time events from Kickcall on your own endpoints).
Open it from the left sidebar of the Agency Portal by clicking Developers.
API Keys (Coming Soon)
API keys authenticate your server-to-server requests to Kickcall. Use them when your platform needs to pull data from Kickcall or trigger actions programmatically.
Generate a key from the API Keys tab and store it securely on your side — treat it like a password.
Never expose a key in a browser, mobile app or public repository.
If a key is ever leaked, delete it and generate a new one. Requests using the old key stop working immediately.
Webhook
Webhooks push events from Kickcall to your endpoint the moment they happen — no polling required. Typical uses are syncing call outcomes into a CRM, updating a dashboard when an appointment is booked, or triggering an internal workflow when a call is missed.
The Webhook tab lists every destination you have configured, with its endpoint URL, the events it is subscribed to and when it was created. Use the copy icon to copy the full URL, the pencil to edit and the bin icon to delete a destination.
Creating a webhook
Go to Developers → Webhook and click Create Webhook.
Endpoint URL (required) — the HTTPS URL on your side that will receive the event payloads.
Destination Name (required) — a friendly label such as Acme CRM, so you can recognise it in the list and in logs.
Description — a short note explaining what this webhook is for.
Events — tick the events you want delivered. Events are grouped by category (Call, Contact, Appointment and more), and you can select an entire category with its group checkbox. The counter at the top right shows how many of the available events you have selected.
Click Create. The destination becomes active straight away and starts receiving matching events.
Webhook Logs
Switch to the Logs tab to see every delivery attempt Kickcall has made to your endpoints. Use the date range picker at the top right to narrow the period, and paginate through results with the records-per-page control.
Status — the HTTP response code your endpoint returned. Green (for example 201) means the delivery succeeded; red (for example 422) means your endpoint rejected or failed to process the payload.
Webhook — the destination name the event was sent to.
Event — which event triggered the delivery.
Attempts — how many times Kickcall tried to deliver this event. More than one attempt means earlier tries did not return a success response.
Action — the eye icon opens the delivery detail so you can inspect exactly what was sent and what came back.
Note: Logs are the fastest way to debug an integration. If your system is missing data, check here first — the status code tells you whether the problem is on Kickcall's side or in your endpoint.