Platform

The CallWhiz AI API, SDK and webhooks

The CallWhiz AI API covers everything the console does, with bearer-token auth and a published OpenAPI description. Webhooks fire before a call to look the caller up and after it to file the result.

Updated 21 September 2026

In short: Everything the console does is an API call, and every call can push events to your systems.

Definitions

Webhook
An HTTP call CallWhiz AI makes to your systems: before a call, so you can look the caller up, and after it, so you can file the result.
Signed token
A short-lived credential the Web SDK uses for browser calling, restricted by a domain allow-list.
OpenAPI description
The published, machine-readable description of the API.

What it does

  • Create and manage agents, place calls and read call records programmatically.
  • Web SDK with signed tokens and domain allow-listing for browser calling.
  • Webhooks before a call (to look the caller up) and after it (to file the result).
  • Published OpenAPI description; bearer-token auth.

Related questions

Is there an API?

Everything the CallWhiz AI console does is an API call: create and manage agents, place calls and read call records programmatically. There is a Web SDK with signed tokens and domain allow-listing for browser calling, webhooks before a call (to look the caller up) and after it (to file the result), a published OpenAPI description and bearer-token auth.

Can the agent connect to my calendar, CRM or internal systems?

CallWhiz AI agents call your systems mid-conversation: booking against a calendar, looking up a customer, an order or a balance, creating or updating a CRM record while the call is still running, or calling any internal API you give the agent as an action. Sensitive actions can sit behind a read-back-and-confirm gate.

Put an agent on a number this afternoon.

Sign up, describe the job, attach a line, and pay per minute. No sales call, no platform fee, no seat licences, no minimum.