Page History

...

• A link to the related customer resource (e.g., GET /customers/1).
• A link to each related item on the orderorder (e.g., GET /orders/1234/lineItems/1).
• A link to the shipping vendor's packing tracking informationinformation (e.g., GET https://tools.usps.com/go/TrackConfirmAction?tLabels=9374859697090312216947).
• A link that allows the visitor to cancel the orderorder (e.g., DELETE /orders/1234).
• A link that allows the visitor to see all open ordersorders (e.g., GET /customers/1/openOrders).

Each of these links are capable of changing the application state (i.e., the resource content as it exists in the client at a specific point in time). Note, however, that some of these links simply request additional resource content (i.e., via the GET method) but links are also used to make changes to the resource state (such as cancelling the order). The important point is that all of these links were provided by the server at the time the resource was requested. This implies that the server used the resource state (i.e., the resource content as it exists in the server at a specific point in time) to determine which application state links were applicable when the request was made.

...