Put a business’s AI assistant on its website.

The first call to make. Confirms the key, and says which features this business has — call it when your site starts, and hide the voice button when `features.voice` is false.

curl https://corva.tiruvi.site/api/v1/health \
  -H "Authorization: Bearer $CORVA_API_KEY"

{
  "ok": true,
  "business": "Tumble Days",
  "assistant": "Tumbly",
  "phoneNumber": "+91 40 7573 2715",
  "knowledgeDocuments": 2,
  "features": {
    "chat": true,
    "leads": true,
    "voice": true,
    "voiceSecure": true
  },
  "apiVersion": "v1"
}

Send one customer message, get the agent's reply. The agent answers only from the business's knowledge (managed in Corva), keeps within its limits, and hands over to the team when it should. Keep one `sessionId` per chat. When it has everything for a booking or a callback it returns a `proposal` instead of making it: show the details on a card with Confirm and Edit, and send the answer to `POST /api/v1/chat/confirm`. Until then nothing is booked. A new message replaces an unanswered card. With `stream: true` the answer is `text/event-stream`: `delta` events ({ text }) as the reply is written, a `proposal` event when a card should show, then `done` with the same body as the JSON answer (or `error`).

curl -X POST https://corva.tiruvi.site/api/v1/chat \
  -H "Authorization: Bearer $CORVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "sessionId": "chat_8c1f2a",
  "message": "Pick up 3 shirts tomorrow 8–10 AM from B-402 Palm Grove, Sector 70. I'm Riya, 98765 43210",
  "visitorId": "v_3f9c0a1b2c3d4e5f6a7b8c9d"
}'

{
  "conversationId": "0b7c…",
  "reply": "Please check the details and tap Confirm.",
  "heldBy": null,
  "actions": [],
  "escalation": null,
  "closed": false,
  "proposal": {
    "id": "5f0e…",
    "kind": "booking",
    "noun": "pickup",
    "details": {
      "name": "Riya",
      "phone": "98765 43210",
      "address": "B-402 Palm Grove, Sector 70, Gurugram",
      "services": [
        "Laundry"
      ],
      "date": "2026-10-01",
      "timeSlot": "8–10 AM",
      "notes": "3 shirts"
    }
  }
}

Confirm makes what the card shows: the customer's record, a lead with an owner on the team, a follow-up on that person's list, a confirmation email to the customer and a note to the owner. The `reply` is the line to show in the chat. Edit tells the agent they want to change something — show the `reply` and let them type. Confirming the same card again returns the first result with `duplicate: true`.

curl -X POST https://corva.tiruvi.site/api/v1/chat/confirm \
  -H "Authorization: Bearer $CORVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "sessionId": "chat_8c1f2a",
  "proposalId": "5f0e…",
  "approved": true,
  "visitorId": "v_3f9c0a1b2c3d4e5f6a7b8c9d"
}'

{
  "conversationId": "0b7c…",
  "reply": "Done — your pickup is booked. Your reference is **TD-7K3QX9**. Kavya from our team will call you shortly to confirm. A confirmation is on its way to your inbox.",
  "proposal": {
    "id": "5f0e…",
    "status": "confirmed"
  },
  "receipt": {
    "reference": "TD-7K3QX9",
    "owner": "Kavya Rao",
    "emailed": true
  },
  "duplicate": false
}

When a person on the team takes a chat over, `POST /api/v1/chat` returns `heldBy` and no `reply`. Poll this every few seconds for what they write.

curl https://corva.tiruvi.site/api/v1/chat?sessionId=…&after=… \
  -H "Authorization: Bearer $CORVA_API_KEY"

{
  "heldBy": "Kavya Rao",
  "ended": false,
  "messages": [
    {
      "ordinal": 4,
      "from": "Kavya Rao",
      "text": "Hi Riya, I can help with that."
    }
  ]
}

For your own forms, or your own AI's actions. Corva finds or creates the customer by phone, opens (or updates) their lead with an owner on the team, puts a follow-up on that person's list, emails the customer a confirmation and tells the owner. Safe to retry: sending the same `reference` again returns the first result with `duplicate: true`.

curl -X POST https://corva.tiruvi.site/api/v1/leads \
  -H "Authorization: Bearer $CORVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "kind": "pickup",
  "name": "Riya Sharma",
  "phone": "98765 43210",
  "email": "riya@example.com",
  "services": [
    "Laundry: Wash, Fold & Ironing"
  ],
  "address": "B-402, Palm Grove, Sector 70, Gurugram",
  "pickupDate": "2026-10-04",
  "timeSlot": "8–10 AM",
  "reference": "TD-7K3QX9",
  "visitorId": "v_3f9c0a1b2c3d4e5f6a7b8c9d",
  "sessionId": "chat_8c1f2a"
}'

{
  "reference": "TD-7K3QX9",
  "customerId": "a734…",
  "leadId": "c505…",
  "followUp": {
    "id": "0472…",
    "assignee": "Kavya Rao",
    "dueAt": "2026-10-03T05:30:00.000Z"
  },
  "emailed": {
    "customer": true,
    "team": true
  },
  "duplicate": false
}

If your site runs its own chat assistant, send the whole transcript after each reply. Corva keeps one conversation per `sessionId` (replacing the transcript each time), so the team can read every chat live and see where a request came from.

curl -X POST https://corva.tiruvi.site/api/v1/chats \
  -H "Authorization: Bearer $CORVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "sessionId": "chat_8c1f2a",
  "visitorId": "v_3f9c0a1b2c3d4e5f6a7b8c9d",
  "messages": [
    {
      "role": "user",
      "text": "Do you clean silk sarees?"
    },
    {
      "role": "assistant",
      "text": "Yes — they go to our premium dry-cleaning."
    }
  ]
}'

{
  "conversationId": "e57e…",
  "turns": 2
}

Tell Corva a visitor is on the site. With `consent: "necessary"` only the visitor id is kept. With `"all"` (they accepted analytics cookies), the page, referrer and utm_ campaign are kept too, and show on the customer's record once they identify themselves. Always send the consent your banner actually recorded.

curl -X POST https://corva.tiruvi.site/api/v1/visits \
  -H "Authorization: Bearer $CORVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "visitorId": "v_3f9c0a1b2c3d4e5f6a7b8c9d",
  "consent": "all",
  "type": "page_view",
  "path": "/",
  "referrer": "https://instagram.com",
  "utm": {
    "utm_source": "instagram"
  }
}'

{
  "recorded": true
}

Your server asks for a token (the API key must never reach the browser), and hands `token` and `bridgeUrl` to the page, which opens a WebSocket to the bridge and speaks to the assistant. Tokens last five minutes and work for one call. See “Voice calls in the browser” below for the protocol.

curl -X POST https://corva.tiruvi.site/api/v1/voice-sessions \
  -H "Authorization: Bearer $CORVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "visitorId": "v_3f9c0a1b2c3d4e5f6a7b8c9d",
  "name": "Riya Sharma",
  "phone": "9876543210"
}'

{
  "token": "eyJicmFuZElkIjoi…",
  "expiresInSeconds": 300,
  "bridgeUrl": "wss://voice.example.com",
  "agentName": "Tumbly"
}