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

Steel Sessions API

Launch, inspect, and release cloud browser sessions.

Steel Sessions API is one of 4 APIs that Steel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sessions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 6 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.steel.dev/v1, http://localhost:3000/v1.

7 operations 6 paths 6 schemas 4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.steel.dev/v1
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Steel Sessions API declares 1 security scheme for authenticating requests. An API key is passed in the header as Steel-Api-Key (SteelApiKey). By default, every request must be authenticated.

  • SteelApiKey — API key issued from app.steel.dev. Pass it in the Steel-Api-Key request header. Self-hosted instances may run without auth.

Paths & Operations 7

Across 6 paths, the API surfaces 7 operations — 4 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Sessions 7

Launch, inspect, and release cloud browser sessions.

POST
/sessions
Create a browser session
createSession body → 200
GET
/sessions
List sessions
listSessions → 200
GET
/sessions/{sessionId}
Get session details
getSession 1 param → 200
GET
/sessions/{sessionId}/context
Get session context
getSessionContext 1 param → 200
GET
/sessions/{sessionId}/live-details
Get session live details
getSessionLiveDetails 1 param → 200
POST
/sessions/{sessionId}/release
Release a session
releaseSession 1 param → 200
POST
/sessions/release
Release all sessions
releaseSessions → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are SessionDetails (18 properties), CreateSession (16 properties), SessionLiveDetails (5 properties), SessionContext (4 properties). Each schema is shown below with its type and property counts.

ReleaseSession
CreateSession
object
Options for launching a browser session.
16 properties
SessionContext
object
Captured browser state for the session.
4 properties
SessionLiveDetails
object
5 properties
SessionDetails
object
18 properties 4 required
Dimensions
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

steel-dev-sessions-api-openapi.yml Raw ↑

Other APIs Steel publishes across the network.

Steel Files API
Steel Quick Actions API
Steel Session Actions API
Where this information came from

This is an independent, third-party profile of Steel Sessions 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.