Choose HTTP Methods by Contract
Distinguish safe, idempotent, and unsafe REST operations before choosing an HTTP method.
The method is the contract A method choice is not style. It is the public reliability contract for retries, caches, clients, and operators. Safe methods should not change user-visible state. Idempotent methods should tolerate repetition against the same target. Unsafe methods need duplicate protection when business impact matters. The three-question test Ask: is the operation read-only, can the same request be repeated, and does the client name the resource? If any answer is fuzzy, the endpoint probably needs a different resource boundary, an idempotency key, or an asynchronous operation resource.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in