# Corva

> Corva is an AI front office for businesses: an assistant that answers a business's customers on website chat, WhatsApp and voice, and turns every conversation into a customer record, a lead with an owner and a follow-up. Its REST API connects a business's website and systems to that assistant.

Integrating Corva into an app: keep the API key (ck_…) on the server only, read GET /api/v1/config instead of hard-coding the business's fields, keep one sessionId per chat, and let the customer confirm every booking card.

## Docs

- [Full developer guide (Markdown)](https://corva.tiruvi.site/llms-full.txt): every section and every endpoint in one file
- [Overview](https://corva.tiruvi.site/developers.md?section=overview): What Corva is, and the three ways a website or system connects to it.
- [Quick start](https://corva.tiruvi.site/developers.md?section=start): A key, two settings, and a chat route on your server.
- [How it fits together](https://corva.tiruvi.site/developers.md?section=concepts): Sessions and visitors, when a chat ends, one customer across channels, the leads board, details, data out, bookings, takeover.
- [Keys, errors and limits](https://corva.tiruvi.site/developers.md?section=auth): Bearer keys, status codes, rate limits, timeouts and formats.
- [API reference](https://corva.tiruvi.site/developers.md?section=reference): Every endpoint, with its fields, a request and a response.
- [Voice calls in the browser](https://corva.tiruvi.site/developers.md?section=voice): Tokens, the WebSocket protocol, iPhone gotchas and limits.
- [Webhooks](https://corva.tiruvi.site/developers.md?section=webhooks): Events Corva sends your systems, and how to verify each delivery.
- [Taking payments](https://corva.tiruvi.site/developers.md?section=payments): Your payment endpoint, offers checked in code, and reporting a payment back.
- [Cookies & consent](https://corva.tiruvi.site/developers.md?section=cookies): The two first-party cookies we suggest, and what consent changes.
- [Going live](https://corva.tiruvi.site/developers.md?section=golive): The checklist before real customers use it.

## API

- [OpenAPI 3 spec](https://corva.tiruvi.site/api/v1/openapi.json): machine-readable endpoints and webhook payloads
- [Setup endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=setup): Check the key, and read how the business is set up.
- [Chat endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=chat): The assistant in your chat window, or your own assistant's transcripts.
- [Leads endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=leads): Bookings, callbacks and enquiries from your own forms.
- [Records endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=records): Read the business's leads, customers and conversations back; keep a lead in step with your system; tell the assistant where an order has got to.
- [Payments endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=payments): Tell Corva where a payment to the business stands, so the team and the assistant know it was paid.
- [Webhooks endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=webhooks): Register the addresses Corva sends events to, without opening the console.
- [Visitors endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=visitors): Who is on the site, with their consent.
- [Voice endpoints](https://corva.tiruvi.site/developers.md?section=reference&group=voice): Talk to the assistant from the browser.