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

Corbado ConnectTokens API

Short-lived tokens authorizing Corbado Connect frontend flows.

Corbado ConnectTokens API is one of 7 APIs that Corbado publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://backendapi.corbado.io/v2.

4 operations 2 paths 8 schemas 1 DELETE1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://backendapi.corbado.io/v2
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Corbado ConnectTokens API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication. The username is the project ID (e.g. pro-1234567890) and the password is the API secret, both issued from the Corbado Developer Pane…

Paths & Operations 4

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

ConnectTokens 4

Short-lived tokens authorizing Corbado Connect frontend flows.

POST
/connectTokens
Create ConnectToken
connectTokenCreate body → 200400
GET
/connectTokens
List ConnectTokens
connectTokenList 4 params → 200401
PATCH
/connectTokens/{connectTokenID}
Update ConnectToken
connectTokenUpdate 1 param body → 200404
DELETE
/connectTokens/{connectTokenID}
Delete ConnectToken
connectTokenDelete 1 param → 200404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ConnectToken (6 properties), ErrorRsp (5 properties), GenericRsp (4 properties), ConnectTokenCreateReq (3 properties). Each schema is shown below with its type and property counts.

ConnectToken
object
6 properties 2 required
ConnectTokenCreateReq
object
3 properties 1 required
ConnectTokenList
object
2 properties 2 required
ConnectTokenUpdateReq
object
1 property
RequestData
object
2 properties
GenericRsp
object
4 properties
Paging
object
3 properties
ErrorRsp
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

corbado-connecttokens-api-openapi.yml Raw ↑

Other APIs Corbado publishes across the network.

Corbado Exports API
Corbado Identifiers API
Corbado PasskeyEvents API
Corbado Passkeys API
Corbado Sessions API
Corbado Users API
Where this information came from

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