> ## 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. # Get Webhook > Fetch a single webhook config. The signing secret is never returned. ## OpenAPI ````yaml /openapi.yaml get /v1/webhooks/{id} 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/webhooks/{id}: get: tags: - Webhooks summary: Get Webhook description: Fetch a single webhook config. The signing secret is never returned. operationId: getWebhook parameters: - name: id in: path required: true description: Webhook id. schema: type: string responses: '200': description: Webhook config. content: application/json: schema: $ref: '#/components/schemas/WebhookPublic' '404': description: Webhook not found in this project. content: application/json: schema: $ref: f6b9272d-37f8-4d5d-848b-40faac599112 '500': description: Failed to load webhook. content: application/json: schema: $ref: f6b9272d-37f8-4d5d-848b-40faac599112 security: - api_key_header: [] components: schemas: WebhookPublic: type: object description: >- A registered webhook subscription. The signing secret is NEVER returned by GET/list endpoints. required: - id - project_id - url - description - subscribed_events - enabled - created_at - updated_at properties: id: type: string description: Webhook id. Use as the path parameter on subsequent calls. example: wh_01HXJ4MZ7K9P3Q6R8S2T4V5W7Y project_id: type: string format: uuid description: The project (team) the webhook belongs to. example: 5d2c31f6-ab7e-481a-b6fd-8b4a96a4e197 url: type: string format: uri description: HTTPS URL Anchor will POST events to. example: https://your-app.example.com/anchor/webhooks description: type: string nullable: true maxLength: 256 description: Optional human-readable description. example: Production task notifications subscribed_events: type: array description: Event types this webhook is currently subscribed to. items: $ref: '#/components/schemas/WebhookEventType' enabled: type: boolean description: When `false`, no events fan out to this webhook. example: true created_at: type: string format: date-time nullable: true updated_at: type: string format: date-time nullable: true WebhookEventType: type: string description: | Catalog of webhook event types Anchor can deliver. Adding a new event type is a coordinated change between session-manager (publisher), webhook-dispatcher (consumer), and the dashboard. enum: - task.completed - task.failed - task.cancelled - task.healed - session.ready - session.completed - session.failed - session.recording.ready - batch.completed - batch.failed - intervention.requested - intervention.resolved - identity.authenticated - identity.authentication_failed 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.