DevelopersGet started

AssistCall API

The AssistCall API lets your own software work with your AI Employee: read the calls it answered, the messages it took and the appointments it booked, keep contacts and your knowledge base in sync, and manage webhooks. Resellers use one key to run all of their client accounts.

On this page

What you can build
Who it’s for
The basics
The API or webhooks?
Start here
Getting help

What you can build

Sync calls into your CRM. Pull each call's summary, transcript and caller, and attach them to the right customer.
Keep one calendar. Read the appointments your AI Employee books, and book, move or cancel appointments from your own scheduling system.
Work through messages. List the messages callers left and mark them resolved when someone has called back.
Keep answers up to date. Update the packages, prices and knowledge base articles your AI Employee quotes from.
Run client accounts as a reseller. Create clients from your own signup or billing system, change their package, suspend and resume them, and read each client's usage.

Who it’s for

You are	Your key reaches	Create it in
A business using AssistCall	Your own account: its calls, messages, appointments, contacts, forms, knowledge, AI Employees, usage and webhooks.	Your dashboard, on the Developers page
A reseller (partner)	Your partner account, your clients and packages, and any one client's data when you send the `AssistCall-Account` header.	The partner portal, on the API page

Keys are created by the account owner. See Quickstart to make one. To try the API on sample data first, ask us for read-only sandbox credentials.

Businesses that get AssistCall through a reseller don't have API keys of their own: their reseller reaches their data with its partner key. If that's you, ask your reseller.

The basics

Base URL

https://api.assistcall.ai/v1

HTTPS and JSON. Send JSON bodies with Content-Type: application/json; every response is JSON.
Bearer tokens. Exchange your key's client id and secret for a one-hour access token (OAuth 2.0 client credentials), then send Authorization: Bearer ac_at_…. See Authentication.
Scopes. Each key holds only the permissions you picked, like calls:read or appointments:write. See Scopes.
Lists return { data, has_more, next_cursor } and page with ?cursor=. See Pagination.
Errors share one shape with a type, a code, a readable message and a request_id. See Errors.
Times are ISO 8601 in UTC (2026-10-25T14:03:11Z) and phone numbers are E.164 (+12125550147).

The API or webhooks?

Use both. Webhooks tell your server the moment something happens: a call ends, a message is taken, an appointment is booked, moved or canceled, or a new caller is added. The API is for reading anything at any time and for making changes. A common pattern is to react to a webhook, then call the API for anything the event didn't include.

Start here

Quickstart Create a key, get a token and list your calls in five minutes.Sandbox Read-only sample data for a demo dental office and a demo reseller, on request.API reference Every endpoint, with examples and a live Try it console.Partner API One key for all your clients, with the AssistCall-Account header.

Getting help

Email [email protected]. If a request went wrong, include its Request-Id response header (it's also in every error body as request_id) so we can find it straight away. Never send your client secret or access tokens.