The last of the four CRUD methods — and one that deserves a bit of extra thought. In this video we add a DELETE endpoint and look at why idempotency matters more here than anywhere else. *You'll learn:* - How to delete a record with GlideRecord and return HTTP 204 (No Content) - What idempotency means and why it applies to DELETE - Why a repeated delete should return 204, not 404 *Chapters:* - 0:00 Introduction - 0:38 Concept - 1:20 Demo - 2:24 Outro *GitHub:* https://github.com/jnichols-servicenow/SN2026-Vehicles-API *Links:* - HTTP semantics — DELETE (RFC 9110) — https://www.rfc-editor.org/rfc/rfc9110#section-9.3.5 - REST API design — idempotency — https://restfulapi.net/idempotent-rest-apis/ - ServiceNow docs — Scripted REST API good practices — https://www.servicenow.com/docs/r/api-reference/rest-api-explorer/scripted-rest-good-practices.html *Series navigation:* - Previous: 07 — PUT and PATCH - Next: 09 — HTTP methods - Full playlist: https://www.youtube.com/playlist?list=PLrhqGp3sUzhvp1sfgP8OZjXRxKOP\_cyBU