Every resource we built used GlideRecord — the JavaScript did all the work. So why does the HTTP method matter? In this video we answer that question. *You'll learn:* - What "safe" and "idempotent" mean in the context of HTTP methods - How method semantics affect caching, retries, and network-layer behaviour - Why using the right method matters even when the wrong one would technically work *Chapters:* - 0:00 Introduction - 0:38 The contract - 1:25 Safety and idempotency - 2:45 The bottom line *GitHub:* https://github.com/jnichols-servicenow/SN2026-Vehicles-API *Links:* - HTTP semantics (RFC 9110) — https://www.rfc-editor.org/rfc/rfc9110 - MDN — HTTP request methods — https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods - MDN — Idempotent — https://developer.mozilla.org/en-US/docs/Glossary/Idempotent *Series navigation:* - Previous: 08 — DELETE - Next: 10 — Versioning - Full playlist: https://www.youtube.com/playlist?list=PLrhqGp3sUzhvp1sfgP8OZjXRxKOP\_cyBU