Access and common errors
Choose the right next step when a request is denied, invalid or unavailable.
Use access for the right service
Manage API access on the Upperblue account page. API and MCP keys are intended for different services. Never include a real key in a support report or public example.
Start with the status
| Status | Next step |
|---|---|
| 400 | Check parameter names, formats and supported values in the reference. |
| 401 / 403 | Check sign-in, the correct credential type and access to the dataset. |
| 429 | Wait and honour Retry-After when supplied. Keep retries bounded. |
| 503 / network error | Treat this as unavailable. Do not present it as a valid empty dataset. |
Browsers and keys
Do not put a secret API key in JavaScript sent to every visitor. Authenticated Upperblue web products use a supported session and allowed origin. A CORS rejection is not a reason to move a key into browser source.
Check status and ask for help
The status page checks only whether the HTTP process responds. It does not establish dataset freshness. For help, share the endpoint, time, HTTP status and safe request identifier where available, but no keys or session cookies. Contact Upperblue.