# Receptiva developer docs

> Receptiva is an AI phone receptionist for personal-injury law firms. These docs cover its MCP connector for Claude and ChatGPT and its REST API for a firm's own systems: how to connect, what each tool and endpoint returns, and what data leaves the firm.

- MCP endpoint: https://mcp.receptiva.ai/mcp (Streamable HTTP, OAuth 2.1, POST only)
- REST API: https://api.receptiva.ai, every path under `/v1` (API keys a firm owner creates; OpenAPI: https://api.receptiva.ai/v1/openapi.json)
- Every page is available as Markdown at its URL plus `.md`, or by requesting the page URL with `Accept: text/markdown`.
- Full text of every page in one file: https://www.receptiva.ai/docs/llms-full.txt

## Get started
- [Receptiva connector for Claude and ChatGPT](https://www.receptiva.ai/docs/overview.md): What the Receptiva MCP connector lets Claude or ChatGPT see and do for your firm today, and how to connect it in three steps.
- [Example prompts](https://www.receptiva.ai/docs/example-prompts.md): Prompts that work well with the Receptiva connector: leads to call back, recent calls, receptionist settings and changes, account status and pricing.

## Connect
- [Connect Receptiva to Claude](https://www.receptiva.ai/docs/connect-claude.md): Add Receptiva as a custom connector in Claude, sign in, choose your firms, and ask your first question.
- [Connect Receptiva to ChatGPT](https://www.receptiva.ai/docs/connect-chatgpt.md): Add Receptiva as a custom connector in ChatGPT, sign in, choose your firms, and ask your first question.

## REST API
- [REST API overview](https://www.receptiva.ai/docs/api-overview.md): How to call the Receptiva REST API from your own systems, covering the base URL, API key authentication, pagination, errors, rate limits and versioning.
- [API keys](https://www.receptiva.ai/docs/api-keys.md): How a firm owner creates and revokes Receptiva API keys, what each permission allows, and how to store a key safely.
- [Keep another system in sync](https://www.receptiva.ai/docs/sync-guide.md): A step-by-step recipe for copying Receptiva calls and leads into a case-management system with the REST API, using updated_since and stable call ids.
- [Webhooks](https://www.receptiva.ai/docs/webhooks.md): How Receptiva notifies your own system when a call finishes or a lead changes, how to verify a delivery, how retries work, and how to test and troubleshoot an endpoint.
- [API reference](https://www.receptiva.ai/docs/api-reference.md): Every endpoint of the Receptiva REST API: the permission it needs, its parameters, what it returns and the errors it can answer.

## Reference
- [Tools reference](https://www.receptiva.ai/docs/tools.md): Every tool your AI assistant can use through the Receptiva connector: what it does, who can use it, the arguments it takes and what it returns.
- [What's new](https://www.receptiva.ai/docs/whats-new.md): Changes to the Receptiva connector, REST API, dashboard and receptionist, newest first, with what an integration should do about each one.
- [Troubleshooting](https://www.receptiva.ai/docs/troubleshooting.md): What each connector error means and how to fix it, from "which firm?" to 406 and 429 responses.
- [Roadmap and API](https://www.receptiva.ai/docs/roadmap.md): What is live today in the Receptiva connector, REST API and webhooks, and what is coming next.

## Trust
- [Data and privacy](https://www.receptiva.ai/docs/data-privacy.md): Exactly what leaves your firm to an AI assistant through the Receptiva connector, what needs your owner's opt-in, what never does, and how every read is audited.

## Optional
- [Receptiva company brief](https://www.receptiva.ai/llms.txt): pricing, positioning and FAQ for the product itself
- [OAuth protected-resource metadata](https://mcp.receptiva.ai/.well-known/oauth-protected-resource/mcp): RFC 9728 discovery document for the MCP server