Multi-brand & operator configs
When a partnerId is enough vs when a brand needs its own operator configuration
Operators and aggregators running multiple brands often ask whether each brand needs its own operator configuration. In most cases it does not — a partnerId is enough. This page explains the difference so you set up only what you need.
One application per operator
You file one application per onboarded operator or aggregator (legal entity, contacts, callback URL, outbound IPs, public key, currencies). You do not file a separate application per brand. Under that one integration you can run many brands.
Default: one operator config, partnerId per brand
For most multi-brand setups, keep a single operator configuration and distinguish brands at runtime with a partnerId on each /game/url call:
partnerIdis a free-form value you choose (e.g. a brand name); it needs no pre-registration.- We tag bets and players by
partnerIdfor reporting. - It is not the same as
operatorId(your integration/config ID) — never setpartnerIdequal tooperatorId.
All brands under one operator config share that config's settings: max exposure / liability, min/max bet limits, signing key, whitelisted IPs, and callback URL.
When a brand needs its own operator config
The following are configured per operator config (per operatorId) and apply uniformly to every brand routed under it. A brand that needs different values therefore requires its own operator config (a new operatorId):
| Need | partnerId enough? | Separate operator config? |
|---|---|---|
| Brand separation for reporting / display | ✅ | — |
| Different max exposure / liability | ❌ | ✅ |
| Different min / max bet limits | ❌ | ✅ |
| Different commercial terms / rates (incl. region-tiered) | ❌ | ✅ |
| Separate signing key or callback URL per brand | ❌ | ✅ |
Liability and min/max limits are set on the operator config and cannot be varied per partnerId — changing them affects every brand under that operatorId. Region-specific rates are configured against a dedicated operatorId per region. Other config-level settings — free bets on/off, lobby on/off, game widget domain — are likewise per operator config.
A separate operator config gives you a new operatorId. To request one, send us the brand name, its callback URL, an RSA public key (you generate), and the desired max exposure / limits.
Outbound IPs are different — they're whitelisted at the integration level (shared across all your operator configs), so adding or changing whitelisted IPs is just a request to us, not a reason to create a separate operator config.
Prefer one operator config + partnerId wherever you can — it's simpler and sufficient for the common case (brand separation with shared limits). Reach for a separate operator config only when a brand genuinely needs different liability, limits, rates, keys, or callback URL.