Quick summary (30 sec)
Inspect APIs, keys, and technical diagnostics for Verion Ads integrations.
What is it?
Developer Console helps you manage developer credentials and debug integrations inside Verion Ads. Developer Console is the technical home for keys, logs, and integration health checks.
Why use it?
Inspect APIs, keys, and technical diagnostics for Verion Ads integrations.
When to use — and when not
- Use when your goal matches Developer Hub.
- Do not use if the menu item is hidden — the feature is OFF for you.
How it works in Verion
From Moat Hub (or direct link), open Developer Hub and adjust the module’s controls for your inventory ops.
Who it is for
- Developers
- Technical publishers
- Agency engineers
Step-by-step
- Open Developer Console from Moat.
- Create or rotate API credentials securely.
- Run a health check against a test endpoint.
- Inspect recent error logs.
- Document key owners and rotation dates for your team.
Best practices
- Never commit secrets to public repos.
- Use least-privilege keys per integration.
- Pair with Publisher API webhooks for eventing.
FAQ
What problem does Developer Hub solve?
Open Developer Hub when you need operator-grade controls that classic member menus do not cover.
What usually blocks Developer Hub?
Most often: Moat entitlement and module enablement Feature key: developer_console.
Troubleshooting
Cannot open or use Developer Hub
First check: Moat entitlement and module enablement. Requires the operator to enable the “developer_console” plugin when it is gated.
Developer Hub runs but results look empty/wrong
Verify plan access and that you opened the intended Moat module (Developer Hub).
Was this helpful?