REST API BEST PRACTISES #3

Is Using Sub-Resources for Actions in REST API a Trap?

How do you structure actions in a RESTful way?

All of my REST API BEST PRACTISES articles are added in this library.

Photo by Sincerely Media on Unsplash

Some developers argue by using sub-resources ( POST /orders/{orderId}/cancel), claiming it keeps things clean and intuitive.

Others warn that this approach can rapidly spiral into a rigid, unmaintainable mess.

So 🤔,

are sub-resources the key to a well-structured API 😎?

— — — — — — — — —-OR— — — — — — — — — —

are they secretly sabotaging your architecture😳?

Let’s Breakdown below 👇

Your claps 👏 help the article reach more developers 👀 on Medium, and your comments make me to keep writing✍️. If you blocked by medium paywall, Guess what? 🎉 Surprice is in this link.

What Sub-Resources for Actions?

At its core, RESTful APIs focus on resources — nouns like orders, users, and products.