PUT and PATCH update an existing document by ID. You only need to send the fields you want to change — unmentioned fields are left unchanged.
PUT /api/data/:collectionName/:id
Typically used for full logical updates. Send only the fields you intend to change; fields you omit are left unchanged.
PATCH /api/data/:collectionName/:id
Explicitly signals a partial update. Semantically equivalent to PUT in urBackend — both merge changes into the existing document without replacing unmentioned fields.
Nested field updates using dot notation are supported.
For example, sending
"meta.views": 105 updates only the views key inside the meta object
without affecting any other keys in meta.Required Header
x-api-key: sk_live_… by default. pk_live_… is accepted only when the collection has RLS enabled and the request includes Authorization: Bearer <accessToken>.
Path Parameters
The name of the collection containing the document.
The MongoDB ObjectId string of the document to update.
Request Body
A JSON object containing the fields to update and their new values.RLS Behavior
When usingpk_live with RLS enabled, urBackend fetches the existing document and compares its owner field against the authenticated user’s ID. If they don’t match, the request is rejected with 403.
Response Fields
true when the update succeeded.The updated document with all current field values.
Human-readable status message.
Code Examples
Success Response
Errors
| Status | Cause |
|---|---|
400 Bad Request | Schema validation failed |
401 Unauthorized | Missing/invalid API key, or missing Bearer token on an RLS-enabled collection |
403 Forbidden | pk_live without RLS, owner field mismatch, or attempt to change the owner field |
404 Not Found | No document with that ID exists |
