v1.0.0 · Production

Blockchain-backed record integrity in 3 API calls.

The Certyo API lets you ingest records, anchor them on Polygon via Merkle-tree batching, and cryptographically verify authenticity — all through a simple REST interface.

The Happy Path

The shortest route from zero to a verified on-chain record. Three calls, ~70 seconds end to end.

Get your credentials

Your Certyo team will provision a tenantId, clientId, and an X-API-Key. Keep the API key in a secure vault — it is only shown once.

Ingest a record

Send a single record to the ingestion endpoint. You get an immediate 202 Accepted with a content hash.

curl -X POST https://www.certyos.com/api/v1/records \
  -H "X-API-Key: ${CERTYO_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "acme-corp",
    "database": "production",
    "collection": "orders",
    "recordId": "order-12345",
    "recordPayload": { "amount": 299.99, "currency": "USD" }
  }'

Verify it on-chain

After ~60 seconds (batch accumulation + Polygon confirmation), verify the record against its on-chain Merkle root.

curl -X POST https://www.certyos.com/api/v1/verify/record \
  -H "X-API-Key: ${CERTYO_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "acme-corp",
    "database": "production",
    "collection": "orders",
    "recordId": "order-12345",
    "payload": { "amount": 299.99, "currency": "USD" }
  }'

Where to next

Quickstart

Follow the full tutorial — from your first API key to an on-chain proof, with explanations at every step.

Guides

Deep-dives on authentication, ingestion patterns, verification, and status polling.

API Reference

Complete reference for the 15 public endpoints: request/response shapes, status codes, examples.

Code Samples

Copy-paste examples in curl, JavaScript, Python, Go, and C# for every core endpoint.

What Certyo actually does

Certyo provides a cryptographic guarantee that a record existed at a point in time and has not been tampered with. Under the hood:

Records you submit are hashed (SHA-256) and accumulated into batches.
Each batch's hashes form a Merkle tree. The tree root is a single 32-byte fingerprint covering all records in the batch.
The Merkle root is pinned to IPFS and anchored on the Polygon blockchain in a single transaction — so thousands of records share the cost of one on-chain write.
Verification recomputes the hash of your payload, walks the Merkle proof up to the root, and checks the root against the Polygon smart contract.

If all three match, the record is mathematically proven to be authentic. No trust in Certyo required.