Skip to main content
POST
Use this endpoint to undo changes: it saves the agent with the settings recorded in an earlier version from List Agent Change History. Nothing is removed from the history. The revert is recorded as a new version, so it can itself be undone the same way.

Path Parameters

string
required
The unique identifier of the agent (UUID format)
integer
required
The id of the version to restore, from List Agent Change History. Use id, not the version display number.

Request Body

No request body.

Behavior

The response is a confirmation only. It does not return the agent or the restored fields. To see exactly what changed, read List Agent Change History a few seconds later: the revert appears as a new entry with action: "reverted", reverted_from_id set to the version you restored, actor.id set to api:<accountId>, and source: "dashboard-api". Only recorded settings are restored. The settings the change history records come back to their values in that version. Everything else stays as it is now: agent status, functions, outbound and voicemail greetings, AMD/IVR, screenshare, email server, call limits and retries, agent type, integrations, SIP, and knowledge base documents. Web transfer also stays, except that restoring call transfer off turns web transfer off with it. The organization’s feature locks apply, as for Update Agent. A revert that would switch on an AI model, voice provider, cloned voice, warm transfer, knowledge base (RAG), PII redaction or email template the organization can no longer use is refused with 403, and nothing is saved. So is a revert that changes the knowledge base settings while RAG is no longer available. Keeping a setting the agent already has on is not refused. The agent’s save rules apply too. A version that breaks one of the rules every agent save follows is refused with 403, and the message says which rule. Reverting to the current settings changes nothing. If the version’s settings already match the agent, the request still returns 200 (“If any settings changed, …”), but no new version is recorded. Applied immediately. The agent’s cached configuration is refreshed as part of the request, so new calls use the restored settings. Calls already in progress are not interrupted. LiveKit agents only. Agents on other providers return 403, matching Update Agent.
Scoped API keys can use this endpoint for agents inside their reseller or organization. An agent outside the key’s scope returns 404, the same as an agent that does not exist.

Common Uses

Undo a bad change

  1. List the history and find the last good version, the one just before the unwanted change:
  1. Revert to that version’s id:
  1. A few seconds later, list the history again to confirm the new reverted entry and what it changed.

Undo a revert

A revert is an ordinary version. Revert to the version just before it to undo it.

Troubleshooting