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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Authlete

Authlete Federation Endpoint API

API endpoints for implementing OpenID Federation using Authlete.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

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

2 operations 2 paths 19 schemas 2 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
Apache 2.0
Resource Areas
1

Authentication & Security 1

Authlete Federation Endpoint 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 2

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

Federation Endpoint 2

API endpoints for implementing OpenID Federation using Authlete.

POST
/api/{serviceId}/federation/configuration
Process Entity Configuration Request
federation_configuration_api 1 param body → 200400401403500
POST
/api/{serviceId}/federation/registration
Process Federation Registration Request
federation_registration_api 1 param body → 200400401403500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are client (104 properties), client_extension (6 properties), federation_registration_response (5 properties), federation_configuration_response (4 properties). Each schema is shown below with its type and property counts.

client
object
104 properties
jwe_alg
stringnull
this is the 'alg' header value for encrypted JWT tokens. Depending upon the context, this refers to key transport scheme to be used by the client and by the se…
federation_configuration_response
object
4 properties
fapi_mode
string
application_type
string
The application type. The value of this property affects the validation steps for a redirect URI. See the description about redirectUris property for more deta…
federation_registration_response
object
5 properties
client_registration_type
string
Values for the clientregistrationtypes RP metadata and the clientregistrationtypessupported OP metadata that are defined in [OpenID Connect Federation 1.0](htt…
client_auth_method
string
The client authentication method that the client application declares that it uses at the token endpoint. This property corresponds to tokenendpointauthmethod…
client_extension
object
6 properties
response_type
string
tagged_value
object
2 properties
federation_registration_request
object
2 properties
jws_alg
stringnull
The signature algorithm for JWT. This value is represented on 'alg' attribute of the header of JWT. it's semantics depends upon where is this defined, for inst…
result
object
2 properties
grant_type
string
The grant type of the access token when the access token was created.
pair
object
2 properties
subject_type
string
The subject type that the client application requests. Details about the subject type are described in [OpenID Connect Core 1.0, 8. Subjct Identifier Types](ht…
client_type
string
The client type, either CONFIDENTIAL or PUBLIC. See [RFC 6749, 2.1. Client Types](https://datatracker.ietf.org/doc/html/rfc6749section-2.1) for details.
jwe_enc
stringnull
This is the encryption algorithm to be used when encrypting a JWT on client or server side. Depending upon the context, this refers to encryption done by the c…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

authlete-federation-endpoint-api-openapi.yml Raw ↑

Other APIs Authlete publishes across the network.

Authlete Authorization Endpoint API
AE Profile APIs.io
Authlete CIBA API
AE Profile APIs.io
Authlete Client Management API
AE Profile APIs.io
Authlete Device Flow API
AE Profile APIs.io
Authlete Dynamic Client Registration API
AE Profile APIs.io
Authlete Grant Management Endpoint API
AE Profile APIs.io
Authlete Hardware Security Key API
AE Profile APIs.io
Authlete Introspection Endpoint API
AE Profile APIs.io
Authlete Jose Object API
AE Profile APIs.io
Authlete JWK Set Endpoint API
AE Profile APIs.io
Authlete Lifecycle API
AE Profile APIs.io
Authlete Native SSO API
AE Profile APIs.io
#Federation Endpoint
← Back to A APIs
API Details
ID
authlete:authlete-federation-endpoint-api
Base URL
https://us.authlete.com
Docs
https://docs.authlete.com/
Provider
Authlete
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=authlete-federation-endpoint-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/authlete-federation-endpoint-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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