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

Border0 Session API

The Session API from Border0 — 3 operation(s) for session.

Border0 Session API is one of 15 APIs that Border0 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://api.border0.com/api/v1.

4 operations 3 paths 7 schemas 3 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.border0.com/api/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Border0 Session API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Border0_Token).

Paths & Operations 4

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

Session 4
GET
/session/{socket_id}/{session_id}/session_log
Download a socket's session recording
get_session-socket-id-session-id-session-log 3 params → 200401404500
GET
/session/{socket_id}/{session_id}
Show a socket's session info by socket ID and session ID
get_session-socket-id-session-id 2 params → 200400401404500
PUT
/session/{socket_id}/{session_id}
Kill a socket's session with socket ID, session ID and json payload with killed flag
put_session-socket-id-session-id 2 params body → 200400401404500
GET
/session/{socket_id}
Show all sessions from a socket by socket ID, including active and killed sessions
get_session-socket-id 1 param → 200401404500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are serializer.SessionLogPublic (24 properties), metadata.IPMetadata (8 properties), restful.ErrorResponse (2 properties), serializer.Recording (2 properties). Each schema is shown below with its type and property counts.

v1.BaseErrorResponse
object
2 properties
serializer.SessionLogPublic
object
24 properties
serializer.SessionLogMetadata
object
1 property
serializer.Recording
object
2 properties
metadata.IPMetadata
object
8 properties
restful.ErrorResponse
object
2 properties
v1.sessionLogRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

border0-session-api-openapi.yml Raw ↑

Other APIs Border0 publishes across the network.

Border0 Audit Actions API
Border0 Client API
Border0 Connect API
Border0 Login API
Border0 Mtls-Ca API
Border0 Organization API
Border0 Organizations API
Border0 Policies API
Border0 Policy API
Border0 Sessions API
Border0 Socket API
Border0 Stats API
Where this information came from

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