Indelible Certify API¶
The Indelible Certify API is a hosted HTTP service that lets publishers certify articles with the Indelible Standard without running any blockchain infrastructure themselves. You send it an API key and some content; it computes the content's IPFS CID, queues the commit/reveal transactions, and signs them with a platform key to which your organization has delegated.
This is NOT a blocking API. A request to create an attestation is validated, written to a pending row, and returns 202 Accepted immediately. A separate worker process signs, submits, and confirms the transactions in the background. Poll for status or wait for confirmation asynchronously.
sequenceDiagram
actor CMS as CMS / Publisher
participant API as Certify API
participant Worker as tx_worker
participant Chain
CMS->>API: POST /v1/attestations
API->>API: validate + compute CID
API-->>CMS: 202 { id, status: pending }
API->>Worker: enqueue commit task
Worker->>Chain: commit(saltedHash)
Note over Worker: wait ≥ 60s
Worker->>Chain: reveal(...)
CMS->>API: GET /v1/attestations/:id
API-->>CMS: 200 { status: confirmed, attestationIndex }
Before You Start¶
Every attestation is attributed to your organization's authority address, the wallet you control. The platform key never becomes the author; it only pays gas and submits transactions on your behalf, via an on-chain delegation.
Onboarding therefore has one prerequisite outside the API itself: your authority address must call delegate(platformAddress) on the TAANQ contract for each chain you intend to publish on. Your Indelible contact will give you the platform address to delegate to and confirm once the delegation is verified - requests made before that will fail with 409 no_active_delegation.
Want to get started?
Reach out to Indelible for your API key and more information.
Continue to:
- Authentication — API keys and request signing.
- Attestations — creating and polling attestations.
- Errors — error codes and how to handle them.