Medusa V2 Admin API Reference

How to Obtain the JWT Token

To obtain a JWT token, send a request to the authentication route passing it the user's email and password in the request body.

If authenticated successfully, an object is returned in the response with the property token being the JWT token.

How to Use the JWT Token

To use the JWT token, pass it in the authorization bearer header.

If you're using the JS SDK, the login method automatically sets the token for you and passes it to subsequent requests. You can also set the token manually using the client.setToken method.

2. API Token#

Use a user's secret API Token to send authenticated requests.

How to Create an API Token for a User

Create the API key token either from the Medusa Admin or using the Create API Key API Route.

An api_key object is returned in the response. You need its token property.

How to Use the API Token

You pass the API Key token as a base64 token in the authorization header. For example, when sending a request in JavaScript:

3. Cookie Session ID#

When you authenticate a user and create a cookie session ID for them, the cookie session ID is passed automatically when sending the request from the browser, or with tools like Postman.

How to Obtain the Cookie Session#

To obtain a cookie session ID, you must have a JWT token for bearer authentication.

Then, if you're using the JS SDK, make sure the auth.type configuration is set to session, as explained in the JS SDK configurations guide. The auth.login method will handle setting the session cookie and passing it in subsequent requests.

If you're not using the JS SDK, send a request to the session authentication API route. To view the cookie session ID, pass the -v option to the curl command.

If you send the cURL request, the headers will be logged in the terminal as well as the response. You should find in the headers a Cookie header.

How to Use the Cookie Session ID in cURL

If you're using the JS SDK, it will pass the cookie session with every request automatically after you use the auth.login method.

If you're not using the JS SDK, copy the value after connect.sid (without the ; at the end) and pass it as a cookie in subsequent requests.

If you're sending requests using JavaScript's Fetch API, you must pass the credentials option with the value include to all the requests you're sending.

If you've enabled HTTP Compression in your Medusa configurations, and you want to disable it for some requests, you can pass the x-no-compression header in your requests.

If you're using the JS SDK, every method accepts a headers parameter as the last parameter. You can pass in it custom headers, including the x-no-compression header.

Many API Routes accept a fields query that allows you to select which fields and relations should be returned in a record. Fields and relations are separated by a comma ,.

Fields Operator#

By default, only the selected fields and relations are returned in the response.

Before every field or relation, you can pass one of the following operators to change the default behavior:

• +: Add the field to the fields returned by default. For example, +title returns the title field along with the fields returned by default.
• -: Remove the field from the fields returned by default. For example, -title removes the title field from the fields returned by default.

Select Relations#

To select a relation, pass to fields the relation name prefixed by *.

Select Fields in a Relation#

The * prefix selects all fields of the relation's data model.

To select a specific field, pass a .<field> suffix instead of the * prefix. For example, variants.title.

To specify multiple fields, pass each of the fields with the <relation>.<field> format, separated by a comma.

Strings#

You can pass a string value in the form of <parameter_name>=<value>.

If the string has any characters other than letters and numbers, you must encode them. For example, if the string has spaces, you can encode the space with + or %20.

When using the JS SDK, you can pass the string directly to the query parameter. The JS SDK will encode the string for you.

You can use tools like this one to learn how a value can be encoded.

Integers#

You can pass an integer value in the form of <parameter_name>=<value>.

Boolean#

You can pass a boolean value in the form of <parameter_name>=<value>.

Date and DateTime#

You can pass a date value in the form <parameter_name>=<value>. The date must be in the format YYYY-MM-DD.

You can also pass the time using the format YYYY-MM-DDTHH:MM:SSZ. Please note that the T and Z here are fixed.

Array#

Array filters can be passed either as:

• <parameter_name>[]=<value1>,<value2>, separating the values by a comma.
• <parameter_name>[]=<value1>&<parameter_name>[]=<value2>, passing each value as a separate query parameter. You can also specify the index of each parameter in the brackets <parameter_name>[0]=<value>.

When using the JS SDK, you can pass the array directly to the query parameter. The JS SDK will handle the rest.

Object#

Object parameters must be passed as separate query parameters in the form <parameter_name>[<key>]=<value>.

When using the JS SDK, you can pass the object directly to the query parameter. The JS SDK will handle the rest.

limit is used to specify the maximum number of items to be returned in the response. offset is used to specify how many items to skip before returning the resulting records.

Use the offset query parameter to change between pages. For example, if the limit is 50, at page 1 the offset should be 0; at page 2 the offset should be 50, and so on.

Response Fields#

In the response of listing API Routes, aside from the records retrieved, there are three pagination-related fields returned:

• limit: the maximum number of items that can be returned in the response.
• offset: the number of items that were skipped before the records in the result.
• count: the total number of available items of this data model. It can be used to determine how many pages are there.

For example, if the count is 100 and the limit is 50, divide the count by the limit to get the number of pages: 100/50 = 2 pages.

Sort Order#

The order field (available on API Routes that support pagination) allows you to sort the retrieved items by a field of that item.

By default, the sort direction is ascending. To change it to descending, pass a dash (-) before the field name.