Skip to content

Integration checklist

  • Live key stored in a secrets manager and never exposed client-side.
  • Every POST sends a unique Idempotency-Key, and retries reuse it.
  • Retries on 429, 500 and 503 use exponential backoff and honour Retry-After.
  • Timeouts are set (we suggest 5 seconds for single screenings) with a safe fallback, for example holding the onboarding for manual review.
  • Non-Latin names (422 unsupported_script) are transliterated or routed to manual review.
  • A hit: true result pauses the flow and creates a case for an analyst.
  • external_id is sent, so whitelisting and future monitoring work.
  • Screening id, list_versions and model_version are stored with your customer record for audit.
  • Webhook signatures are verified, and events are deduplicated by id.
  • Automated tests cover the sandbox test names, including error triggers.
  • Your threshold was reviewed with your compliance team.