Hanzo
OpenapiLabel

Dispose of this tenant's expired assertions, whole records only

Applies this tenant's retention, and only this tenant's. It is bounded three ways, each a compliance property rather than a convenience.

POST /v1/label/dispose

Addresshttps://api.hanzo.ai/v1/label/dispose
MethodPOST
OperationriskDisposeLabels
AuthAuthorization: Bearer $HANZO_API_KEY

Applies this tenant's retention, and only this tenant's.

It is bounded three ways, each a compliance property rather than a convenience. It refuses a boundary younger than the platform floor, because a label can be the input to an adverse action and five years is what the retention ledger holds such a record for. It never touches a record under litigation hold. And it disposes of whole records rather than redacting fields.

It removes the derived columnar copy BEFORE the record, and refuses the whole disposal if the warehouse cannot be reached. The other order would leave rows in the warehouse that nothing can identify any more, which is a disposal that did not happen and says it did.

Request

1 field, body application/json (required).

FieldInTypeRequiredDescription
beforebodystringBefore disposes of assertions WRITTEN before this instant, RFC 3339.

Response

StatusBodyMeaning
200riskDisposeOutok

200 body — 7 fields.

FieldInTypeAlwaysDescription
beforebodystringBefore echoes the retention boundary that was applied, RFC 3339 in UTC, as this plane parsed it from the request.
disposedbodyintegerDisposed is how many whole records were removed.
heldbodyintegerHeld is how many records inside the boundary were kept under litigation hold.
oldestbodystringOldest is the WRITE time of the oldest assertion this tenant still holds after the sweep, RFC 3339, and it is omitted exactly when nothing remains at all.
remainingbodyintegerRemaining is how many disposable records are still older than the boundary.
restoredbodyintegerRestored is how many records this sweep had already removed from the derived columnar copy and then did NOT dispose of, because a litigation hold arrived…
totalbodyintegerTotal and Oldest describe what the tenant still holds afterwards, so a disposal that removed nothing is distinguishable from a tenant that had nothing.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


Label API · All Hanzo APIs · Interactive reference

How is this guide?

On this page