// HTTP method
DELETE
Request removal of the association between the target URI and its current resource.
UnsafeIdempotent in intended effect
Idempotency
Idempotent in intended effect: after one or more successful requests, the target remains removed. Later responses may differ, such as 204 followed by 404.
Common use cases
- Remove a resource.
- Revoke a named credential resource.
- Delete a collection member while preserving the collection.
Common mistakes
- Creating additional side effects on every retry.
- Returning a body with 204 No Content.
- Using DELETE as an arbitrary command with unclear target semantics.
Request
DELETE /api-keys/key_123 HTTP/1.1
Authorization: Bearer …Response
HTTP/1.1 204 No Content// GET STARTED
Design and test a DELETE operation.
Define the contract in API Designer, then execute it with Cloud Runner or Browser Runner.