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

Fusio Authorization API

The Fusio Authorization API is the OAuth2 authorization server Fusio ships in the product. It issues and refreshes access tokens across the authorization_code, client_credentials, password and refresh_token grants, resolves the identity behind a token, and revokes tokens. It is advertised through RFC 8414 authorization-server metadata, RFC 9728 protected-resource metadata and an OpenID Connect discovery document served from the same instance.

Fusio Authorization API is one of 5 APIs that Fusio publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authorization, Authentication, OpenID Connect, REST API, and Security. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, authentication docs, and a GitHub repository.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version 1.

Requests are made against a single base URL, https://demo.fusio-project.org.

2 operations 2 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1
Base URL
https://demo.fusio-project.org
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Fusio Authorization API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (app) using the clientCredentials and authorizationCode flows, exposing 2 scopes.

Paths & Operations 2

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

authorization 2
GET
/authorization/whoami
Returns user data of the current authenticated user
authorization.getWhoami → 2004XX5XX
POST
/authorization/revoke
Revoke the access token of the current authenticated user
authorization.revoke → 2004XX5XX

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Backend_App (12 properties), Backend_User (11 properties), Backend_Token (7 properties), Common_Message (3 properties). Each schema is shown below with its type and property counts.

Backend_App
object
This object represents an app to access the API on-behalf of a user
12 properties
Backend_Token
object
This object represents a token, this an access token which was requested by a user
7 properties
Backend_User
object
This object represents a user
11 properties
Common_Message
object
Common error message
3 properties
Common_Metadata
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fusio-authorization.json Raw ↑

Other APIs Fusio publishes across the network.

Fusio Backend API
Fusio Consumer API
Fusio Worker API
Fusio System API
Where this information came from

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