> ## Documentation Index > Fetch the complete documentation index at: https://docs.anchorbrowser.io/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Anchor Browser is cloud browser infrastructure for AI agents and automation: browser sessions you control over CDP or REST, natural-language web tasks, versioned automation tasks, managed authentication into third-party web apps (identities with MFA), persistent volumes and profiles, recordings, live view, batch sessions, webhooks, and network options including residential proxies, extra stealth, and captcha solving for sites that block standard browsers. AI agents should start at https://docs.anchorbrowser.io/for-agents, then get an API key with Agent Access at https://docs.anchorbrowser.io/quickstart/agent-access — no dashboard account required. Read those two pages before authentication or API calls. # List Task Executions (Legacy) > Retrieves execution history for a task, including success/failure status, execution times, and outputs. Results can be filtered by version and status. If you are using the new Task Builder, see the Tasks V2 endpoints in this API reference. ## OpenAPI ````yaml /openapi.yaml get /v1/task/{taskId}/executions openapi: 3.1.0 info: title: AnchorBrowser API version: 1.0.0 description: > Anchor Browser ([anchorbrowser.io](https://anchorbrowser.io)) provides cloud browsers built for AI agents and automation. Use this API to launch and control browser sessions, run natural-language web tasks, authenticate into third-party web apps with managed identities, and capture recordings — reliably and at scale, without operating browser infrastructure yourself. ## Core resources - **Sessions** (`/v1/sessions`): launch configurable cloud browsers — residential proxies, stealth browsing, captcha solving, profiles, extensions, recording — and connect over CDP with Playwright, Puppeteer, or any CDP client. - **AI tools** (`/v1/tools/perform-web-task`): state a goal in natural language and the built-in agent completes it inside the browser. Related tools fetch webpages, take screenshots, render PDFs, and execute code in a session. - **Tasks** (`/v1/task`): create, version, deploy, and monitor repeatable browser automations built to run reliably in production. - **Applications and identities** (`/v1/applications`, `/v1/identities`): managed authentication into third-party web apps — including multi-step logins and TOTP-based 2FA — so agents can act on behalf of users. - **Profiles** (`/v1/profiles`): persist cookies and login state across sessions. - **OS-level control** (`/v1/sessions/{sessionId}/mouse`, `/keyboard`, `/clipboard`): raw input for flows that resist DOM automation. - Plus batch sessions for running browser fleets in parallel, session recordings, webhooks, events, extensions, client certificates, and billing usage. ## Authentication Pass an API key in the `anchor-api-key` header on every request. Create keys at [app.anchorbrowser.io](https://app.anchorbrowser.io) under API Access. AI agents that have no key yet can obtain one autonomously through the unauthenticated [agent-access flow](https://docs.anchorbrowser.io/quickstart/agent-access) (`POST /v1/agent-access`). ## For AI agents and LLMs - Docs: [docs.anchorbrowser.io](https://docs.anchorbrowser.io), with a machine-readable index at [/llms.txt](https://docs.anchorbrowser.io/llms.txt) and the full corpus at [/llms-full.txt](https://docs.anchorbrowser.io/llms-full.txt). - MCP server for hosted browser control: `https://api.anchorbrowser.io/mcp`. - Official SDKs: `anchorbrowser` on [npm](https://www.npmjs.com/package/anchorbrowser) and [PyPI](https://pypi.org/project/anchorbrowser/). `DELETE` operations terminate sessions or permanently remove resources (profiles, identities, extensions); `GET` operations are safe and read-only. servers: - url: https://api.anchorbrowser.io description: API server security: [] paths: /v1/task/{taskId}/executions: get: tags: - Tasks (Legacy) summary: List Task Executions (Legacy) description: > Retrieves execution history for a task, including success/failure status, execution times, and outputs. Results can be filtered by version and status. If you are using the new Task Builder, see the Tasks V2 endpoints in this API reference. parameters: - name: taskId in: path required: true description: The ID of the task schema: type: string format: uuid - name: page in: query required: false description: Page number schema: type: string pattern: ^[1-9]\d*$ default: '1' - name: limit in: query required: false description: Number of results per page schema: type: string pattern: ^[1-9]\d*$ default: '10' - name: status in: query required: false description: Filter by execution status schema: type: string enum: - success - failure - timeout - cancelled - queued - running - name: version in: query required: false description: Filter by task version schema: type: string responses: '200': description: Task executions retrieved successfully content: application/json: schema: $ref: '#/components/schemas/TaskExecutionResultsListResponse' '404': description: Task not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Failed to retrieve task executions content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - api_key_header: [] components: schemas: TaskExecutionResultsListResponse: type: object properties: data: type: object properties: results: type: array items: $ref: '#/components/schemas/TaskExecutionResult' pagination: type: object properties: page: type: integer minimum: 1 description: Current page number limit: type: integer minimum: 1 description: Number of results per page total: type: integer minimum: 0 description: Total number of results totalPages: type: integer minimum: 0 description: Total number of pages required: - page - limit - total - totalPages required: - results - pagination ErrorResponse: type: object properties: error: type: object properties: code: type: integer message: type: string TaskExecutionResult: type: object properties: id: type: string format: uuid description: Unique identifier for the execution result taskVersionId: type: string format: uuid description: Task version identifier version: type: string description: Version that was executed status: type: string enum: - success - failure - timeout - cancelled - queued - running description: Execution status output: type: string nullable: true description: Task execution output errorMessage: type: string nullable: true description: Error message if execution failed startTime: type: string format: date-time description: Execution start time executionTime: type: number nullable: true description: Execution duration in milliseconds required: - id - taskVersionId - version - status - startTime securitySchemes: api_key_header: type: apiKey in: header name: anchor-api-key description: > API key for your Anchor Browser account, sent as the `anchor-api-key` header on every request. Create one at [app.anchorbrowser.io](https://app.anchorbrowser.io) (API Access), or obtain one programmatically via the unauthenticated agent-access flow (`POST /v1/agent-access`). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.