Skip to main content
POST
Roll Back Agent

Overview

Moves the agent’s production pointer back to a version that has been deployed to production before, recording a new deployment with that version’s original semver. Phone numbers attached to the agent begin answering with the restored version. Find candidates with List Agent Deployments, where is_rollback_eligible is true. staging is not changed. Requires an admin, owner, operator, or prompter role.

Headers

string
required
Your API key for authentication.

Path Parameters

string
required
The agent’s unique identifier.

Body Parameters

string
required
ID of the version to restore. It must belong to this agent, have at least one production deployment on record, and not be the current production pin. Missing or empty returns 400 BAD_REQUEST. A version never deployed to production, or one that is already live, also returns 400 BAD_REQUEST with a message explaining which. An ID that is not one of this agent’s versions returns 404 NOT_FOUND.

Response

string
The restored version’s number, for example 1.3.1.
array
The agent’s three environments after the rollback. Each has id, env_type (dev, staging, or production), and current_version_id (the pinned version, or null if unpinned).
null | array
null on success, or a list of error objects if the request failed.

Docs for agents: llms.txt