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 Multi-Factor Authentication API

Multi-factor authentication (MFA) adds an extra layer of security to admin accounts by requiring additional verification factors during login, such as a TOTP code or a recovery code.These API routes allow admin users to manage their MFA factors, challenges, and recovery codes.

Medusa Multi-Factor Authentication API is one of 82 APIs that Medusa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Multi-Factor Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 5 operations across 4 paths, and defines 1 schema. 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.

5 operations 4 paths 1 schemas 1 GET4 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
License
Resource Areas
1

Authentication & Security 4

Medusa Multi-Factor Authentication 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 5

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

Multi-Factor Authentication 5

Multi-factor authentication (MFA) adds an extra layer of security to admin accounts by requiring additional verification factors during login, such as a TOTP code or a recovery co…

POST
/auth/mfa/challenges/{id}/verify
Verify a Multi-Factor Authentication (MFA) Challenge
PostMfaChallengesIdVerify 1 param body → 200400401404409422500
GET
/auth/mfa/factors
List Multifactor Authentication (MFA) Factors
GetMfaFactors → 200400401404409422500
POST
/auth/mfa/factors
Start Multi-Factor Authentication (MFA) Factor Enrollment
PostMfaFactors body → 200400401404409422500
POST
/auth/mfa/factors/{id}/verify
Verify and Enable a Multi-Factor Authentication (MFA) Factor
PostMfaFactorsIdVerify 1 param body → 200400401404409422500
POST
/auth/mfa/recovery-codes
Generate Multi-Factor Authentication (MFA) Recovery Codes
PostMfaRecoveryCodes body → 200400401404409422500

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (3 properties). Each schema is shown below with its type and property counts.

Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medusa-multi-factor-authentication-api-openapi.yml Raw ↑

Other APIs Medusa publishes across the network.

Medusa GraphQL API
Medusa MCP Remote Server
Medusa Api Keys API
Medusa Auth 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
Where this information came from

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