Update a dataset
PUT/api/v1/dataset/:pk
Update a dataset
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 412
- 422
- 500
Dataset changed
Bad request
Unauthorized
Forbidden
Not found
A concurrent save on this dataset won a database lock race, so this conditional request could not be applied. The client's If-Match token is NOT proven stale: unlike a 412, the correct action is to retry the SAME request (with backoff; a few attempts, then surface the conflict) rather than refetch the entity for a new token.
The dataset changed since the version identified by the request's If-Match header; the update was not applied. The token is stale: refetch the entity to pick up the current version before retrying — retrying the same request unchanged will fail again (contrast the retryable 409 above).
Could not process entity
Fatal error