Skip to main content
The Vendor API is the seller’s surface. Every route is scoped to one seller through the member authentication and x-seller-id mechanism described in API conventions. A seller can never read or mutate another seller’s data.

Account and team

Products and offers

Products are shared master records. Updates stage a change request rather than writing directly, and the list shows products the seller created plus published, unrestricted products.

Catalog taxonomy (read-only)

GET /vendor/product-categories[/:id], /vendor/product-tags[/:id], /vendor/product-types[/:id], /vendor/product-attributes[/:id], and /vendor/collections[/:id]. Use POST /vendor/product-categories/:id/products and POST /vendor/collections/:id/products to place own products.

Orders and fulfillment

Order edits, returns, claims, exchanges

Full RMA suites exist per domain, following the same action pattern Medusa uses (begin → stage item/shipping actions → request → confirm):
  • POST /vendor/order-edits + /:id/request|confirm|items|shipping-method sub-routes
  • GET/POST /vendor/returns + /:id/request-items|dismiss-items|receive-items|receive|shipping-method sub-routes
  • GET/POST /vendor/claims + /:id/claim-items|inbound|outbound sub-routes
  • GET/POST /vendor/exchanges + /:id/inbound|outbound sub-routes
  • GET /vendor/return-reasons[/:id], GET /vendor/refund-reasons[/:id]

Payments

Payouts

Inventory and stock locations

Shipping

Pricing, promotions, customers

Configuration and misc

Next steps

Store API