Real API, test data, your own key. Access is granted by hand while the sandbox is closed.

Request sandbox access

Tell us what you want to test and we send a key. A person reads it, so say which product category you are working on.

Keys are issued manually. There is no self-serve signup and no card.

What's included

Sandbox API key

Your own itg_test_… key, minted on signup
Full /v1/sign access

Battery, textile, electronics, steel schemas
Public /v1/verify

No key needed, verify from anywhere
Onboarding checklist

Guided first sign + first verify flow

Quick start preview

1 Sign an artifact

curl -X POST "$Intygio_API/v1/sign" \
  -H "X-API-Key: itg_test_…" \
  -H "Content-Type: application/json" \
  -d '{"schema_id":"battery","payload":{"id":"urn:eu:dpp:battery:ACME-EV-001","mfg":"ACME","mod":"EV-80","cat":"ev","kwh":75.0,"co2":45.2,"co2_class":"B","chem":"NMC811","recycled_co":16,"recycled_li":6,"mfg_date":"2026-01-01","soh":100,"iss":"EU-DPP-SP-00001","iat":1748736000}}'

Response

{ "token": "0001…", "schema_id": "battery", "signed_at": "2026-…" }

2 Verify anywhere, no key needed

curl -X POST "$Intygio_API/v1/verify" \
  -H "Content-Type: application/json" \
  -d '{"token":"<token from sign response>"}'

Response

{ "status": "AUTHENTIC", "signer_id": "EU-DPP-SP-…" }

AUTHENTIC means the signature holds and the payload is unchanged since the signer signed it. It does not mean the values are correct. Completeness is returned beside the status, never inside it.