-
Notifications
You must be signed in to change notification settings - Fork 152
CRUD Delete Single item
When you perform a delete operation, the operation may be immediate or not (e.g., it could require some post processing).
To delete a single item you MUST issue a DELETE request against the single item (e.g., .../v1/employees/123 to delete employee 123).
- MAY provide the ETag value in order to state that it should only be deleted IF the ETag is the correct one (see concurrency section for details)
- SHOULD return HTTP 204 (No Content) if the deletion succeeded
- SHOULD return HTTP 202 (Accepted) if the deletion is accepted but is not immediate
- in that case the Location header should provide a link to where the client can poll for the final result of the operation
- MUST return 404 if the resource was not found
This project is distributed under the terms of the EUPL FOSS license
REST Resources Design Workflow
REST Resources Single items and collections
REST Resources Many to many Relations
REST Resources Relations expansion
HTTP Status Codes Success (2xx)
HTTP Status Codes Redirection (3xx)
HTTP Status Codes Client Error (4xx)
HTTP Status Codes Server Error (5xx)
Pagination Out of range/bounds
Long-running Operations Example
Concurrency vs Delete operation
Caching and conditional requests About
Caching and conditional requests Rules
Caching and conditional requests HTTP headers
Error handling Example with a single error
Error handling Example with multiple errors
Error handling Example with parameters
Error handling Example with additional metadata
Bulk operations HTTP status codes
Bulk operations Resources naming convention
Bulk operations Creation example
Bulk operations Update example
Bulk operations Create and update example
File upload Simple file upload
File upload Simple file upload example
File upload Complex file upload
File upload Complex file upload example
REST Security General recommendations
REST Security Insecure direct object references