Developers

The LimeCall REST API, authentication, webhooks and limits.

LimeCall has two separate surfaces with two separate kinds of key. Mixing them up is the single most common integration mistake, so start here:

The widget key is already in your page source and is meant to be public. The secret key must never reach a browser. They are not interchangeable, and neither surface accepts the other's key.

Base URL

https://app.limecall.com/api/v1

Authentication

Every request carries a bearer token:

Authorization: Bearer sk_live_...

Create tokens under Settings → API keys, or on the Developers page in the dashboard. See API keys.

A first request

curl https://app.limecall.com/api/v1/calls \
  -H "Authorization: Bearer sk_live_..."

Writing an outcome back

The most valuable single call in the API. When a call turns into a booking or a sale, write that back and it appears on the call and in your totals:

curl -X PATCH https://app.limecall.com/api/v1/calls/{callId} \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"outcome":"appointment_booked","value":250,"currency":"USD"}'

The outcome name is yours — use the same one consistently and calls group by it. Sending value is what lets LimeCall report revenue by channel rather than call counts by channel. See Conversions.

Requires a token with write access.

Content type

Send Content-Type: application/json on requests with a body. Responses are JSON.

This API is not the dashboard's API

The /api/v1 surface is the customer-facing API, authenticated with sk_live_ tokens. The dashboard itself uses a separate internal API with session authentication.

Only /api/v1 is supported for integration. Anything you find by watching the dashboard's network traffic is internal, undocumented and will change without notice.

Endpoint reference

Resource	Endpoints	Covers
Calls	7	List, inspect, recordings, transcripts, summaries, outcome writeback
Messages	3	Send SMS/MMS, list history
Contacts	5	Full CRUD
Phone numbers	3	List and reconfigure your lines
Voicemails	2	List and mark handled
Users	5	Your team, and verified caller-ID numbers
Webhooks	5	Manage subscriptions
Analytics	3	Usage and breakdowns
Devices	2	Push tokens, for your own client

Also in this section

• API keys — creating and scoping tokens

• Webhook events — the events and how to handle them

• Errors, pagination & rate limits — status codes, paging and limits

Working in the browser instead

The REST API is for your server. To drive the callback widget from your own page — open it on a button, fire it from a form you already have, listen for events — use the browser API, which needs no secret key:

• JavaScript API

• Connect your own form

No-code alternatives

If you do not want to write code, Zapier, Make and n8n cover most integration needs. See Zapier, Make & n8n.