The Demonstrations API lets your customers record browser workflows through a shareable URL — no Anchor account required. A customer opens the link, performs a task in a live browser, and Anchor automatically generates a reusable deterministic workflow from the recording.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.
How it works
- Create a demonstration session via API — you get back a
share_url - Send the share URL to your customer (email, embed, etc.)
- Customer opens the link, sees a live browser, and performs the task
- Customer clicks “Finish Demonstration” — the recording is submitted
- Anchor generates a workflow from the recorded actions
- Poll the status endpoint until it reaches
completed— you gettask_idandtool_id
API Endpoints
Create a demonstration
| Field | Type | Required | Description |
|---|---|---|---|
task_name | string | Yes | Name for the workflow being recorded |
task_description | string | Yes | Natural language description of what the task does — used by the AI to understand the recording |
identity_id | string | No | Pre-authenticate the browser with a saved identity |
identity_skip_validation | boolean | No | Skip identity validation (default: true) |
user_name | string | No | Display name shown in the recording UI (“Thanks, John!”) |
session_config | object | No | Override browser session settings (start URL, proxy, timeouts, etc.) |
The
share_url is a signed JWT link valid for 1 hour. The customer does not need an Anchor account — the token contains the session and team context.Get demonstration status
Poll this endpoint to track progress after recording completes.| Status | Description |
|---|---|
recording | Browser session is live, user is recording |
processing | Recording complete, workflow is being generated |
completed | Workflow generated successfully — task_id and tool_id are available |
failed | Workflow generation failed |
stopped | Session was stopped before completing |
Complete recording
Called automatically by the recording UI when the user clicks “Finish Demonstration”. Can also be called programmatically.- Ends the browser session (triggers upload of recorded actions)
- Waits for the recording artifacts to be uploaded to S3
- Submits the recording to Hektor for workflow generation
- Returns immediately with
status: "processing"
Stop demonstration
Stop a demonstration without generating a workflow. Useful for cleanup.End-to-end example
Identity pre-authentication
Pass anidentity_id to pre-authenticate the browser before the customer opens it. The customer will see the target application already logged in and can immediately start recording the task.
Share URL and the recording UI
Theshare_url opens a full-screen recording interface with:
- Live browser iframe — the customer interacts with the actual website
- Live Browser Events panel — shows clicks, typing, navigation in real-time
- “Finish Demonstration” button — completes the recording and triggers workflow generation
window.open), the parent window receives a demonstration-complete postMessage with the task_id, task_version_id, and tool_id.
Session configuration
Override default session settings:max_duration: 30 minutes and idle_timeout: 30 minutes.
