Cheat Sheet logoCheat Sheet Today
REST API Methods and Idempotency/Avoid mutations on GET

Do not track writes in the same endpoint contract.

Back to sheetBrowse commands
Sign in to save
Section: Idempotency patterns

Avoid mutations on GET

text
text
Avoid: GET /posts/123/mark-read
Explanation

A GET endpoint should not change business state. Use a dedicated write route if you need to record events or acknowledgements.

View in sheet →

Learn the surrounding workflow

Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.

Compare commandsView fixes

Related commands

Same sheet · prioritizing Idempotency patterns
Use an idempotency key for POST
Deduplicate retryable create requests.
OpenIn sheethttpsame section
Client-chosen resource ID via PUT
Make resource creation naturally idempotent.
OpenIn sheethttpsame section
Use set-style PATCH operations
Favor deterministic patches.
OpenIn sheetjsonsame section
GET retrieves data
Read without changing server state.
OpenIn sheethttp1 tag match
POST creates or triggers processing
Submit a new resource or command-like workflow.
OpenIn sheethttp
PUT replaces state
Send a full replacement representation.
OpenIn sheethttp