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

Medusa Auth API

Auth API routes allow you to manage an admin user's authentication.

Medusa Auth API is one of 82 APIs that Medusa 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, API documentation, an API reference, and authentication docs.

This API exposes 19 operations across 18 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 2.19.0.

Requests are made against 2 base URLs: http://localhost:9000, https://api.medusajs.com.

19 operations 18 paths 10 schemas 2 DELETE2 GET15 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.19.0
Base URL
https://{medusa-backend-domain}
Authentication
HTTP Basic, HTTP Bearer, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 4

Medusa Auth API declares 4 security schemes for authenticating requests. It accepts HTTP basic authentication (api_token). It accepts HTTP bearer tokens (jwt_token). An API key is passed in the cookie as connect.sid (cookie_auth). It accepts HTTP bearer tokens (reset_password).

Paths & Operations 19

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

Auth 19

Auth API routes allow you to manage an admin user's authentication.

DELETE
/auth/mfa/factors/{id}
Disable a Multi-Factor Authentication (MFA) Factor
DeleteMfaFactorsId 1 param body → 200400401404409422500
POST
/auth/session
Set Authentication Session
PostSession → 200400401404409422500
DELETE
/auth/session
Delete Authentication Session
DeleteSession → 200400401404409422500
POST
/auth/token/refresh
Refresh Authentication Token
PostAdminAuthTokenRefresh → 200400401404409422500
GET
/auth/user/providers
List Auth Providers for Admin Users
GetUserProviders → 200400401404409422500
POST
/auth/user/{auth_provider}
Authenticate User
PostActor_typeAuth_provider 1 param body → 200400401404409422500
POST
/auth/user/{auth_provider}/callback
Validate Authentication Callback
PostActor_typeAuth_providerCallback 1 param → 200400401404409422500
POST
/auth/user/{auth_provider}/register
Retrieve Registration JWT Token
PostActor_typeAuth_provider_register 1 param body → 200400401404409422500
POST
/auth/user/{auth_provider}/reset-password
Generate Reset Password Token for Admin User
PostActor_typeAuth_providerResetPassword 1 param body → 201400401404409422500
POST
/auth/user/{auth_provider}/update
Reset an Admin User's Password
PostActor_typeAuth_providerUpdate 1 param body → 200400401404409422500
POST
/auth/customer/emailpass/verification/confirm
Verify the Customer's Email
PostActor_typeAuth_providerVerificationConfirm body → 200400401404409422500
GET
/auth/customer/providers
List Auth Providers for Customers
GetCustomerProviders → 200400401404409422500
POST
/auth/customer/{auth_provider}
Authenticate Customer
PostActor_typeAuth_provider 1 param body → 200400401404409422500
POST
/auth/customer/{auth_provider}/callback
Validate Authentication Callback
PostActor_typeAuth_providerCallback 1 param → 200400401404409422500
POST
/auth/customer/{auth_provider}/register
Retrieve Registration JWT Token
PostActor_typeAuth_provider_register 1 param body → 200400401404409422500
POST
/auth/customer/{auth_provider}/reset-password
Generate Reset Password Token for Customer
PostActor_typeAuth_providerResetPassword 1 param body → 201400401404409422500
POST
/auth/customer/{auth_provider}/update
Reset a Customer's Password
PostActor_typeAuth_providerUpdate 1 param body → 200400401404409422500
POST
/auth/verification/confirm
Confirm Customer Verification
PostVerificationConfirm body → 200400401404409422500
POST
/auth/verification/request
Request Customer Verification
PostVerificationRequest body → 201400401404409422500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are StoreCustomerAddress (18 properties), StoreCustomer (13 properties), AdminUser (9 properties), AuthProvider (4 properties). Each schema is shown below with its type and property counts.

AuthProvider
object
The public information of a registered auth provider instance. This is safe to expose to unauthenticated clients and never contains provider options or secrets.
4 properties 4 required
AdminUser
object
The user's details.
9 properties 9 required
AuthResponse
object
The authentication's details.
1 property 1 required
Error
object
3 properties
AuthProvidersListResponse
object
The response of listing the auth providers available.
1 property 1 required
AuthCallbackResponse
object
The authentication's details.
1 property 1 required
AuthAdminSessionResponse
object
The authenticated user's details.
1 property 1 required
StoreCustomer
object
The customer's details.
13 properties 8 required
StoreCustomerAddress
object
The customer address's details
18 properties 18 required
AuthStoreSessionResponse
object
The authenticated customer's details.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medusa-auth-api-openapi.yml Raw ↑

Other APIs Medusa publishes across the network.

Medusa GraphQL API
Medusa MCP Remote Server
Medusa Api Keys API
Medusa [auth Provider] API
Medusa Campaigns API
Medusa Carts API
Medusa Claims API
Medusa Collections API
Medusa Currencies API
Medusa Customer Groups API
Medusa Customers API
Medusa Draft Orders API
Where this information came from

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