Tidio for Developers

What is available to build on, what is gated, and what I would watch for

Tidio offers three main developer-facing surfaces: a JavaScript Widget SDK for frontend control, a REST-based OpenAPI for backend work, and webhooks for event-driven automation. The important caveat is pricing: the Widget SDK is broadly available, but the more serious backend tooling is locked behind the Plus plan.

Widget SDK (tidioChatAPI)

The Widget SDK is the most accessible developer tool in the product. It lets you control the frontend widget from your own code.

What you can do with it:

• Open or close the widget programmatically
• Identify logged-in users and pass custom attributes
• Hide or show the widget based on page state or user state
• Trigger flows from your own UI
• Control language behavior
• Listen for widget and conversation events

Typical use cases I see:

• Showing chat only after a user has spent time on a page
• Passing logged-in account context to agents
• Opening chat from a custom button instead of the floating widget
• Hiding the widget on specific layouts or devices

Implementation: The SDK runs through window.tidioChatAPI after you install the Tidio script.

window.tidioChatAPI.setVisitorData({
  distinct_id: "user_12345",
  email: "customer@example.com",
  name: "Jane Smith",
  plan: "Pro"
});

window.tidioChatAPI.open();

OpenAPI (REST)

Tidio's OpenAPI is the piece that matters if you need backend integration.

What it covers:

• Contacts
• Conversations
• Operators
• Custom properties and synced metadata

How it works: Standard REST conventions, JSON payloads, bearer-token authentication.

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

What I would note: This is where pricing becomes a real product decision. OpenAPI access requires Plus, which means API-dependent integrations start at a much higher cost floor than many developers will expect.

Rate limiting: Tidio enforces rate limits and returns 429 / too_many_requests when exceeded. I would build in retry logic and backoff from the start.

Webhooks

Webhooks let Tidio push events to your server instead of forcing you to poll for changes.

Common event types include:

• contact.created
• conversation.solved_automatically
• Ticket and reply events

Setup: Configure endpoint URLs inside the Tidio dashboard, choose subscribed events, and verify requests using the x-tidio-signature header.

Example payload shape:

{
  "created_at": 1687177445,
  "project_public_key": "your_project_key",
  "topic": "contact.created",
  "version": 1,
  "webhook_id": "7307ac4d-...",
  "content": { ... }
}

Example receiver:

const express = require('express');
const app = express();
app.use(express.json());

app.post('/tidio-webhook', (req, res) => {
  const { topic, content } = req.body;

  if (topic === 'conversation.solved_automatically') {
    console.log('Lyro resolved:', content);
  }

  res.sendStatus(200);
});

app.listen(3000);

What I take from developer feedback

Developer feedback on Tidio is lighter than on more technical platforms because the product is still aimed mainly at business users. The recurring themes I do see are fairly consistent:

• The frontend SDK is useful and approachable
• The docs are workable, but not always as complete as developers want
• API and webhook access are gated too high for smaller teams

That last point matters most. If your integration roadmap depends on backend sync, custom workflows, or real-time events, Tidio's Plus requirement may be the deciding factor by itself.

Summary

For lighter integrations, Zapier often fills the gap well enough. For anything more serious or custom, I would budget around the Plus plan from the start and review the official developer documentation closely before committing.