magento Authentication API
Endpoints for obtaining integration tokens for admin and customer users. Token-based authentication issues a Bearer token that must be included in the Authorization header of subsequent requests.
magento Authentication API is one of 16 APIs that magento publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 2.4.
Requests are made against a single base URL, https://{store_domain}/rest/{store_code}.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
magento Authentication API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Bearer token obtained from the /V1/integration/admin/token or /V1/integration/customer/token endpoint. Include in the Authorization header as "Bearer {token}".
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.
Endpoints for obtaining integration tokens for admin and customer users. Token-based authentication issues a Bearer token that must be included in the Authorization header of subs…
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Error (2 properties), CustomerTokenRequest (2 properties), AdminTokenRequest (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from magento 12
Other APIs magento publishes across the network.