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

Strapi Admin Authentication API

Authentication endpoints for administrator accounts used to access the Strapi admin panel.

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

Tagged areas include Admin Authentication. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against a single base URL, https://{host}.

5 operations 5 paths 4 schemas 5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.0.0
Base URL
https://{host}
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • adminBearerAuth — Admin JWT token obtained from the /admin/login endpoint. Include as Authorization: Bearer {token}.

Paths & Operations 5

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

Admin Authentication 5

Authentication endpoints for administrator accounts used to access the Strapi admin panel.

POST
/admin/login
Login to admin panel
adminLogin body → 200400
POST
/admin/renew-token
Renew admin JWT token
adminRenewToken body → 200400
POST
/admin/forgot-password
Request admin password reset
adminForgotPassword body → 200400
POST
/admin/reset-password
Reset admin password
adminResetPassword body → 200400
POST
/admin/register-admin
Register the first administrator
registerFirstAdmin body → 200400

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are AdminUser (10 properties), AdminRole (5 properties), Error (2 properties), AdminAuthResponse (1 property). Each schema is shown below with its type and property counts.

AdminRole
object
5 properties
Error
object
2 properties
AdminUser
object
10 properties
AdminAuthResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

strapi-admin-authentication-api-openapi.yml Raw ↑

Other APIs Strapi publishes across the network.

Strapi Webhooks
Strapi Admin Roles API
Strapi Admin Users API
Strapi API Tokens API
Strapi Authentication API
Strapi Content Entries API
Strapi Content Manager API
Strapi Content Types API
Strapi Permissions API
Strapi Roles API
Strapi Transfer Tokens API
Strapi Upload API
Where this information came from

This is an independent, third-party profile of Strapi Admin Authentication 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.