Developers
EnvironmentPRODUCTION
You are working against production. The switch mirrors the ENV pill in the topbar and namespaces every key, record and webhook you touch.
Sandbox, nothing there touches production or billing. Its vault demo-co/sandbox is free, gas is faucet-funded, and rr_test_… keys never work against production (nor the other way round).
Open documentationPUBLIC
developers.roxregister.com
Quickstarts with copy-paste snippets, the full API reference, error codes, the webhook event catalogue and JWS test vectors, public by design, no key required to read. Keys stay in this platform; there is no public signup.
API keys, grouped by vault
Keys are scoped to a single vault and created in that vault's Settings → API Keys. A key alone can never seal, every mutation also carries your request-signing JWS.
policiesVault settings →
prod-backendsealverify2 min agoActive
claims-evidenceVault settings →
claims-servicesealwebhooks18 min agoActive
statutory-reportsVault settings →
reporting-roread3 h agoActive
Webhooks
Webhook endpoints & delivery logs
Endpoints, per-delivery attempts and response codes, retries and test events live in the Webhooks screen. Event types and signature verification are documented on the portal.
Integration copilot
✦ Rox IntelligenceDescribe your stack, get a snippet
Tell me your stack and what you're sealing, I'll write the integration plan and the code against your real vaults. Or paste an error code (e.g. RR-1003) for a plain-language fix.
✦ Generated by Rox Intelligence, review before external use