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

Tidio Lyro API

Lyro AI data sources and ticket answering

Tidio Lyro API is one of 9 APIs that Tidio publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Lyro. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and rate-limit docs.

This API exposes 5 operations across 5 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://api.tidio.co.

5 operations 5 paths 9 schemas 1 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.tidio.co
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Tidio Lyro API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Tidio-Openapi-Client-Id (clientId). An API key is passed in the header as X-Tidio-Openapi-Client-Secret (clientSecret). By default, every request must be authenticated.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Lyro 5

Lyro AI data sources and ticket answering

GET
/lyro/data-sources
Get Lyro data sources
getLyroDataSources 4 params → 200400
POST
/lyro/data-sources/qa
Create Lyro QA data source
createLyroQaDataSource body → 201422
PUT
/lyro/data-sources/website
Upsert Lyro data source
upsertLyroWebsiteDataSource body → 200422
POST
/lyro/data-sources/website/scrape
Add website as Lyro data source (scraping)
scrapeWebsiteLyroDataSource body → 201409422
POST
/lyro/tickets
Ask Lyro to answer ticket
askLyroToAnswerTicket body → 200409422

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are LyroDataSource (17 properties), LyroTicketRequest (6 properties), LyroTicketMessage (6 properties), LyroWebsiteUpsert (3 properties). Each schema is shown below with its type and property counts.

LyroTicketRequest
object
6 properties 6 required
ErrorItem
object
2 properties
LyroQaCreate
object
2 properties 2 required
LyroWebsiteUpsert
object
3 properties 3 required
LyroDataSourceList
object
2 properties
PaginationMeta
object
2 properties
LyroDataSource
object
17 properties
ErrorResponse
object
1 property
LyroTicketMessage
object
6 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tidio-lyro-api-openapi.yml Raw ↑

Other APIs Tidio publishes across the network.

Tidio Webhooks
Tidio Widget SDK
Tidio Contacts API
Tidio Departments API
Tidio Operators API
Tidio Products API
Tidio Project API
Tidio Tickets API
Where this information came from

This is an independent, third-party profile of Tidio Lyro 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.