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

Notte Sessions API

Create and manage remote cloud browser sessions.

Notte Sessions API is one of 7 APIs that Notte 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 8 operations across 7 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.4.40.

Requests are made against a single base URL, https://api.notte.cc.

8 operations 7 paths 5 schemas 1 DELETE5 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.4.40
Base URL
https://api.notte.cc
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Notte Sessions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Notte API key obtained from the Notte Console (https://console.notte.cc), passed as a Bearer token in the Authorization header. The SDK reads the NOTTEAPIKEY e…

Paths & Operations 8

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

Sessions 8

Create and manage remote cloud browser sessions.

POST
/sessions/start
Session Start
sessionStart body → 200
GET
/sessions
List Sessions
listSessions 3 params → 200
GET
/sessions/{session_id}
Session Status
sessionStatus 1 param → 200
DELETE
/sessions/{session_id}/stop
Session Stop
sessionStop 1 param → 200
GET
/sessions/{session_id}/debug
Session Debug Info
sessionDebugInfo 1 param → 200
GET
/sessions/{session_id}/replay
Session Replay
sessionReplay 1 param → 200
GET
/sessions/{session_id}/cookies
Session Cookies Get
sessionCookiesGet 1 param → 200
POST
/sessions/{session_id}/cookies
Session Cookies Set
sessionCookiesSet 1 param body → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are SessionStartRequest (16 properties), SessionResponse (14 properties), Cookie (8 properties), SetCookiesRequest (1 property). Each schema is shown below with its type and property counts.

SessionStartRequest
object
16 properties
CookiesResponse
object
1 property
Cookie
object
8 properties
SessionResponse
object
14 properties
SetCookiesRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

notte-sessions-api-openapi.yml Raw ↑

Other APIs Notte publishes across the network.

Notte Agents API
Notte Health API
Notte Page API
Notte Personas API
Notte Scraping API
Notte Vaults API
Where this information came from

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