Find related blog posts below

Want to know more about Medusa

[Medusa](https://medusajs.com/) is an open source headless commerce platform built using Node.js. It aims to provide developers with a great experience and limitless customization capabilities.

The core of Medusa is the headless server. It exposes a [set of APIs](https://docs.medusajs.com/api/store/auth/) that the other 2 components, admin and storefront, can use to connect to the server and access or manipulate data.

In this tutorial, you’ll learn how to create custom endpoints on your Medusa server for both the storefront and admin.

## Prerequisites

This tutorial assumes you already have a Medusa server installed. If not, you can follow the [Quickstart guide](https://docs.medusajs.com/quickstart/quick-start) to get started in a few minutes.

## Overview

Custom endpoints reside under the `src/api` directory in your Medusa Backend. To define a new endpoint, you can add the file `index.js` under the `src/api` directory. This file should export a function that returns an Express router.

Your endpoint can be under any path you wish.

### **Storefront Endpoint**

By Medusa’s conventions, all Storefront REST APIs are prefixed by `/store`. For example, the `/store/products` lets you retrieve the products to display them on your storefront.

### Admin Endpoint

By Medusa’s conventions, all Admin REST APIs are prefixed by `/admin`. For example, the `/admin/products` lets you retrieve the products to display them on your Admin.

## Implementation

To create a new endpoint, start by creating a new file in `src/api` called `index.js`. At its basic format, `index.js` should look something like this:

```jsx
import { Router } from "express"

export default () => {
  const router = Router()

  router.get("/hello", (req, res) => {
    res.json({
      message: "Welcome to Your Store!",
    })
  })

  return router
}
```

This endpoint is accessible under the path `/hello`. If you want to create an endpoint for the storefront and follow Medusa’s conventions you can prefix the path with `/store`:

```jsx
router.get("/store/hello", (req, res) => {
```

Similarly, you can create an endpoint for the admin and follow Medusa’s conventions by prefixing the path with `/admin`:

```jsx
router.get("/admin/hello", (req, res) => {
```

## Making Endpoints Accessible from the Admin

If you’re customizing the admin dashboard or creating your own, you need to use the `cors` library. An `OPTIONS` request should be added for each route and handle the requests with the `cors` library.

First, you need to import your Medusa’s configurations along with the `cors` library:

```jsx
import cors from "cors"
import { projectConfig } from "../../medusa-config"
```

Then, create an object that holds the CORS configurations:

```jsx
const corsOptions = {
  origin: projectConfig.admin_cors.split(","),
  credentials: true,
}
```

Finally, for each route you add, create an `OPTIONS` request:

```jsx
router.options("/admin/hello", cors(corsOptions))
router.get("/admin/hello", (req, res) => {
  //...
})
```

## Multiple Endpoints

### **Same File**

You can add more than one endpoints in `src/api/index.js`:

```jsx
router.get("/admin/hello", (req, res) => {
  res.json({
    message: "Welcome to Your Store!",
  })
})

router.get("/admin/bye", (req, res) => {
  res.json({
    message: "Come back again!",
  })
})
```

### Multiple Files

Alternatively, you can add multiple files for each endpoint or set of endpoints for readability and easy maintenance.

To do that with the previous example, first, create the file `src/api/hello.js` with the following content:

```jsx
export default (router) => {
  router.get("/admin/hello", (req, res) => {
    res.json({
      message: "Welcome to Your Store!",
    })
  })
}
```

You export a function that receives an Express router as a parameter and adds the endpoint `admin/hello` to it.

Next, create the file `src/api/bye.js` with the following content:

```jsx
export default (router) => {
  router.get("/admin/bye", (req, res) => {
    res.json({
      message: "Come back again!",
    })
  })
}
```

Again, you export a function that receives an Express router as a parameter and adds the endpoint `admin/bye` to it.

Finally, in `src/api/index.js` import the two functions at the beginning of the file:

```jsx
import helloRoute from "./hello"
import byeRoute from "./bye"
```

and in the exported function, call each of the functions passing them the Express router:

```jsx
export default () => {
  const router = Router()

  helloRoute(router)
  byeRoute(router)

  return router
}
```

## Use Services

[Services](https://docs.medusajs.com/advanced/backend/services/create-service) in Medusa bundle a set of functionalities related to a model into one class. Then, you can use that class anywhere in your backend. For example, you can use the `ProductService` to retrieve products or perform operations like creating or updating a product.

You can retrieve any registered service in your endpoint using `req.scope.resolve` passing it the service’s registration name.

Here’s an example of an endpoint that retrieves the count of products in your store:

```jsx
router.get("/admin/products/count", (req, res) => {
  const productService = req.scope.resolve("productService")

  productService.count().then((count) => {
    res.json({
      count,
    })
  })
})
```

The `productService` has a `count` method that returns a Promise. This Promise resolves to the count of the products. You return a JSON of the product count.

## Protected Routes for

Protected routes are routes that should be accessible by logged-in users only.

To make a route protected, first, import the `authenticate` middleware:

```jsx
import authenticate from "@medusajs/medusa/dist/api/middlewares/authenticate"
```

Then, add the middleware to your route:

```jsx
router.get("/store/products/count", authenticate(), (req, res) => {
  //...
})
```

Now, only authenticated customers or users can access this endpoint.

### Accessing Current Customer

You can get the logged-in customer’s ID using `req.user`:

```jsx
const id = req.user.customer_id
```

To get the customer’s details, you can use the `customerService`:

```jsx
const id = req.user.customer_id
const customerService = req.scope.resolve("customerService")

const customer = await customerService.retrieve(id)
```

### Accessing Current User

You can get the logged-in user ID using `req.user`:

```jsx
const id = req.user.userId
```

To get the user’s details, you can use the `userService`:

```jsx
const id = req.user.userId
const userService = req.scope.resolve("userService")

const user = await userService.retrieve(id)
```

## Route Parameters

The routes you create receive 2 parameters. The first one is the absolute path to the root directory that your server is running from. The second one is an object that has your plugin's options. If your API route is not implemented in a plugin, then it will be an empty object.

```jsx
export default (rootDirectory, pluginOptions) => {
  const router = Router()

  //...
}
```

## What’s Next?

Endpoints are just one essential part of Medusa’s architecture. Here are more resources to learn more about Medusa’s server and how to customize it:

- [What are subscribers and how to create them?](https://docs.medusajs.com/advanced/backend/subscribers/create-subscriber)
- [What are services and how to create them?](https://docs.medusajs.com/advanced/backend/services/create-service)
- [How to create a payment provider?](https://docs.medusajs.com/advanced/backend/payment/how-to-create-payment-provider/)

> Should you have any issues or questions related to Medusa, then feel free to reach out to the Medusa team via [Discord](https://discord.gg/F87eGuwkTp).

How to Create Custom Endpoints in Medusa

In this tutorial, you’ll learn how to create a comic book store with Medusa and add important ecommerce features.

How to Create a Comic Book Online Store with Medusa, Gatsby, PayPal, and MeiliSearch

In this part, you’ll learn how to link orders to their respective stores in a marketplace.

Medusa Open Source Marketplace Part 2: Make Orders Vendor Specific


2021 has been quite overwhelming with all the interest we have received from the developer community - thanks a ton to all of you for that! Read below for a quick review of 2021 and a short glimpse into 2022.

## Highlights of 2021 :zap:️

###Product highlights:

- Fully open-source; from core and admin to starters and design system
- Created an onboarding flow that gets you up and running with only 2 commands
- Developing starters that allow you to spin up a full store with a Gatsby or Next.js frontend
- Building an extensive plugin library with integrations to Stripe, Contentful, Strapi, Algolia, Paypal, and many more
- Building out our documentation, incl. deployment guides, setup tutorials, plugin guides
- Migrating the project to Typescript

###Community highlights:

- Growing from 10 to +5,500 GitHub stars since our official launch 6 months ago
- Launching our community Discord and welcomed ~700 amazing members
- Hosting our first Hackathon and got 85 contributions to the core project

## What is to come in 2022 :crystal_ball:

###Medusa 2.0
We aim to launch Medusa 2.0 by the end of Q1. A first core foundation for this will be released with our new [Admin dashboard in January](https://www.medusajs.com/post/admin-redesign). We will share more details about the roadmap as we progress on our [Discord](https://discord.gg/F87eGuwkTp).
###Doubling down on community
Hackathon, conferences, merch store, video tutorials, and a heck of a lot more; community is king and we want to give back for all the contributions we have received through many more activities addressed specifically to our community.
###Medusa Cloud
It should not take much to deploy Medusa and although our product will always remain open-source and available for self-hosting, we want to make it a one-click experience to get started with a Medusa store - and don’t worry you will always own the code that powers your store so that when it is time to customize your can quickly take over.
Plenty of exciting things to happen. We cannot wait to show it all to you!
