API surface
REST, webhooks, callback contracts, versioning and backward compatibility give integrations a predictable boundary.
- REST API
- Webhooks
- API versioning
- Backward compatibility
INTEGRATION ENGINEERING
The integration layer is designed around explicit contracts, authenticated callbacks and adapter-first onboarding.
DETAIL ↓NETXGEN / PUBLIC NETWORKMAINnetxgengaming.comTECHNICtechnic.netxgengaming.comSTATUSstatus.netxgengaming.com
08
Integration Engineering
The integration layer is designed around explicit contracts, authenticated callbacks and adapter-first onboarding. The sections below describe the capability surface in customer-facing technical language while intentionally avoiding internal credentials, topology and commercially sensitive controls.
Discovery & health
Discovery, health, metadata and manifests expose integration readiness without exposing internal topology.
- /discovery
- /health
- /meta
- Service manifests
Secure callbacks
Authentication, HMAC, signatures and idempotency protect callbacks and reduce duplicate processing.
- API authentication
- HMAC
- Signed requests
- Idempotency
External services
SMS, payments, KYC, OCR, verification, email, push, monitoring and other services can be enabled through tenant-level entitlements.
- SMS providers
- Payment providers
- KYC providers
- Tenant entitlements