How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Anchor Browser Session Recordings API

The Session Recordings API from Anchor Browser — 5 operation(s) for session recordings.

Anchor Browser Session Recordings API is one of 20 APIs that Anchor Browser publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Session Recordings. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.anchorbrowser.io.

5 operations 5 paths 4 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://api.anchorbrowser.io
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Anchor Browser Session Recordings API declares 1 security scheme for authenticating requests. An API key is passed in the header as anchor-api-key (api_key_header).

  • api_key_header — API key passed in the header

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Session Recordings 5
POST
/v1/sessions/{session_id}/recordings/pause
Pause Session Recording
1 param → 200401404500
POST
/v1/sessions/{session_id}/recordings/resume
Resume Session Recording
1 param → 200401404500
GET
/v1/sessions/{session_id}/recordings
List Session Recordings
1 param → 200401404429
GET
/v1/sessions/{session_id}/recordings/primary/fetch
Get Session Recording
1 param → 200401404500
DELETE
/v1/sessions/{session_id}/recordings/{recording_id}
Delete Session Recording
2 params → 200400401500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are RecordingItem (7 properties), SuccessResponse (1 property), ErrorResponse (1 property), RecordingListResponse (1 property). Each schema is shown below with its type and property counts.

RecordingItem
object
7 properties
RecordingListResponse
object
1 property
ErrorResponse
object
1 property
SuccessResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

anchorbrowser-session-recordings-api-openapi.yml Raw ↑

Other APIs Anchor Browser publishes across the network.

Anchor Browser API
Anchor Browser MCP Server
LangChain Anchor Browser Tools
Anchor Browser Agentic capabilities API
Anchor Browser AI Tools API
Anchor Browser Applications API
Anchor Browser Batch Sessions API
Anchor Browser Billing API
Anchor Browser Browser Sessions API
Anchor Browser Certificates API
Anchor Browser Event Coordination API
Anchor Browser Extensions API
Where this information came from

This is an independent, third-party profile of Anchor Browser Session Recordings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.