Overview#
Global deployments of the platform mean different partners integrating from different regions under different regulatory regimes, with different language and currency requirements. The Partners domain handles the full scope of that: API key lifecycle management across environments, rate-limited and permission-scoped partner access, event-driven webhooks with signed payloads, and the localisation configuration needed to make the platform feel native in any jurisdiction.
Key Features#
- Multi-environment API key management with dev, staging, and production separation
- Tiered rate limiting across starter, professional, enterprise, and unlimited tiers
- Fine-grained permission scopes with secure key rotation and optional expiration
- Integration webhooks with event subscriptions, signature verification, and health checks
- Usage analytics with per-endpoint request tracking, error rates, and response times
- Multi-locale internationalisation with RTL language support
- Regional date, time, and currency format configuration
- Global platform region management with compliance tracking across multiple jurisdictions
- Tenant locale initialisation with default and additional locale support
Use Cases#
Relevant sectors include financial crime technology, law enforcement software, and intelligence platform integration.
- Enabling third-party partners to integrate via API with scoped access and rate limiting
- Deploying the platform across multiple regions with localised date, time, and currency formats
- Monitoring partner integration health and usage patterns for capacity planning
- Managing regulatory compliance status across global deployment regions
Integration#
The Partners domain connects with partner configuration, integration framework, webhook management, and tenant settings. It supports multi-region deployment with compliance tracking for GDPR, HIPAA, and other regulatory frameworks.
Open Standards#
- GraphQL (June 2018 specification): all partner API operations, including key management, webhook configuration, and locale settings, are exposed through a typed GraphQL schema using queries and mutations.
- OAuth 2.0 (RFC 6749): API key permission scopes follow the OAuth 2.0 scope convention, and partner access tokens are validated as Bearer credentials on each authenticated request.
- SHA-256 (FIPS 180-4): API key values and webhook shared secrets are stored only as SHA-256 digests; the plain-text token is returned once at creation time and never persisted.
- IETF BCP 47: locale codes throughout the platform (e.g.,
en-US,en-GB,fr-FR,ar-SA) conform to IETF BCP 47 language tag syntax for language and region identification. - ISO 4217: currency codes used in regional and locale configuration (USD, EUR, GBP, SGD, etc.) follow the ISO 4217 alphabetic currency code standard.
- ISO 8601: all timestamps exposed through the API (key creation, expiry, last-used, webhook health checks, usage period boundaries) are serialised in ISO 8601 extended format.
- IANA Time Zone Database (IANA TZDB): region timezone identifiers (e.g.,
America/New_York,Europe/London,Asia/Singapore,UTC) are taken from the IANA Time Zone Database. - JSON (RFC 8259): partner configuration payloads, webhook event bodies, and locale translation bundles are all exchanged and stored as JSON.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14