SDK npm package is not published yet and API environments may be unavailable.View status
Platform Concepts

Issuance lifecycle

Documents in Ananke Labs follow a defined lifecycle from issuance to expiry. Understanding these states is essential for building correct integrations.

Lifecycle states

Both Ananke Trust and Ananke TCode documents share common lifecycle states:

StateMeaningVerification result
ActiveDocument is valid and currentvalid
SuspendedTemporarily paused — can be reinstatedsuspended
RevokedPermanently invalidated — cannot be reinstatedrevoked
ExpiredPast its validity periodexpired

State transitions

Valid transitions:

  • Active → Suspended — temporary hold (e.g., pending review)
  • Active → Revoked — permanent invalidation
  • Active → Expired — time-based expiry
  • Suspended → Active — reinstate after review
  • Suspended → Revoked — upgrade suspension to permanent revocation

Revoked and Expired are terminal states. Once a document reaches either state, it cannot be brought back to Active.

Ananke Trust lifecycle

Ananke Trust documents are managed via the POST /v1/trust/issuances/{id}/lifecycle endpoint, or using the SDK helper methods:

  • client.trust.documents.suspend(id)
  • client.trust.documents.revoke(id)
  • client.trust.documents.reactivate(id)

The lifecycle endpoint accepts an action string: suspend, revoke, reinstate, or expire.

Ananke TCode lifecycle

Ananke TCode stamps have dedicated endpoints for lifecycle actions:

  • POST /v1/tcode/stamps/{id}/suspend
  • POST /v1/tcode/stamps/{id}/revoke
  • POST /v1/tcode/stamps/{id}/reactivate

Replacement

Both Ananke Trust and Ananke TCode support document replacement — issuing a new version of an existing document while preserving the reference chain. Replacement creates a new document linked to the original. The original is typically revoked as part of the replacement.