Copy page

What's New

September 7, 2026

Clearer call failure reporting: Improved call failure details and corrected cases where platform or connection failures were reported as recipient declines (#206, #82, #111, #195).

Developer API calls in Call Records: Calls created through the Developer API now appear in Dashboard Call Records and can be found using their provider call ID (#151).

KYC for purchased numbers: Identity verification (KYC) is now required before purchased numbers can make outbound calls, strengthening security and compliance. The shared number pool is intended only for development and testing; for production, use your own purchased numbers with completed KYC or connect through a SIP integration.

September 3, 2026

Server SDK 0.7.0: The stable TypeScript and Python packages now include the Calls and Goal Runs client surfaces. Goal Run responses expose the nullable call_id field for call correlation when that persisted identifier is available. The TypeScript SDK source is available under the MIT License at CALLE-AI/server-sdk-typescript.

August 21, 2026

Safer calle call start result handling: CALL-E CLI and @call-e/core now recognize JSON results returned through MCP content blocks while preserving the original response. This prevents valid run_call results from being treated as missing a run_id, helping users avoid unsafe retries when a call may already have started.

Longer call-planning timeout: Call planning now uses a dedicated 150-second timeout, reducing failures caused by the previous 15-second default. An explicit --timeout-seconds value continues to override the planning timeout (#79).

Reliable Goal publishing: Fixed an issue that could leave a Goal in Draft while the Dashboard reported that publication was proceeding (#135).

Correct call activity timelines: Fixed cases where ringing or calling events could appear after a call had already ended (#112).

Reliable Goal Run authorization: Fixed an authorization issue that could cause an accepted Goal Run to fail before the outbound call started (#106).

August 15, 2026

Clearer call plan CLI guidance: The CLI documentation now points users to calle call plan --help to view the parameters supported by the call plan subcommand.

More informative MCP timeout errors: Timeout failures for MCP tools/call requests now include additional error information to make them easier to diagnose.

Phone keypad IVR support: CALL-E now supports phone keypad IVR interactions.

Dashboard Call Records: The Dashboard now includes Call Records for reviewing task history, conversations, and call audio recordings.

SDK and API integration examples: The Dashboard now includes SDK and API integration examples and can display the instruction associated with each Goal.

Durable multi-session execution: Users can run tasks concurrently across different chat sessions while each session keeps one active task at a time. Accepted tasks continue through page refreshes, closed tabs, and temporary connection or service interruptions.

Session recovery and clearer task status: The Dashboard restores messages, progress, drafts, user-facing reasoning summaries, and final Goal results after reconnecting. Clearer task states remain synchronized across current and background sessions.

Reliable commands and call control: Messages, interaction answers, reauthorization, and Stop requests can be retried without creating duplicate work. Stop applies only to its intended task, while uncertain call submissions are verified before retrying.

Dashboard reliability fixes: Fixed issues that could lose or stall accepted tasks, duplicate messages or calls, mislabel queued work, or leave the Dashboard out of sync. Stop outcomes now reflect confirmed results and preserve a task's true completion state.

August 11, 2026

Dashboard-issued API keys: Developer API authentication now accepts the iams_live_ API keys shown in the CALL-E dashboard. The server SDK configuration remains unchanged: pass the key through CALLE_API_KEY, and the SDK sends it as a Bearer credential.

July 29, 2026

Terminal webhook delivery: Call tasks that include webhook_url now send terminal event notifications to that URL. Each notification includes a stable event id for idempotent processing, and delivery is retried when the receiver does not return a 2xx response. CALL-E waits until the post-call outcome and requested structured results are finalized, so the webhook contains the same complete terminal snapshot returned by the Calls API.

Current deliveries include CALL-E-Event-Id for deduplication and do not include a webhook secret, timestamp, or signature header. Receivers must treat the payload as untrusted input, validate the event shape, and compare the header event id with the body id. The Python and TypeScript SDKs keep their legacy signed-webhook helpers only for source compatibility and mark them deprecated.

July 22, 2026

Phone-only Goal Run requests in API 0.6: Create Goal Run requests now use a top-level phone plus variables. The target wrapper and per-Run region, locale, and display_name fields have been removed. Voice region and callee locale are fixed by the published Goal; recipient names needed by the conversation belong in the Goal's input schema and are supplied through variables.

The TypeScript and Python SDK source candidates now implement the matching client.goals surface at version 0.6.0, including Goal discovery, Run creation, Run reads, and result-or-error polling. Existing Calls and Webhooks surfaces remain compatible; registry packages stay on their current stable versions until the 0.6.0 release is published.

Simplified Goal Runs API 0.5: This release includes:

1. Useful Goal metadata: Goal list and get responses now include the current published title and description alongside the input and result schemas.

2. Smaller response: Goal and Goal Run responses expose RunSpec ids and versions without content fingerprints.

3. One result contract: a Goal Run returns the parsed object directly in result, or one unified error when execution or result processing fails. When both are null, clients continue polling.

4. Goal discovery: GET /v1/goals lists the authenticated owner's active, listed, published Goal interfaces with opaque cursor pagination. The API 0.5 SDK design adds client.goals.list(...) in both TypeScript and Python while keeping stable 0.2 packages Calls-only until a matching SDK minor is released.

July 21, 2026

Goal Runs API preview: This preview includes:

1. Published Goal interface: Read the current normalized input schema, result schema, and RunSpec identity with GET /v1/goals/{goal_id}.

2. Goal Run creation: Create one singleton Run with POST /v1/goals/{goal_id}/runs. Requests supply one target, scalar variables, and a required business-stable Idempotency-Key; they cannot replace the published schemas or choose a RunSpec version. Initial acceptance and exact replay both return 201.

3. Result polling: Read execution and schema-bound results with GET /v1/goals/{goal_id}/runs/{goal_run_id}. The Goal Run preserves the exact RunSpec version pinned when CALL-E accepted it.

4. SDK transition: The Goal Runs guide defines TypeScript and Python parity on client.goals, with get, run, get-Run, wait, and run-and-wait helpers using each language's naming convention. Stable 0.2 SDK packages continue to support the one-shot Calls API until matching next-minor packages are released.

See Goal Runs for request, polling, version-pinning, and SDK examples.

June 8, 2026

Developer API and server SDKs: This release includes:

1. Developer API: Create outbound call tasks, retrieve call task details, list call task events, and receive terminal webhook messages from a trusted server environment.

2. TypeScript server SDK: The CALL-E TypeScript server SDK is available on npm.

Code
pnpm add @call-e/calle

Use CalleClient to create a call task and wait for a terminal result.

3. Python server SDK: The CALL-E Python server SDK is available on PyPI.

Code
pip install calle-ai

Import CalleClient from calle to create call tasks and poll results.

4. Server-side integrations: API keys and server SDKs are designed for trusted backend services, workers, and automation systems. Browser SDKs, scheduled call tasks, cancel call task APIs, and project-level webhook management are not part of this release.