All documentation

Tenant Onboarding

Set up your Naiza workspace, invite fraud operations users, configure API access, and connect webhooks to deliver decisions to your systems.

Download Markdown
GuidesAPI ReferenceCode ExamplesBest Practices

Tenant Onboarding

This guide walks through the practical path from account creation to a production-ready integration.

1) Environments

Use separate tenants, API keys, webhook URLs, and secrets for each environment:

  • Development
  • Staging
  • Production

Never reuse production keys outside production.

2) Create API Keys

  1. Log in to the Naiza dashboard
  2. Navigate to Settings → API Keys
  3. Create a key for each environment
  4. Store the key in a secret manager or CI secret store

3) Choose Your Integration Surface

Pick the APIs that match your product surface:

  • Server-side risk decisions: POST /api/v1/decisions/evaluate
  • Server-side event ingestion: POST /api/v1/events (sync) or POST /api/v1/events/async
  • Browser signals: POST /api/v1/websdk/tokens + POST /api/v1/websdk/signals
  • Operational automation: lists + feedback + webhooks

4) Webhooks

  1. Create a subscription: POST /api/v1/webhooks/subscriptions
  2. Persist signingSecret immediately (returned once)
  3. Implement signature verification using raw request bytes
  4. Use POST /api/v1/webhooks/subscriptions/:id/test to validate connectivity

See Webhooks in the API Reference.

5) Sandbox Testing Checklist

  • Validate 401 handling for missing/invalid keys
  • Validate 400 / 422 handling for invalid payloads
  • Validate 429 backoff behavior
  • Confirm webhook retries do not double-apply side effects (idempotency)

6) Go-Live

  • Enable monitoring dashboards for decision volume and error rates
  • Define operational runbooks for key rotation and incident response
  • Document internal ownership for webhook endpoint uptime