> ## Documentation Index > Fetch the complete documentation index at: https://docs.vocily.ai/llms.txt > Use this file to discover all available pages before exploring further. # Deploy history > When each version started answering, and when it stopped. **Paged.** This list used to return every row in one response. It now returns 20 by default - pass `?limit=` up to 100, and `?cursor=` with the previous response's `next_cursor` for the next page. See [Pagination](/developers/api-reference#pagination). Newest first. Two things are recorded: a version going live, and the agent being taken off air. Publishing is not — it files a frozen copy and goes nowhere near traffic, so it is not a deploy. | `action` | | | --------- | --------------------------------------------------------------- | | `live` | This version started answering calls | | `off_air` | The agent stopped answering; `version` is what it was taken off | `version_id` is `null` when that version was later deleted. The number and the moment still tell you what happened. An `off_air` row **does** carry the uuid — it names the version that stopped answering. ## OpenAPI ````yaml developers/openapi.json GET /v1/agents/{agent_id}/activations openapi: 3.1.0 info: title: Vocily API description: >- Public REST API for Vocily. Build and configure an agent, publish a version and put it live, place outbound calls, and read back calls, chats and what the agent remembered. Authenticate with a workspace API key as a Bearer token. Some things stay in the dashboard, by design: creating an API key, buying or connecting a phone number, setting an agent's webhook URL, connecting WhatsApp and its templates, building HTTP tools, and running batch campaigns. version: v1 servers: - url: https://api.vocily.ai description: Production security: [] paths: /v1/agents/{agent_id}/activations: get: tags: - agent-versions summary: List Activations description: >- The deploy history, newest first, **cursor-paginated**. Two things are recorded: a version going live, and the agent being taken off air. `activated_by_email` is left out: it names your own staff, and the WHAT and WHEN are the deploy history; the WHO is internal to your team. operationId: list_activations_v1_agents__agent_id__activations_get parameters: - name: agent_id in: path required: true schema: type: string title: Agent Id description: The agent's id, as `GET /v1/agents` returns it. - name: cursor in: query required: false schema: anyOf: - type: string - type: 'null' description: >- Opaque cursor from a previous response's `next_cursor`; omit for the first page title: Cursor description: >- Opaque cursor from a previous response's `next_cursor`; omit for the first page - name: limit in: query required: false schema: type: integer maximum: 100 minimum: 1 default: 20 title: Limit description: Maximum records to return in one page. responses: '200': description: >- Deploy history, newest first: when each version started answering and when it stopped. content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/PublicActivation' description: The rows on this page. has_more: type: boolean description: Whether another page exists. `false` on the last. next_cursor: type: string nullable: true description: >- Pass back as `?cursor=` for the next page; `null` on the last one. **Opaque** — do not parse or construct one. A cursor from a differently sorted list is refused with `invalid_cursor` rather than silently returning page 1. required: - data - has_more example: data: - version: 0 version_id: 00000006-0000-4000-8000-000000000006 action: live at: '2026-09-16T19:38:04.028171Z' has_more: false next_cursor: null '401': description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/ApiError' example: detail: Invalid API key code: UNAUTHORIZED '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' '429': description: Rate limit exceeded — honor `Retry-After`. content: application/json: schema: $ref: '#/components/schemas/ApiError' example: code: rate_limited security: - bearerAuth: [] components: schemas: PublicActivation: additionalProperties: false description: >- One entry in the deploy history: when a version started answering, or stopped. `version_id` is null when that version was later deleted — the number and the moment still tell the story, which is the point of keeping the row. properties: version: description: Which version number was involved. title: Version type: integer version_id: anyOf: - type: string - type: 'null' default: null description: >- That version's uuid. `null` when the version has since been deleted — `version` and the timestamp still tell you what happened. title: Version Id action: description: >- What happened. `live` — this version started answering calls. `off_air` — the agent stopped answering; `version` is what it was taken off. enum: - live - off_air title: Action type: string at: description: When it happened (UTC, ISO 8601). format: date-time title: At type: string required: - version - action - at title: PublicActivation type: object ApiError: type: object description: >- Error envelope. `code` is derived from the HTTP status, so branch on it for the CLASS of failure; the specific reason is `detail.code`. Every public refusal carries both. properties: detail: type: object description: >- The reason. `code` is the domain reason (e.g. `call_not_found`) and `message` is a sentence safe to log. On a `422` it also carries `errors[]`, one entry per rejected field — see `HTTPValidationError`. properties: code: type: string example: call_not_found message: type: string example: Call not found required: - code - message code: type: string description: Derived from the HTTP status, not the domain reason. example: NOT_FOUND HTTPValidationError: type: object title: HTTPValidationError description: >- A request the API could not read: a field of the wrong type, out of range, missing, or one we do not accept. Same envelope as every other error. properties: detail: type: object description: >- What was wrong, as `code`, a one-line `message`, and every offending field in `errors`. required: - code - message - errors properties: code: type: string enum: - validation_error message: type: string description: >- The first problem in one line, with a count of the rest — e.g. `model.temperature: Input should be less than or equal to 2 (and 1 more)`. errors: type: array items: $ref: '#/components/schemas/ValidationError' description: >- One entry per offending field. **Every problem is reported at once**, not just the first, so a malformed body needs one round trip to fix rather than one per field. code: type: string enum: - VALIDATION_ERROR description: Derived from the HTTP status, as on every error. ValidationError: type: object title: ValidationError required: - field - message - type properties: field: type: string description: >- The offending field as a path from the root of your request — `voice.speed`, `variables[0].key`, or `query.limit` for a query parameter. **This is the field to read.** message: type: string description: What is wrong with it, in plain language. type: type: string description: >- A stable machine code for the kind of failure, e.g. `extra_forbidden` for a field we do not accept, `missing` for a required one, or `less_than_equal` for a number out of range. Switch on this rather than on `message`, which may be reworded. securitySchemes: bearerAuth: type: http scheme: bearer description: 'Your API key as a Bearer token, e.g. `Authorization: Bearer vk_…`.' ````