Back

Lorikeet SDK
Embed Lorikeet into your product, send context to Lorikeet and getting back action-ready AI responses
Overview
Lorikeet SDK is the developer-facing way to integrate Lorikeet into your own product or systems via Lorikeet’s REST API (and client libraries), so your app/agent can send customer messages to Lorikeet and receive the AI’s responses (and any actions/outcomes) back
What it is
In practice, Lorikeet's SDK can be used for two main integrations
Embed Lorikeet in your product (in-app experiences)
Your team builds the UI surface (chat bubble, swipe-down assistant, etc.).
The “SDK” (API and libraries) handles the conversation and workflow execution behind the scenes
Voice integrations (telephony)
Inbound Voice Calls (SDK): initialize a Lorikeet voice conversation before forwarding the live call to Lorikeet, while passing customer identifiers/context for personalization and routing
Outbound Voice Calls: let Lorikeet place proactive calls as part of workflows (reminders, verification calls, follow-ups), capturing outcomes for reporting/actions
How to integrate
Integrating Lorikeet via the SDK is straightforward: you keep the customer experience in your product, and use Lorikeet behind the scenes to understand requests, follow your policies, and take actions. Your team builds the surface (in-app assistant, chat entry point, or an internal agent), then sends customer messages and context to Lorikeet and displays the responses back to the customer.
For chat and in-app experiences, the SDK works as a simple request/response integration. Your app forwards each customer message to Lorikeet, receives an AI-generated reply, and can continue the conversation over multiple turns using the same conversation ID. You can pass customer identifiers and any relevant context up front so responses are personalized and workflows can execute accurately.
For voice, the SDK supports initializing inbound calls with the right customer context before routing the live call to Lorikeet, and it can also power outbound calling as part of proactive workflows (like reminders, verification calls, and follow-ups). This approach reduces implementation effort while keeping the integration maintainable as your voice workflows evolve.





