API/Sandbox and production
v1.0.0-beta.mdGet API keys
Start here

Sandbox and production

Sandbox is the merchant plus the key prefix, on the same host. Forced failure scenarios are named; there is no flag that fabricates an approval.

Forced failures

Sandbox keys accept the header x-sidaxis-scenario. Live keys ignore it.

ScenarioWhat it injects
successNothing at all — the real engine runs and needs a real face
liveness_failThe capture fails liveness: 403 BIOMETRIC_LIVENESS_FAILED
vrc_coercedA coercion signal: 403 COERCION_DETECTED
subject_mismatchThe face does not match the claimed subject: 403 IDENTITY_MISMATCH
duplicate_enrollAn identity already exists for this face

The one real difference

Sandbox skips blockchain anchoring, so sandbox receipts come out without a public seal. Everything else — refusal reasons, assurance levels, ceilings, webhooks — behaves as in production.

Sidaxis is the human authorisation layer. It never moves money, holds funds or settles. The machine-readable contract is openapi.yaml.
Sidaxis API documentationQuickstartAuthenticationHosted or headlessSandbox and productionIdempotencyRate limitsErrors and refusalsField namesWebhooksAssuranceThe document ruleAlias availabilityMerchant themeMCP serverCompatibilityStatusRoadmapChangelogIdentityEnroll an identityRecognise a personDisclose an attributeMandatesThe eight scopesIssue a mandateCheck an actionConsume a mandateRead a mandateRevoke a mandateReceiptsRead a merchant's receiptsVerify a receiptHosted sessionsCreate a hosted sessionConsume a hosted sessionOne Face for agents