How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lorikeet Conversations API

Create, continue, and inspect AI-agent-handled support conversations.

Lorikeet Conversations API is one of 4 APIs that Lorikeet publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conversations. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0-modeled.

Requests are made against a single base URL, https://api.lorikeetcx.ai/v1.

4 operations 2 paths 8 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0-modeled
Base URL
https://api.lorikeetcx.ai/v1
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Lorikeet Conversations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer API key issued to your Lorikeet account. Send as Authorization: Bearer . Lorikeet also supports OAuth2, JWT bearer, Basic, HMAC, and M2M flows for tool/…

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Conversations 4

Create, continue, and inspect AI-agent-handled support conversations.

POST
/conversations
Create a conversation
createConversation body → 201401429
GET
/conversations
List conversations
listConversations 3 params → 200401
GET
/conversations/{conversation_id}
Retrieve a conversation
getConversation 1 param → 200404
POST
/conversations/{conversation_id}
Continue a conversation
continueConversation 1 param body → 200404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Conversation (9 properties), Message (5 properties), EndUser (4 properties), CreateConversationRequest (4 properties). Each schema is shown below with its type and property counts.

Message
object
5 properties
EndUser
object
4 properties
ConversationList
object
2 properties
Error
object
1 property
ConversationStatus
string
Lifecycle of a conversation. escalated indicates the agent handed off to a human per the workflow's escalation rules.
Conversation
object
9 properties
ContinueConversationRequest
object
2 properties 1 required
CreateConversationRequest
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lorikeet-conversations-api-openapi.yml Raw ↑

Other APIs Lorikeet publishes across the network.

Lorikeet Knowledge API
Lorikeet Messages API
Lorikeet Webhooks API
Where this information came from

This is an independent, third-party profile of Lorikeet Conversations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.