Environments

Hubble provides two separate environments. You will start on Staging, and move to Production after your integration is verified.

Staging & Production URLs

Environment	Base URL	Purpose
Staging	https://api.dev.myhubble.money	Testing and development
Production	https://api.myhubble.money	Live transactions with real money

Getting Your Credentials

Before you can use the API, you need two key pieces of information:

• clientId — Your unique partner identifier
• clientSecret — Your secret key (store securely, never expose in client-side code)

Use the integration portal to obtain your staging credentials. Production credentials are provided separately by Hubble after your staging integration is verified.

Credential Isolation

Do NOT use staging credentials on production or vice versa. This will cause authentication failures.

Making Your First API Call

Once you have your credentials, test connectivity by calling the Login API:

curl -X POST "https://api.dev.myhubble.money/v1/partners/auth/login" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "YOUR_STAGING_CLIENT_ID",
    "clientSecret": "YOUR_STAGING_CLIENT_SECRET"
  }'

Successful Response

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expiresInSecs": 3600
}

IP Whitelisting

For security, Hubble only allows requests from pre-approved IP addresses:

• Staging: IP whitelisting may not be required (contact Hubble to confirm)
• Production: Your server IPs must be whitelisted before going live

To have your IP addresses whitelisted, contact the Hubble team with:

• Your company details
• The server IP addresses you'll be making requests from

Dynamic IP Support

If your infrastructure uses dynamic IPs, inform Hubble during onboarding. In such cases, IP whitelisting is not required.

Environment Configuration Best Practices

• Configure base URLs separately - Don't hardcode URLs. Switching from staging to production should be a config change.
• Use environment variables - Store credentials in environment variables, not in source code.
• Never commit credentials - Add credential files to .gitignore and use secrets management in production.

// Example: Environment-based configuration
const config = {
  baseUrl: process.env.HUBBLE_ENV === 'production'
    ? 'https://api.myhubble.money'
    : 'https://api.dev.myhubble.money',
  clientId: process.env.HUBBLE_CLIENT_ID,
  clientSecret: process.env.HUBBLE_CLIENT_SECRET,
};

Next Steps

Once you've confirmed connectivity with the staging environment:

1. Set up authentication and token management
2. Explore the brand catalog
3. Place test orders