List Agent Versions
Versioning
List Agent Versions
POST
List Agent Versions
Use this API to fetch the version history for a custom agent. A new version is created automatically on every Update Agent Version call. Versions are returned newest-first (descending by version number). Each version is a behavioral snapshot of the agent at that point in time — identity fields (
Errors:
name, description, enabled, managedBy) live on the root agent document and are not part of version snapshots.
Any auth secrets in a version snapshot are redacted ("__redacted__") before the response is returned: both rest-api strategy secrets and mcp-tools server secrets (execution.mcpServers[].auth).
Endpoint
POST https://api.velt.dev/v2/agents/versions/list
Headers
string
required
Your API key.
string
required
Your Auth Token.
Body
Params
object
required
Example Requests
Response
Success Response
Alongside those three
versions[] fields, every behavioral field the agent had at that version is present on each row: rawInstructions, instructions, phaseTimeoutMs, contextGathering, execution, response, postProcess, input, scope, and setup. The example above is abridged. Identity fields (name, description, enabled, managedBy) are not versioned and never appear here; read them from Get Agent.
This endpoint returns the agent’s full version history in one response. There is no pagination and no cap, so an agent with a long edit history returns a correspondingly large payload.
Failure Response
INVALID_ARGUMENT (missing or empty agentId) / NOT_FOUND (the workspace store database could not be resolved).
An agent that does not exist is not an error here. It returns
200 with an empty versions array, which is indistinguishable from an agent that exists but has no version history.
