Tidio API

REST access to contacts, conversations, and operators — but only on Plus

Tidio offers an OpenAPI-compliant REST API for programmatic access to its platform. The API covers the core objects most teams need for integrations and data sync, but there's an important caveat up front: it requires the Plus plan. Pricing starts at $749/month — contact Tidio sales for custom quotes. That puts it out of reach for most small businesses.

Base endpoint and format

All API requests go to:

https://api.tidio.co/v1/

Responses are JSON. The API follows standard REST conventions — GET for reads, POST for creates, PATCH for updates, DELETE for removals.

What the API covers

Resource Endpoints Typical use
Contacts List, get, create, update, delete Sync customer data with your CRM
Conversations List, get, create, update Pull conversation history, create tickets
Operators List, get Monitor agent status and assignments
Properties List, get, create Manage custom contact properties
Messages List within conversations Export chat transcripts
Tidio REST API resources and typical integration use cases.

The API is functional but not exhaustive. You won't find endpoints for Flows, Lyro configuration, analytics, or widget settings. It's designed for data access, not full platform administration.

Authentication

The API uses Bearer token authentication. You generate an API key in your Tidio dashboard under Settings > Developer.

Authorization: Bearer YOUR_API_KEY

Keep your API key secret. If compromised, regenerate it immediately from the dashboard.

Rate limiting

Tidio enforces rate limits and responds with HTTP 429 (Too Many Requests) when you exceed them. The documented limits are generous for typical integration use cases, but if you're running bulk operations, you'll need to implement retry logic with exponential backoff.

Example request

curl -X GET "https://api.tidio.co/v1/contacts" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

Response:

{
  "data": [
    {
      "id": "abc123",
      "name": "Jane Doe",
      "email": "jane@example.com",
      "properties": { ... }
    }
  ],
  "meta": {
    "total": 1,
    "page": 1
  }
}

Error handling

The API returns standard HTTP status codes:

Code Meaning
200 Success
201 Created
400 Bad request — check your parameters
401 Unauthorized — invalid or missing API key
404 Resource not found
429 Rate limited — slow down and retry
500 Server error — retry later
HTTP status codes returned by the Tidio REST API.

Error responses include a JSON body with a message field describing the issue.

Plan requirements

This is the biggest barrier. The REST API is only available on the Plus plan (starting from $749/month — talk to sales for custom pricing). Lower-tier plans — including Starter, Growth, and even Tidio+ — do not include API access.

For teams on lower plans who need integrations, the alternative is:

Who needs the API vs. Zapier

Scenario Best option
Sync contacts with a CRM Zapier (simpler) or API (more control)
Export conversation history API
Trigger actions in other tools Zapier
Build a custom dashboard API
Simple workflow automation Zapier
Bulk data operations API
Choosing between Tidio's REST API and Zapier integration depending on your use case.

In my view, most small and mid-sized teams will get everything they need from Zapier and native integrations. The API makes sense for larger organizations with custom development resources and specific data requirements — contact Tidio sales to discuss Plus plan pricing for your team size.

Bottom line

Tidio's REST API is well-structured and adequate for data integration use cases. The documentation is OpenAPI-compliant, responses are clean JSON, and the endpoint coverage handles the basics. The main issue is access: the Plus plan requirement means most Tidio users will never use it. If you're on a lower plan, start with the Widget SDK and Zapier.

Last updated: April 2026. Based on Tidio's API documentation and developer resources.