Test and live keys
Use sk_test_… on the testbox and sk_live_… in production. Secrets are shown once and stored as hashes; revoked keys fail closed. Scope each app to full or restricted access.
Ask for the fields and agreements you need, let the person approve on their phone, then read live, verified values. Nothing sensitive to store on your side.
Authenticate server-side with your secret key. The person approves on their own device, and you get a signed result plus live fields.
Name the fields and agreements your app needs. You get a request id and a QR to show.
They see exactly what you asked for and approve with a fingerprint. Poll or wait for the webhook.
Read the current value under the grant, with how each field was proven. Store nothing sensitive.
POST /v1/auth/connect/start { "auth_app_id": "app_live_9Qx…", "required_field_ids": ["legal_name", "email"], "agreement_ids": ["tos_v3"] } → 201 Created { "request_id": "req_7f3a…", "qr_url": "https://…", "expires_in": 300 }
GET /v1/sign/status?request_id=req_7f3a… → 200 OK { "status": "approved", "vault_id": "vlt_c91e…", "grant_id": "gr_2291…", "agreements_signed": ["tos_v3"], "signature": "ed25519:7f3a…c91e" }
GET /v1/company/users/vlt_c91e… → 200 OK · read logged under gr_2291 { "legal_name": { "value": "Diego Ramírez", "status": "verified" }, "email": { "value": "diego@…", "status": "verified" }, "grant": { "scope": "read", "revocable": true } }
Subscribe to grants, updates, signatures and revocations. When a customer changes a field or pulls access, you know in the same second.
Quickstarts and references for the SDK, auth flow and Company API.
Read the docsDrop-in libraries to start connect requests, verify signatures and handle grants.
Get the SDKSecret keys, REST JSON, restricted scopes per app. Same power as the portal.
API referenceSubscribe to sign, grant, update and revoke events to keep your records current.
Event catalogTutorials and patterns: verified onboarding, field requests, agreement re-sign and more.
Start learningThe open protocol, plus the source-available ledger, gateway and SDK, under the Atrustos org.
Browse reposUse sk_test_… on the testbox and sk_live_… in production. Secrets are shown once and stored as hashes; revoked keys fail closed. Scope each app to full or restricted access.
The protocol (message formats, cryptography and signing rules) is open source under Apache 2.0. The core ledger, gateway and SDK are source-available, so anyone can audit exactly how Atrustos works.
Grab the docs, create a test key and connect your first verified customer.
Photography: Unsplash