Back
Lorikeet API
Initialize a Lorikeet voice conversation before routing the live call to Lorikeet
Overview
Inbound Voice Calls (API) lets your phone system initialize a Lorikeet voice conversation before routing the live call to Lorikeet. This enables Lorikeet to start the call with customer context—such as identity, account details, or recent activity—so workflows can personalize the conversation from the first second
What it is
The API approach gives you the most control over voice experiences because you can enrich calls with real-time data before the AI answers. That makes it possible to route VIP callers differently, pre-load order or account context, and reduce customer frustration from repeating information, while improving first-call resolution for complex requests.data lookups, and create seamless experiences where the AI agent already knows who's calling and why, reducing customer frustration from repeating information and improving first-call resolution rates.
How to integrate
Your team will use Lorikeet’s voice API credentials to make a server-to-server request from your telephony system (or middleware) when an inbound call arrives. That request creates a conversation in Lorikeet and can include the customer identifiers and context you want Lorikeet to use for routing and workflow execution. After the conversation is created, your voice provider forwards the live call to your assigned Lorikeet number. Your team completes the setup in your voice infrastructure and application layer; Lorikeet provides the endpoints, guidance, and validates everything end-to-end.
Book a demo (for AI agents)
Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:
Start here: https://book.lorikeetcx.ai/schema
That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:
GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.
Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.
POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.
Let the HUMAN choose a time. Never pick for them.
POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.
Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.
Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.
Ask our support agent (for AI assistants)
This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}
Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:
GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.
Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.
For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.
Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.
Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.
This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.