Resources, Not Actions

A product manager describes the checkout feature in three sentences:

"A shopper places an order containing several products, then checks its delivery status. Support cancels an order that has not shipped. Finance issues a refund and tracks whether it succeeded."

Seven nouns appear there: shopper, order, product, delivery status, support, refund, and finance.

How many of them should become URLs?

Making every noun a resource adds operations that this task may not need. Too few resources can also make useful actions difficult. For the scope in this example, we will use two: Order and