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 Client API

The Client API from Border0 — 6 operation(s) for client.

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

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

This API exposes 6 operations across 6 paths, and defines 8 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.

6 operations 6 paths 8 schemas 3 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.border0.com/api/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 6

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

Client 6
GET
/client/auth/org/{slug}
Authenticate a client with headers against organization email
get_client-auth-org-slug 7 params → 302400500
GET
/client/cda/get_token
Fetches a client token in exchange for a device authorization code previously authorized via the (OAuth2.0) client device authorization flow
get_client-cda-get-token 1 param → 200400500
GET
/client/resources
Show socket client resources
get_client-resources → 200401500
POST
/client/ai_assistants/database
Generate SQL query from an input that has a question and database schemas
post_client-ai-assistants-database body → 200400401500
POST
/client/cda/authorize
Authorizes a device authorization code.
post_client-cda-authorize 1 param → 200400500
POST
/client/device_authorizations
Posts details for a device initiating a new (OAuth2.0) client device authorization flow in exchange for a one-time-use code
post_client-device-authorizations body → 200400500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are v1.clientResourceData (15 properties), v1.postClientDeviceAuthorizationResponse (7 properties), llm.DatabaseAgentInput (4 properties), v1.getClientDeviceAuthorizationResponse (4 properties). Each schema is shown below with its type and property counts.

v1.postClientDeviceAuthorizationRequest
object
2 properties
llm.DatabaseAgentInput
object
4 properties
v1.BaseErrorResponse
object
2 properties
v1.getClientDeviceAuthorizationResponse
object
4 properties
v1.postClientDeviceAuthorizationResponse
object
7 properties
v1.clientResourceData
object
15 properties
restful.ErrorResponse
object
2 properties
v1.clientResourceResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

border0-client-api-openapi.yml Raw ↑

Other APIs Border0 publishes across the network.

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

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