Liccium Developer Portal
Redaction & Deletion API

deletion

Endpoint:https://b2c-api-main-737c477.zuplo.app

Permanent deletion (administrators, enabled declarers)

Fully delete one declaration

POST
https://b2c-api-main-737c477.zuplo.app
/v1/delete

Permanent deletion of one declaration by CID; there is no batch form. The declaration and its metadata leave active storage and every participating registry: it disappears from ISCC search, the metadata routes answer 410 with a minimal deletion marker (cid, iscc, status: deleted, deletedAt, authorizedBy, chain links), and the provenance chain shows the position as deleted. A protected recovery snapshot is kept for 90 days for disaster recovery only and is not reachable through any API.

Authorisation: administrator keys may delete any declaration; a declarer key may delete its own declarations only when deletion has been enabled for it. recursive: true deletes the whole supersedes chain of the CID and is accepted from administrator keys only. Irreversible; deleting an already deleted CID answers 200 with changed: false.

Fully delete one declaration › Request Body

  • cidstring · required

    Declaration id (cidV1). An ISCC is rejected.

  • reasonstring · maxLength: 500
  • recursiveboolean

    Administrators only: delete every declaration on the CID's supersedes chain.

    Default: false

Fully delete one declaration › Responses

Deleted, or already deleted (changed: false). For recursive: true the body is a ChainDeleteResult and 200 means every chain member was deleted or already carried a marker.

  • cidstring
  • okboolean
  • changedboolean

    false when the CID was already deleted

  • markerobject

    Public deletion marker. Contains no original metadata and no personal information.

  • declarerIdstring
  • effectsobject

    What each store reported: snapshot, marker, index, stats, iroh, rows, s3Versions

redactionstatus