Adding custom routes in medusa

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

The cool part about medusa is that we get the option to customize a lot of things. One of them is routes. This article will show you how to add a store and an admin route.
When it comes to these routes, we add all of them to our server project. Go ahead and open your server project in your favorite IDE.
Custom routes are added in the src/app directory. In our case, we'll add an index.js.
import { Router } from 'express';
export default () => {
const router = Router();
router.get('/store/ping', (req, res) => {
res.json({
message: 'Pong from the server!',
});
});
return router;
};
This will inject a new route under store/ping, which the storefront can use.
Note: the store prefix is according to medusa conventions. You can modify it and return a direct route.
Now let's restart our server and test the endpoint in Insomnia.

There you go, it works!
We can use this same principle to prefix admin routes.
However, the route is now prefixed with admin.
import { Router } from 'express';
export default () => {
const router = Router();
router.get('/admin/ping', (req, res) => {
res.json({
message: 'Pong from the server!',
});
});
return router;
};
You can go ahead and try this endpoint as well.

And that's it. We now learned how to add custom routes to our medusa server. These routes will come in handy while exploring other options for our admin and front end.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter