Create or replace an item
PUT/api/v1/collections/:collection_id/items/:key
Writes data at key: 201 when the key was free, 200 when it replaced an item. tags replace the bag when sent and leave it alone when omitted. data is at most 64 KB as JSON and must satisfy the collection's schema. A precondition (If-Match or expected_version) names a version of an existing item, so it is 404 for a free key.
Request
Responses
- 200
- 201
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
Item replaced
Item created
Invalid request — a query parameter or body field the operation does not declare, or a value that fails validation
Authentication required
Insufficient permissions
Not found
The item has moved past the version this write read (VERSION_CONFLICT, with meta.current_version), or the write would exceed the project's storage_bytes quota (QUOTA_STORAGE_EXCEEDED). Nothing is written.
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there