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

Customers can either be created when they register through the Store APIs, or created by the admin using the Admin APIs.These API routes allow admin users to manage customers in their store.

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

Tagged areas include Customers. 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 9 paths, and defines 17 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 9 paths 17 schemas 3 DELETE7 GET9 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 Customers 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 9 paths, the API surfaces 19 operations — 3 DELETE, 7 GET, 9 POST. Each is listed below with its method, path, parameters, and response codes.

Customers 19

Customers can either be created when they register through the Store APIs, or created by the admin using the Admin APIs. These API routes allow admin users to manage customers in…

GET
/admin/customers
List Customers
GetCustomers 19 params → 200400401404409422500
POST
/admin/customers
Create Customer
PostCustomers 1 param body → 200400401404409422500
GET
/admin/customers/{id}
Get a Customer
GetCustomersId 2 params → 200400401404409422500
POST
/admin/customers/{id}
Update a Customer
PostCustomersId 2 params body → 200400401404409422500
DELETE
/admin/customers/{id}
Delete a Customer
DeleteCustomersId 1 param → 200400401404409422500
GET
/admin/customers/{id}/addresses
List Addresses
GetCustomersIdAddresses 14 params → 200400401404409422500
POST
/admin/customers/{id}/addresses
Add a Customer Address
PostCustomersIdAddresses 2 params body → 200400401404409422500
GET
/admin/customers/{id}/addresses/{address_id}
List Addresses
GetCustomersIdAddressesAddress_id 3 params → 200400401404409422500
POST
/admin/customers/{id}/addresses/{address_id}
Update a Customer's Address
PostCustomersIdAddressesAddress_id 3 params body → 200400401404409422500
DELETE
/admin/customers/{id}/addresses/{address_id}
Remove an Address from Customer
DeleteCustomersIdAddressesAddress_id 3 params → 200400401404409422500
POST
/admin/customers/{id}/customer-groups
Manage Customer Groups of Customer
PostCustomersIdCustomerGroups 2 params body → 200400401404409422500
POST
/store/customers
Register Customer
PostCustomers 4 params body → 200400401404409422500
GET
/store/customers/me
Get Logged-in Customer
GetCustomersMe 4 params → 200400401404409422500
POST
/store/customers/me
Update Customer
PostCustomersMe 4 params body → 200400401404409422500
GET
/store/customers/me/addresses
List Customer's Addresses
GetCustomersMeAddresses 14 params → 200400401404409422500
POST
/store/customers/me/addresses
Create Address for Logged-In Customer
PostCustomersMeAddresses 4 params body → 200400401404409422500
GET
/store/customers/me/addresses/{address_id}
Get Customer's Address
GetCustomersMeAddressesAddress_id 5 params → 200400401404409422500
POST
/store/customers/me/addresses/{address_id}
Update Customer's Address
PostCustomersMeAddressesAddress_id 5 params body → 200400401404409422500
DELETE
/store/customers/me/addresses/{address_id}
Remove Customer's Address
DeleteCustomersMeAddressesAddress_id 5 params → 200400401404409422500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are AdminCustomerAddress (18 properties), StoreCustomerAddress (18 properties), AdminCustomer (16 properties), StoreCreateCustomerAddress (14 properties). Each schema is shown below with its type and property counts.

AdminCustomerAddressResponse
object
The address's details.
1 property 1 required
AdminCustomer
object
The customer's details.
16 properties 9 required
Error
object
3 properties
AdminCustomerGroup
object
The customer group's details.
6 properties 6 required
AdminCustomerAddress
object
The customer's address.
18 properties 18 required
CustomerGroupInCustomerFilters
object
Filter by customer groups to get their associated customers.
5 properties 5 required
AdminCustomerResponse
object
The customer's details.
1 property 1 required
AdminBatchLink
object
A batch operation to manage the associations between two entities.
2 properties
StoreCustomerAddressListResponse
object
The paginated list of customer addresses.
5 properties 4 required
StoreCreateCustomerAddress
object
The address's details.
14 properties
StoreUpdateCustomer
object
The details to update in the customer.
5 properties
StoreCustomerAddressResponse
object
The address's details.
1 property 1 required
StoreCreateCustomer
object
The details of the customer to create.
6 properties
StoreCustomer
object
The customer's details.
13 properties 8 required
StoreUpdateCustomerAddress
object
The properties to update in the address.
14 properties
StoreCustomerAddress
object
The customer address's details
18 properties 18 required
StoreCustomerResponse
object
The customer's details.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

medusa-customers-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 Draft Orders API
Where this information came from

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