* initialized next.js project * finished markdown sections * added operation schema component * change page metadata * eslint fixes * fixes related to deployment * added response schema * resolve max stack issue * support for different property types * added support for property types * added loading for components * added more loading * type fixes * added oneOf type * removed console * fix replace with push * refactored everything * use static content for description * fixes and improvements * added code examples section * fix path name * optimizations * fixed tag navigation * add support for admin and store references * general enhancements * optimizations and fixes * fixes and enhancements * added search bar * loading enhancements * added loading * added code blocks * added margin top * add empty response text * fixed oneOf parameters * added path and query parameters * general fixes * added base path env variable * small fix for arrays * enhancements * design enhancements * general enhancements * fix isRequired * added enum values * enhancements * general fixes * general fixes * changed oas generation script * additions to the introduction section * added copy button for code + other enhancements * fix response code block * fix metadata * formatted store introduction * move sidebar logic to Tags component * added test env variables * fix code block bug * added loading animation * added expand param + loading * enhance operation loading * made responsive + improvements * added loading provider * fixed loading * adjustments for small devices * added sidebar label for endpoints * added feedback component * fixed analytics * general fixes * listen to scroll for other headings * added sample env file * update api ref files + support new fields * fix for external docs link * added new sections * fix last item in sidebar not showing * move docs content to www/docs * change redirect url * revert change * resolve build errors * configure rewrites * changed to environment variable url * revert changing environment variable name * add environment variable for API path * fix links * fix tailwind settings * remove vercel file * reconfigured api route * move api page under api * fix page metadata * fix external link in navigation bar * update api spec * updated api specs * fixed google lint error * add max-height on request samples * add padding before loading * fix for one of name * fix undefined types * general fixes * remove response schema example * redesigned navigation bar * redesigned sidebar * fixed up paddings * added feedback component + report issue * fixed up typography, padding, and general styling * redesigned code blocks * optimization * added error timeout * fixes * added indexing with algolia + fixes * fix errors with algolia script * redesign operation sections * fix heading scroll * design fixes * fix padding * fix padding + scroll issues * fix scroll issues * improve scroll performance * fixes for safari * optimization and fixes * fixes to docs + details animation * padding fixes for code block * added tab animation * fixed incorrect link * added selection styling * fix lint errors * redesigned details component * added detailed feedback form * api reference fixes * fix tabs * upgrade + fixes * updated documentation links * optimizations to sidebar items * fix spacing in sidebar item * optimizations and fixes * fix endpoint path styling * remove margin * final fixes * change margin on small devices * generated OAS * fixes for mobile * added feedback modal * optimize dark mode button * fixed color mode useeffect * minimize dom size * use new style system * radius and spacing design system * design fixes * fix eslint errors * added meta files * change cron schedule * fix docusaurus configurations * added operating system to feedback data * change content directory name * fixes to contribution guidelines * revert renaming content * added api-reference to documentation workflow * fixes for search * added dark mode + fixes * oas fixes * handle bugs * added code examples for clients * changed tooltip text * change authentication to card * change page title based on selected section * redesigned mobile navbar * fix icon colors * fix key colors * fix medusa-js installation command * change external regex in algolia * change changeset * fix padding on mobile * fix hydration error * update depedencies
4.0 KiB
description
| description |
|---|
| Learn how to install the Medusa JS Client in a storefront. Medusa JS Client provides easy access to the Medusa API from a client written in TypeScript. |
Medusa JS Client
The Medusa JS Client provides easy access to the Medusa API from a client written in TypeScript. This reference guides you to learn what methods the client has and how you can use them.
This client can be use as an alternative to directly interacting with the REST APIs.
Installation
To install the Medusa JS Client run the following command:
npm install @medusajs/medusa-js
Usage
Import Medusa as a default import and initiate it:
import Medusa from "@medusajs/medusa-js"
const medusa = new Medusa()
Troubleshooting: Could not find a declaration file for module '@medusajs/medusa-js'
If you import @medusajs/medusa-js in your code and see the following TypeScript error:
Could not find a declaration file for module '@medusajs/medusa-js'
Make sure to set moduleResolution in your tsconfig.json to nodenext or node:
{
"compilerOptions": {
"moduleResolution": "nodenext",
// ...
},
// ...
}
How to Use this Reference
You'll find in the sidebar of this reference names of different resources. These resources are properties in the Medusa instance you initialize and you can access them directly using the instance. Then, you'll be able to access the methods or nested resources within those resources.
For example, to create a new customer you can access the create method under the customers property of your client:
import Medusa from "@medusajs/medusa-js"
const medusa = new Medusa()
// use method
medusa.customers.create({
// data
})
The customers resource also has another resource addresses nested inside it with its own method that you can access similarly:
medusa.customers.addresses.addAddress({
// data
})
Authentication
Authentication can be achieved in two ways using the medusa-js client: either by utilizing API keys or by using cookie based authentication. Each method has its own unique use case.
Using API keys
API keys can only be used for admin functionality in Medusa since only users of the admin system have API keys. Refer to the Configuration section to learn how to add the API key to requests.
You can follow this guide to learn how to create an API key for an admin user.
Using cookies
Authentication using cookies is done automatically by Axios, which is used within the Medusa JS Client, when authenticating using the auth endpoints. After authentication, all subsequent calls will be authenticated.
Configuration
Initialize with config object
The package can be initialized with several options:
const medusa = new Medusa({
maxRetries: 3,
baseUrl: "https://api.example.com",
})
| Option | Default | Description |
|---|---|---|
maxRetries |
0 |
The amount of times a request is retried. |
baseUrl |
'http://localhost:9000' |
The url to which requests are made to. |
apiKey |
'' |
Optional API key used for authenticating admin requests. |
publishableApiKey |
'' |
Optional publishable API key used for storefront requests. You can create a publishable API key either using the admin APIs or the Medusa admin. |