Medusa Return Reasons API
A return reason is a possible reason that an item is returned from the customer, such as when returning an item.These API routes allow admin users to manage return reasons.
Medusa Return Reasons API is one of 82 APIs that Medusa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Return Reasons. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 7 operations across 4 paths, and defines 9 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Medusa Return Reasons 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 7
Across 4 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
A return reason is a possible reason that an item is returned from the customer, such as when returning an item. These API routes allow admin users to manage return reasons.
Schemas 9
The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are StoreReturnReason (7 properties), AdminReturnReason (7 properties), AdminReturnReasonListResponse (5 properties), AdminCreateReturnReason (5 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 Medusa 12
Other APIs Medusa publishes across the network.
This is an independent, third-party profile of Medusa Return Reasons 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.