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

The User API from Border0 — 4 operation(s) for user.

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

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

This API exposes 5 operations across 4 paths, and defines 10 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.

5 operations 4 paths 10 schemas 2 GET1 POST2 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 User API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Border0_Token).

Paths & Operations 5

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

User 5
GET
/user/confirm/{token}
Confirm and activate user with a temporary token
get_user-confirm-token 1 param → 200401404500
GET
/user/{user_id}
Show user info by user ID
get_user-user-id 1 param → 200401403404500
PUT
/user/{user_id}
Update an existing user
put_user-user-id 1 param body → 200400401403404500
POST
/user
Register a new user
post_user body → 204400500
PUT
/user/password
Update an existing (authenticated) user's account password
put_user-password body → 200400401403404500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are serializer.User (12 properties), serializer.SubscriptionLimit (9 properties), v1.createUserRequest (8 properties), serializer.Organization (7 properties). Each schema is shown below with its type and property counts.

v1.updateUserPasswordRequest
object
3 properties
v1.BaseErrorResponse
object
2 properties
serializer.Subscription
object
3 properties
datatypes.JSONMap
object
serializer.User
object
12 properties
serializer.SubscriptionLimit
object
9 properties
serializer.Plan
object
1 property
v1.createUserRequest
object
8 properties 3 required
serializer.Organization
object
7 properties
v1.updateUserRequest
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

border0-user-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 Session API
Border0 Sessions API
Border0 Socket API
Where this information came from

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