--- title: Roadmap and API description: 'What is live today in the Receptiva connector, REST API and webhooks, and what is coming next.' sidebarTitle: Roadmap section: reference order: 30 updated: 2026-10-07 --- For what has already shipped, and when, see [What's new](/docs/whats-new). There are two ways to bring Receptiva data into other tools: the MCP connector for Claude and ChatGPT, and the REST API for your own systems. Here is what each offers today and what is coming next. Items marked coming soon are in development and not yet available; this page is updated as they ship. ## Status | Capability | Status | | --- | --- | | MCP connector at `https://mcp.receptiva.ai/mcp` with tools for account status, receptionist settings, calls and leads, including lead status updates and receptionist settings changes. See the [Tools reference](/docs/tools). | Live | | Sign-in with OAuth 2.1 and dynamic client registration (Google or an email one-time code) | Live | | Disconnecting an AI app from the Receptiva dashboard | Live | | Audit log entries for every call and lead read, every lead status change and every receptionist settings change | Live | | `GET https://api.receptiva.ai/v1/health` | Live | | REST API to read your account status, receptionist settings, calls, transcripts, recordings and leads, and to set a lead's status. See the [REST API overview](/docs/api-overview). | Live | | API keys, created and revoked by the firm's owner in the dashboard. See [API keys](/docs/api-keys). | Live | | Changing receptionist settings over the REST API | Coming soon | | Webhooks: `call.completed`, `lead.created` and `lead.updated` events, signed, retried for about two days, with a delivery log, test events and resend in the dashboard and on the REST API. See [Webhooks](/docs/webhooks). | Live | | Webhook events for trial and account changes (`trial.*`, `org.*`), and an event when a call starts | Coming soon | | OpenAPI document at `https://api.receptiva.ai/v1/openapi.json` | Live | | Changing, applying and rolling back receptionist settings over MCP | Live | | The email your receptionist gives callers, and up to 20 firm facts it shares when a caller asks | Live | | Caller numbers in full on calls, missed calls in the call list, and listing calls updated since a given time | Live | | On the REST API, listing leads updated since a given time (status changes included) and fetching the lead for one call | Live | | `lead_id` on every call, so a sync can fetch a call's lead directly, and `processing_complete` and `as_of` for polling | Live | | Safe lead status writes on the REST API: `expected_status` refuses a change if the lead has moved on (`409 status_conflict`) | Live | | A key describing itself at `GET /v1/account` (its permissions and expiry), with the firm's stable id | Live | | Finding a caller's calls and leads by phone number (`caller_number`), on the REST API and the connector | Live | | Your own id (`external_id`) and a status note (`status_reason`) on each lead, written with the lead's status or on their own, and finding a lead by `external_id` | Live | | Call transcripts, recording links and full lead intake over MCP, when the firm's owner turns on full caller data | Live | | Timestamps on transcript turns (`start_s`, seconds from the start of the call) | Live | | Structured call details: who a call was about, the caller's company, who they asked for, and claim, policy and case numbers with a match key, plus finding calls by one (`reference`). On the REST API and the connector | Live | | Full call records: after a transfer, the transcript includes the receptionist's briefing to your staff member and the conversation that follows (`segment`, `staff` turns), and one call's detail includes an AI summary of that conversation. On the REST API and the connector | Live | | Call recordings on the REST API (download, or a link that works for one hour), and a recording link through the connector when the firm's owner has turned on full caller data | Live | | House rules: up to 10 short standing preferences for how your receptionist responds, such as a question to ask every new caller | Live | | Editing firm facts and house rules in the Receptiva dashboard | Coming soon | | Setting up your receptionist and phone number tools over MCP | Coming soon | | A trial card inside Claude and ChatGPT (MCP App) | Coming soon | | Listings in the Claude and ChatGPT connector directories | Coming soon | | Case-management sync (for example Clio or Filevine) | Coming soon | | SMS | Coming soon | When an item ships, it moves to Live here. New tools also appear on the [Tools reference](/docs/tools) as soon as they are available. If you use Claude, refresh the connector to pick them up (see [Troubleshooting](/docs/troubleshooting#new-tools-dont-show-up)). Until the directory listings are approved, Receptiva works with Claude and ChatGPT as a custom connector. See [Connect Claude](/docs/connect-claude) and [Connect ChatGPT](/docs/connect-chatgpt). ## The REST API today The REST API reads your firm's account status, receptionist settings, calls, transcripts, recordings and leads, and sets a lead's status. It uses API keys your firm's owner creates in the dashboard. Start with the [REST API overview](/docs/api-overview), or the [sync guide](/docs/sync-guide) if you are connecting a case-management system. Changing receptionist settings is available through the [MCP tools](/docs/tools) only. A system that needs new calls as they happen can receive [webhooks](/docs/webhooks), poll for them, or do both. ## Early access If you are building on Receptiva and need something that is not here yet, email [hello@receptiva.ai](mailto:hello@receptiva.ai) and tell us what you are building. ## Next - [REST API overview](/docs/api-overview) - [Tools reference](/docs/tools) - [Overview](/docs)