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

Authlete CIBA API

API endpoints for implementing Client-Initiated Backchannel Authentication (CIBA).

Authlete CIBA API is one of 21 APIs that Authlete publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 4 base URLs: https://us.authlete.com, https://jp.authlete.com, https://eu.authlete.com, https://br.authlete.com.

4 operations 4 paths 21 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.16
Base URL
https://us.authlete.com
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

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

  • bearer — Authenticate every request with a Service Access Token or Organization Token. Set the token value in the Authorization: Bearer header. Service Access Token: Sc…

Paths & Operations 4

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

CIBA 4

API endpoints for implementing Client-Initiated Backchannel Authentication (CIBA).

POST
/api/{serviceId}/backchannel/authentication
Process Backchannel Authentication Request
backchannel_authentication_api 1 param body → 200400401403500
POST
/api/{serviceId}/backchannel/authentication/issue
Issue Backchannel Authentication Response
backchannel_authentication_issue_api 1 param body → 200400401403500
POST
/api/{serviceId}/backchannel/authentication/fail
Fail Backchannel Authentication Request
backchannel_authentication_fail_api 1 param body → 200400401403500
POST
/api/{serviceId}/backchannel/authentication/complete
Complete Backchannel Authentication
backchannel_authentication_complete_api 1 param body → 200400401403500

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are backchannel_authentication_response (37 properties), backchannel_authentication_complete_response (28 properties), backchannel_authentication_complete_request (18 properties), backchannel_authentication_request (8 properties). Each schema is shown below with its type and property counts.

delivery_mode
string
backchannel_authentication_complete_request
object
18 properties 3 required
grant_scope
object
2 properties
grant
object
3 properties
backchannel_authentication_issue_request
object
1 property 1 required
grant_management_action
string
The grant management action of the device authorization request. The grantmanagementaction request parameter is defined in [Grant Management for OAuth 2.0](htt…
backchannel_authentication_fail_request
object
4 properties 2 required
backchannel_authentication_request
object
8 properties 1 required
authz_details
object
The authorization details. This represents the value of the authorizationdetails request parameter in the preceding device authorization request which is defin…
1 property
backchannel_authentication_response
object
37 properties
backchannel_authentication_fail_response
object
4 properties
tagged_value
object
2 properties
result
object
2 properties
backchannel_authentication_issue_response
object
7 properties
dynamic_scope
object
2 properties
pair
object
2 properties
backchannel_authentication_complete_response
object
28 properties
property
object
3 properties
scope
object
5 properties
cimd_options
object
Options for [OAuth Client ID Metadata Document](https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/) (CIMD). These options allow per…
3 properties
authorization_details_element
object
7 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

authlete-ciba-api-openapi.yml Raw ↑

Other APIs Authlete publishes across the network.

Authlete Authorization Endpoint API
Authlete Client Management API
Authlete Device Flow API
Authlete Dynamic Client Registration API
Authlete Federation Endpoint API
Authlete Grant Management Endpoint API
Authlete Hardware Security Key API
Authlete Introspection Endpoint API
Authlete Jose Object API
Authlete JWK Set Endpoint API
Authlete Lifecycle API
Authlete Native SSO API
Where this information came from

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