Environments
Environments
Nova runs one isolated stack per MVNO, per environment. Pick the right
base URL for the MVNO and environment you are integrating against — never
hard-code a single URL across MVNOs.
Base URL pattern
https://api[-uat].<mvno>.85.group/api/v1
| MVNO | UAT | Production |
|---|---|---|
| megsApp | https://api-uat.megsapp.85.group/api/v1 | https://api.megsapp.85.group/api/v1 |
| Spar Mobile | https://api-uat.sparmobile.85.group/api/v1 | https://api.sparmobile.85.group/api/v1 |
Don't see your MVNO here? Ask your account manager — new MVNOs spin up
on the same pattern but are not listed publicly until launch.
API key environment isolation
API keys are issued per-environment. A UAT key will not authenticate
against production and vice versa. Plan for two sets of keys.
Data isolation
UAT and production are entirely separate Cloud SQL databases. Test data
lives only in UAT and is wiped on database refreshes (typically monthly,
announced in the Changelog).
CORS
Browser calls are accepted only from the allowed partner-portal origins
configured for that MVNO. If you are building a dashboard outside our
hosted portal, ask us to allowlist your origin.
IP allowlisting
Not enforced by default. Enterprise partners can request IP-restricted
keys — talk to your account manager.
Updated about 4 hours ago