Developer preview API v1

Sandbox only. No real funds moved. No production access is granted here. Access requirements

Credential lifecycle

Rotate through overlap and revoke without delay

Credentials change on a cadence and on signal, with dual-key overlap and urgent revocation when exposure is suspected.

Ownership and runbook

Owner: Credential Custodian. Runbook: RB-API-SECURITY-OPS-001. Rotate credentials through dual-key overlap so each key change keeps a valid credential live until the replacement is confirmed.

Rotate on a schedule and on signal

Replace credentials on the agreed cadence and immediately after suspected exposure, personnel change, or provider incident. Reconcile each key to the exact developer app and programme before deactivating the old key.

Revocation is urgent

Revoke a credential as soon as it is believed compromised, and propagate the revocation to every system that cached it. Do not reuse a revoked key or allow a revoked key to bypass the secret manager.

Dual-key rotation sequence

1. Issue replacement credential for dapp_01900000000000000000000000
2. Update servers and verify the replacement works
3. Keep the old credential briefly for overlap
4. Revoke and destroy the old credential
5. Record the rotation in RB-API-SECURITY-OPS-001