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 Fulfillments API

A fulfillment is created for items in an order, return, exchanges, or claims to deliver items to/from the customer.These API routes allow admin users to manage fulfillments.

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

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

This API exposes 3 operations across 3 paths, and defines 12 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.

3 operations 3 paths 12 schemas 3 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 Fulfillments 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 3

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

Fulfillments 3

A fulfillment is created for items in an order, return, exchanges, or claims to deliver items to/from the customer. These API routes allow admin users to manage fulfillments.

POST
/admin/fulfillments
Create Fulfillment
PostFulfillments 1 param body → 200400401404409422500
POST
/admin/fulfillments/{id}/cancel
Cancel a Fulfillment
PostFulfillmentsIdCancel 2 params → 200400401404409422500
POST
/admin/fulfillments/{id}/shipment
Create a Shipment for a Fulfillment
PostFulfillmentsIdShipment 2 params body → 200400401404409422500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are AdminFulfillment (17 properties), AdminFulfillmentAddress (16 properties), AdminCreateFulfillment (13 properties), AdminFulfillmentItem (11 properties). Each schema is shown below with its type and property counts.

AdminFulfillment
object
The fulfillment's details.
17 properties 17 required
AdminFulfillmentDeliveryAddress
object
The address to deliver the items to.
11 properties
Error
object
3 properties
AdminCreateFulfillmentShipment
object
Details of the shipment to create for a fulfillment.
1 property 1 required
AdminFulfillmentProvider
object
The fulfillment provider's details.
2 properties 2 required
AdminFulfillmentLabel
object
The details of a fulfillmet's shipment label.
8 properties 8 required
AdminCreateFulfillment
object
The filfillment's details.
13 properties 6 required
AdminFulfillmentItem
object
The details of a fulfillment's item.
11 properties 11 required
AdminFulfillmentAddress
object
An address's details.
16 properties 16 required
AdminFulfillmentResponse
object
A fulfillment's details.
1 property 1 required
AdminCreateFulfillmentItem
object
An item to fulfill.
6 properties 4 required
AdminCreateFulfillmentLabel
object
Details of the fulfillment label to create.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medusa-fulfillments-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 Fulfillments 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.