Environments

Picking a base URL, and which environment to integrate against.

heliumOS Wi-Fi offload runs two independent environments. Each has its own gateway, partner records, API keys, and certificate authority, with no sharing between them.

One older endpoint is being retired. api.dev.hib.nova.xyz is the original proof-of-concept and is being phased out. New integrations should point at api-dev.dev.hib.nova.xyz. If you were issued a key against the proof-of-concept, your account owner will migrate you when you're ready.

The SDK accepts these as named environments:

PasspointSDK.configure({
  apiKey: 'pk_xxx',
  environment: 'development', // 'production' | 'development'
});

Or pass a custom base URL, which must end at /api/inventory/v1 with no trailing endpoint:

PasspointSDK.configure({
  apiKey: 'pk_xxx',
  environment: 'https://your-api.example.com/api/inventory/v1',
});

Which to use when

• Local app development, internal QA, end-to-end tests: development. Build a parallel partner record there with throwaway subscriber IDs.
• Customer-facing builds: production. Never point a customer build at development. The CAs differ, so installed profiles fail to associate.

Each environment has a different CA. A profile installed while pointing at development will not authenticate against production hotspots. Re-installing after switching environments is required.

Confirming you're hitting the right one

The SDK logs the resolved base URL at info level on first use. Server-side, call a partner endpoint with curl -v and check the response: partner IDs and certificate chains are environment-specific.