POST
/v1/soft-deleteREAD / WRITESoft-delete a record
Tombstones a record so it stops appearing in search, without freeing its slot or losing audit history.
Tombstones the record: it stops appearing in search results, but its slab slot and audit history are retained — unlike Delete a record, which frees the slot immediately. Use soft-delete when you want the record gone from results but still want a complete history of what the collection contained.
Request body
idintegerrequiredId of the record to tombstone.
collectionstringoptionalCollection the record belongs to. Optional at the HTTP level — pass it explicitly.
Response fields
successbooleanoptionaltrue on success.
log_indexintegeroptionalRaft log index of the committed tombstone. Present only in cluster mode.
The Python SDK's soft_delete() returns None on success and raises on
failure. The TypeScript SDK's softDelete() 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
- Delete a record — hard delete, frees the slot immediately
- Insert a record