How can we help?

The tenant ID is shown in the URL bar of the dashboard (app.falconveritas.com/t/{tenantId}/...) and is returned by GET /v1/me when authenticated. For API access, include it in the X-Tenant-Id header.

prod (app.falconveritas.com) is the production environment serving real customers. staging (staging.app.falconveritas.com) is a UAT environment that mirrors production semantics but runs against synthetic data — use it for pre-launch validation. dev (dev.app.falconveritas.com) is for the engineering team and may be broken at any time.

Never enter real customer data into dev or staging.

First, confirm you're using the correct secret for the environment. The webhook secret for staging is different from prod; switching environments without rotating your webhook URL will leave you with a stale secret. See troubleshooting → webhook signature.

Issue a new key via POST /v1/tenants/{id}/api-keys, deploy the new key in your services in a rolling fashion, then revoke the old one via DELETE /v1/tenants/{id}/api-keys/{key_id}. The full key-rotation runbook is at runbooks → key rotation.

Per the security audit (LL-002), the inference proxy uses the publishable key after the initial service-role token lookup. This means even admin-scoped tokens are scoped by row-level security. To access cross-tenant data you must use the dedicated admin routes, which log every call to security_events. See troubleshooting → RLS denied.

≥ 0.92 auto-match (no human review); 0.70–0.92 routed to analyst review with full evidence; < 0.70 raised as an exception and queued for triage. Thresholds are tenant-configurable via Reconciliation → Match thresholds.