Simpliers CHAT API

List, publish, and unpublish your automations.

Last updated: September 10, 2026

Scope

This API reads and changes the status of automations built in the panel. There are no endpoints for building, editing, or deleting an automation, or for sending messages.

  • Authentication works with a Bearer key in the Authorization header. The key is created in the panel and its full value is shown only at the moment it is created.
  • The access level of a key is set while it is created and does not change later: you choose either view only, or viewing with publishing and unpublishing.
  • Requests are sent from a server only. Requests carrying an Origin header return 403, so a browser or a mobile app cannot use this API.
  • The rate limit is 120 requests per minute per key and 300 per minute per IP. A request over the limit returns 429.

Authentication

Every request carries a single key. No account id is sent with the request. The key is created in the panel, in the API keys part of the Integrations tab in account settings.

  • Open account settings in the panel and go to the API keys part of the Integrations tab.
  • Create a new key and choose its access level.
  • Store the key in your server environment variables.

The key is sent in the Authorization header on every request:

Authorization: Bearer smpl_...

The key cannot be embedded in a browser or a mobile app. A request carrying an Origin header returns 403 browser_origin_not_allowed, because a browser adds that header to every request.

Access levels

The access level is chosen while the key is created and cannot change for the life of the key.

View only

Reads the automation list. Requests that change status return 403 missing_scope.

View and manage

Reads the automation list; publishes or unpublishes an automation.

Endpoints

All endpoints live under https://api.simpliers.com.

The commands run in a terminal. Replace {flowId} with the automation id and "smpl_..." with your key. Publish and unpublish requests send no body.

List automations
GET /api/v1/chat/flows?status=published
View only

Parameters are separated by commas. The status=published parameter returns only published automations, and status=unpublished returns only unpublished ones. Without the parameter, all automations of the account are listed. "limit" sets the page size. Page size is 25 by default, 100 at most. The flowId comes from this response too.

curl -H "Authorization: Bearer smpl_..." \  "https://api.simpliers.com/api/v1/chat/flows?status=published"
Publish an automation
POST /api/v1/chat/flows/{flowId}/publish
View and manage
curl -X POST -H "Authorization: Bearer smpl_..." \  "https://api.simpliers.com/api/v1/chat/flows/{flowId}/publish"
Unpublish an automation
POST /api/v1/chat/flows/{flowId}/unpublish
View and manage

An unpublished automation does not run until it is published again, and its setup is not deleted.

curl -X POST -H "Authorization: Bearer smpl_..." \  "https://api.simpliers.com/api/v1/chat/flows/{flowId}/unpublish"

Response codes

For errors, the response holds an error object with code and message fields. The code is stable, the message text can change.

{  "error": {    "code": "missing_scope",    "message": "..."  }}
  • 403
    browser_origin_not_allowed
    If the request has an Origin header, meaning it came from a browser, it returns an error. The key is used from a server only.
  • 403
    missing_scope
    The key is not at the access level this endpoint needs. A view only key cannot change status.
  • 404
    flow_not_found
    The automation was not found. An automation belonging to another account returns this code too.
  • 429
    rate_limit_exceeded
    The request limit was exceeded. The same request can be repeated a minute later.

Rules and limits

Rules for a key:

  • Request limit
    120 requests per minute per key, 300 per minute per IP. A request over the limit returns 429 rate_limit_exceeded.
  • Account scope
    No account id is sent with the request, and a key only sees the automations of its own account.
  • Blocked account
    If account.effective in the response is blocked, an automation does not run even when it looks published. The request succeeds and the automation is not triggered.
  • Key rotation
    The name and the access level of a key are not edited later. You can create a new key and change the value on your server.