Third-Party Integrations
At a glance
Third-Party Integrations is the unified configuration layer for nine external service families — payment gateways, calendars, social media, video streaming, mapping, WADA/ADAMS anti-doping, insurance, government sports registries, and accounting backends — each modelled as a typed Integration document with Key Vault credential refs, a draft→active→paused→decommissioned lifecycle, sandbox toggles, per-capability feature flags, and usage tracking so tenants can wire up the boule ecosystem without storing secrets inline.
How it works
Every third-party connection is represented by a domain-typed integration document (PaymentGatewayIntegration, CalendarIntegration, SocialMediaIntegration, StreamingIntegration, MappingIntegration, WadaAdamsIntegration, InsuranceIntegration, GovSportsRegistryIntegration, AccountingIntegration) that follows the same draft→active→paused→decommissioned lifecycle. Secrets are never stored inline; instead the document holds key-vault credential refs (api_key_ref, oauth_client_secret_ref, signing_certificate_ref) that the runtime resolves through Azure Key Vault at call time. Each integration carries its own typed configuration: payment gateways declare supported currencies, sandbox mode, and Stripe/PayPal/Swish/iDEAL provider hints; calendar integrations encode OAuth refs, sync direction (push/pull/bidirectional), and event-type filters; social media integrations track per-page/account credentials and toggle publish, analytics, and moderation capabilities; streaming integrations store API keys, RTMP URLs, and DVR/chat/auto-record flags; mapping integrations hold per-API-key domain allowlists and a usage budget.
WADA/ADAMS integrations carry organization and sport codes, athlete pool ids, and toggles for whereabouts sync, TUE management, test-result tracking, and notification relay. Insurance integrations expose broker/policy-group ids and switches for auto-enrollment, claims submission, premium calculation, and certificate generation. Government sports registries auto-uppercase the country code and gate membership reporting, grant applications, facility registration, event reporting, and compliance tracking on configurable schedules.
Accounting integrations bind to Fortnox, Xero, QuickBooks, and Visma with a chart-of-accounts mapping, fiscal-year config, sync direction, and VAT-reporting toggles. Usage tracking records every outbound call so tenant admins can see request counts, error rates, and quota burn per integration, and a validation endpoint exercises the credentials in sandbox mode before the document leaves draft.
Key capabilities
- Unified lifecycle (draft→active→paused→decommissioned) across nine integration families
- Key-vault credential refs (api_key_ref, oauth_*_ref, signing_certificate_ref) — no inline secrets
- Per-integration sandbox mode and pre-flight validation before activation
- Capability flags per integration (publish, analytics, moderation, sync direction, auto-enrollment)
- Multi-currency and multi-country support with auto-normalised country codes
- Usage tracking with request counts, error rates, and quota visibility
- Domain-specific config (RTMP URL, ADAMS pools, chart-of-accounts mapping, broker IDs)
In practice
A federation finance officer wants to push invoices to Fortnox. They open Settings → Integrations, click Add → Accounting, choose provider Fortnox, and the wizard creates an AccountingIntegration in draft. They authorise the OAuth flow, which writes the refresh token into Key Vault and stores only the credential ref.
They map the chart of accounts (license fees → 3010, tournament fees → 3020), pick fiscal year 2026, set sync direction to push, and click Validate. The platform exercises the connection in sandbox mode, reports a green check, and they flip the lifecycle to active. The next nightly job pushes 142 invoices; the usage panel shows 142 requests, 0 errors, and 1.3% of the daily quota consumed.
Features in this subsystem
9| ID | Status | Features |
|---|---|---|
| F14.04.01 | Shipped | Payment gateway integration (Stripe, PayPal, Swish, iDEAL, etc.) — PaymentGatewayIntegration CRUD, lifecycle (draft→active→paused→decommissioned), key-vault credential refs, multi-currency, sandbox mode, usage tracking, validation ✅ PL-F1404a |
| F14.04.02 | Shipped | Calendar integration (Google Calendar, Outlook, iCal) — CalendarIntegration CRUD, lifecycle, OAuth/API-key refs, sync direction (push/pull/bidirectional), sync state tracking, event type filtering ✅ PL-F1404a |
| F14.04.03 | Shipped | Social media API integration (Facebook, Instagram, X) — SocialMediaIntegration CRUD, lifecycle, OAuth refs, page/account management, publish/analytics/moderation capabilities, auto-publish events ✅ PL-F1404a |
| F14.04.04 | Shipped | Video streaming platform integration (YouTube, Twitch) — StreamingIntegration CRUD, lifecycle, API/stream-key refs, channel management, RTMP URL, DVR/chat/auto-record config ✅ PL-F1404a |
| F14.04.05 | Shipped | Mapping/geolocation services (Google Maps, Mapbox) — MappingIntegration CRUD, lifecycle, API-key refs, geocoding/directions/static-maps/places-search toggles, domain allowlist, usage budget ✅ PL-F1404a |
| F14.04.06 | Shipped | WADA/ADAMS integration for anti-doping — WadaAdamsIntegration CRUD, lifecycle (draft→active→paused→decommissioned), ADAMS API/signing-key refs, organization/sport codes, athlete pool management, whereabouts sync, TUE management, test result tracking, notification relay ✅ PL-F1404b |
| F14.04.07 | Shipped | Insurance provider API integration — InsuranceIntegration CRUD, lifecycle, API/OAuth credential refs, broker/policy group IDs, coverage types, auto-enrollment, claims submission, premium calculation, certificate generation, sandbox mode ✅ PL-F1404b |
| F14.04.08 | Shipped | Government sports registry integration (per country) — GovSportsRegistryIntegration CRUD, lifecycle, API/signing-certificate refs, federation code, country code (auto-uppercased), membership reporting, grant applications, facility registration, event reporting, compliance tracking, reporting schedule ✅ PL-F1404b |
| F14.04.09 | Shipped | Accounting software integration (Fortnox, Xero, QuickBooks) — AccountingIntegration CRUD, lifecycle, OAuth/API-key refs, company ID, fiscal year config, sync direction (push/pull/bidirectional), chart of accounts mapping, invoice/payment/expense sync, VAT reporting, sandbox mode ✅ PL-F1404b |