Callingly
MESSAGING · MESSAGING
Outbound calls, SMS, leads, and calling teams in the account they connected.
Connecting Callingly in practice
Callingly exists to make a phone ring the instant a lead arrives, so POST /calls and POST /sms are irreversible real-world actions, and the entire official reference is a help-centre article with no rate limit in it — an agent looping over leads has no published ceiling and every mistake is somebody’s phone.
Worth knowing
- The bearer token is generated at Settings > API Keys and "You cannot view the API key again so make sure you save it somewhere safe", so a lost key means a new one.
- Agencies acting for a client account must pass an account_id parameter; omit it and the call applies to the agency’s own account instead.
- Only three webhook events exist — call_completed, lead_created and lead_updated — and they are filtered by call status (completed, missed, offline), lead status (contacted, missed, removed, voicemail) and lead fields such as lead_owner, result, stage, status and tags, so anything not covered by those filters has to be polled.
- No rate limit, quota or throttling header is documented, which for an API whose side effect is an outbound call makes a conservative self-imposed limit the only safeguard.
Checked against Callingly API documentation (2026-09-29), Integrate Callingly using a webhook (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Callingly behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.