Core Store API
Medusa's built-in store routes for products, carts, checkout, orders, and customers.
These are Medusa's own store routes. Waylo Commerce runs them as Medusa ships them, plus the company checkout rules it adds to carts through workflow hooks. Those rules' errors, such as permission_denied and company_not_active, aren't listed on these pages. This reference is built from Medusa's published spec for the release the backend runs, without the routes that need Medusa plugins or feature flags Waylo Commerce doesn't enable. The same authentication applies: a publishable API key on every route, and a customer token or session on routes that act for a customer.
Products
List and read products, with prices for a region.
Carts
Create and update carts, then complete them into orders.
Customers
The signed-in customer and their addresses.
Orders
The signed-in customer's orders.
Use the Send button only against a development backend, with test customers. Never enter a real customer's password or a production customer token on this site.
Code samples use Medusa's JS SDK (@medusajs/js-sdk), which works against any Waylo Commerce backend. Routes Waylo Commerce adds, such as companies, are in the Store API.
Change an employee's role POST
Errors: `last_owner`. Emits `employee.updated`.
Verify the Customer's Email POST
Verifies the customer's email using a token that is typically sent to their email address. This is used to confirm the customer's email during registration or authentication when [email verification is required](https://docs.medusajs.com/resources/commerce-modules/auth/auth-providers/emailpass). You can listen to the `auth.verification_requested` event in a subscriber and send an email to the customer with the verification token.