Changelog

All changes to the DialerBee API, newest first.

1.0.0-rc6

Sending is available. Click-to-call (POST /v1/calls) and SMS (POST /v1/sms) work once your account administrator switches them on in the console's guided sending setup. WhatsApp sending is not open yet.

• New scopes calls:originate and messages:send, held only by a sending key (IP allow-list required, daily and per-minute caps). They replace calls:write and sms:send, which no key ever held.
• Click-to-call is a Tier-2 operation behind the switch tier2_calls_originate_enabled; GET /v1/me reports it as tier2.calls_originate.
• Every API SMS goes through the console's compliance checks before it is sent; a named caller_id must be one of your verified caller IDs.
• New errors: sending_suspended, outbound_not_approved, insufficient_balance (402), spend_cap_reached and message_refused.

1.0.0-rc5

• Click-to-call: POST /v1/calls (scope calls:write) connects one of your agents (named by extension or sign-in email) with a customer, after checking that the agent is signed in and ready and holding the agent for the call; every compliance check runs first. New errors: agent_unavailable and dial_refused. Not available yet (403 tier_not_enabled).

• Speed-to-lead: POST /v1/leads adds one lead to a draft, ready, paused or running campaign through the import's own validation, with an optional lead source and dial_now (the lead goes first in a running campaign's dialling order for dial_within_seconds). A running campaign or dial_now also needs calls:write and is not available yet; AI assistants ask you to confirm every lead.

• WhatsApp: POST /v1/whatsapp/messages (scope whatsapp:send) sends a text or an approved template; a repeated client_reference is refused. Not available yet (403 tier_not_enabled).

• SMS sending (POST /v1/sms) is available as a Tier-2 operation, behind the same duplicate guard.

• The hosted MCP server at https://api.dialerbee.com/mcp, and a private sandbox for each API client.

• Call summaries: every call of the account answers with a status (ready, processing, or not_generated with a not_generated_reason) and a schema_version, for calls handled by people and by an AI agent. New fields: reason_for_contact, intent, next_action, outcome_candidate, language (BCP 47), source and generated_at. summary is null unless the status is ready. 404 not_found now means only that the id names no call of the account.

• Response objects may gain fields within v1: ignore fields you do not know. Request objects still refuse unknown fields.

• Leads: import with a result per lead, list, read, update and history.

• Campaigns: list, read, progress, pause; resume (Tier 2).

• Calls: list, read, recording, transcript and AI summary.

• Webhooks: endpoints, signed deliveries with the DialerBee-* headers, event history, replay and secret rotation with a 24-hour overlap.

• Do-Not-Call: check and add. Removing a number is not in the API: an account administrator does it in the DialerBee console (see Later). Consent (Tier 2).

• Callbacks: list and cancel; schedule and move (Tier 2).

• Appointments: list and read; book, move and cancel (Tier 2).

• SMS: delivery reports and usage counters; sending (Tier 2).

• Reports: disposition counts.

• API clients with several keys each, scopes, Tier-2 account switches, RFC 9457 errors, idempotency keys, cursor pagination.