Sub-operator Access Control for Partner API Credentials

What’s New

We’re introducing support for sub-operator access control when creating Partner API credentials in the Hub.

Soon, you’ll be able to define exactly which sub-operators an API key can access—directly at creation time. This aligns the create flow with the existing update functionality and underlying API capabilities.

Key improvements:

• Add support for specifying operatorIds when creating API credentials
• Enable selective access to sub-operators (instead of default full access)
• Maintain existing behavior: leaving operatorIds empty grants access to all sub-operators

Why It Matters

This update gives you more precise control over API access.

Instead of not having access, you’ll be able to scope API credentials to specific sub-operators—improving security, governance, and flexibility in multi-operator setups.

It also unlocks upcoming improvements in the Hub UI, where operator selection will be available during API key creation and editing.