Skip to main content
The Replier API lets your own code or an automation tool do what you can do in Replier: list workspaces, accounts and posts, create and change automations, read results and contacts, and send catch-up or one-time replies. To use Replier from ChatGPT, Claude or another AI app, connect it as an AI app instead. The API reference lists every endpoint with its parameters and responses.

​
Create an API key

  1. In Replier, open your account menu and choose Manage account → Integrations.
  2. Under API keys, select Create API key.
  3. Enter a name you will recognize later, choose its access, and select Create key.
  4. Copy the key. Replier shows it only once.
Anyone who has the key can use Replier as you, so keep it out of code you share and out of your browser. If a key leaks, delete it and create a new one. A key that can only view your data is refused when it tries to change something. A key that can also make changes can create, edit, turn on or off and delete automations, save your default message text, reorder the next-post queue, upload reply photos, and send catch-up and one-time replies. Either way, a key acts with your role in each workspace, so it can’t do more than you can.

​
Make a request

Send the key as a bearer token to https://api.usereplier.com/v1:
Every other request is made in one workspace. Use a workspace id from that list:
Requests that change something send JSON:
Automations made or changed through the API have the same limits as in Replier: up to 24 targets, three buttons, an optional photo, and message flows in Studio workspaces.

​
Errors

A refused request answers with an HTTP status and a body like this:
code stays the same; message may be reworded. Some errors add fields beside them, such as the automation that already has the post you chose.

​
Retry safely

Requests that change something take an Idempotency-Key header. Send a new random value, such as a UUID, for each operation, and the same value when you retry it. A retry with the same key returns the first result instead of creating a second automation or sending replies twice. Sending catch-up, backfill or one-time replies, and creating a one-time automation, require the header; without it the request is refused with IDEMPOTENCY_KEY_REQUIRED.
To avoid overwriting someone else’s change, send expected_version with the version you read. If the automation changed since, the request is refused with VERSION_CONFLICT. Deleting an automation requires it.

​
Changes to the API

Within /v1, Replier only adds: new endpoints, new optional parameters, new response fields and new values in fields that list states or reasons. Ignore fields and values you don’t know. A change that would break existing code comes as /v2.

​
Pause or delete a key

In Manage account → Integrations, each key shows its access and when it was last used. Choose Pause access to refuse its requests until you choose Resume access. Choose Delete key to remove it for good; code using it loses access right away. Automations it created keep running.