/v1/deleteREAD / WRITEDelete a record
Hard-deletes a record by id, freeing its slot in the collection.
Frees the record's slot and unlinks it from its collection immediately — this is a hard delete, not a tombstone. Use Soft-delete a record instead if you want the record to stop appearing in search while keeping its audit history and slot reserved.
Request body
idintegerrequiredId of the record to delete.
collectionstringoptionalCollection the record belongs to. Optional at the HTTP level (falls back to the node's default namespace) — pass it explicitly; every Cloud project starts with zero collections.
Response fields
successbooleanoptionaltrue on success.
log_indexintegeroptionalRaft log index of the committed delete. Present only in cluster mode.
The Python SDK's delete() returns None on success and raises on
failure — it discards success/log_index rather than returning them.
The TypeScript SDK's delete() returns the full response object above.
Errors
| Status | code | Meaning |
|---|---|---|
400 | validation_error | Malformed request body. |
401 | unauthorized | Missing or invalid API key. |
403 | forbidden | The key's scope doesn't include read_write. |
404 | record_not_found, collection_not_found | The record or collection doesn't exist. |
500 | internal_error | Commit or audit-chain failure. |
Related endpoints
- Soft-delete a record — tombstone instead of hard-delete
- Insert a record
- Get a record