Spotto API: Regional Endpoints and OpenAPI Specs
Overview
The Spotto API provides programmatic access to your cloud operations data. Each regional endpoint serves a complete Swagger/OpenAPI specification, which is the best place to explore available endpoints and try out requests.
Regional Endpoints
Spotto operates three fully isolated environments. When you sign up, you select your region - and that choice determines which API endpoint you'll use for all requests.
| Region | API Endpoint |
|---|---|
| Australia | https://api-au.spotto.ai/ |
| USA | https://api-us.spotto.ai/ |
| Europe | https://api-eu.spotto.ai/ |
Each region is completely separate. Your data lives exclusively in the region you selected during signup, and you must use that region's API endpoint to access it. There's no cross-region data sharing or replication.
Getting Started
The quickest way to explore the API:
- Navigate to your region's endpoint in a browser
- Browse the Swagger UI to see available operations
- Generate an API key from the Spotto Portal
- Start making requests
API Specification
Each regional endpoint serves an interactive Swagger UI with:
- Complete endpoint documentation
- Request/response schemas
- Built-in "Try it out" functionality
- Authentication configuration
The Swagger spec is always current with the deployed API version, so it's the authoritative reference for available operations and their parameters.
Troubleshooting
I’m getting 401 Unauthorized
What you're seeing: Requests fail with 401 Unauthorized in Swagger UI or curl.
Likely causes:
- Missing/incorrect API key header.
- API key was rotated or revoked. How to fix:
- Generate or rotate a key in the Spotto Portal (see Authentication).
- Confirm you are sending
x-api-key: <YOUR_KEY>(or your configured auth header) on every request. - Retry against the correct regional endpoint for your account.
I’m calling the wrong region
What you're seeing: Everything “looks right” but responses are empty or auth fails. Likely causes: Your account exists in a different Spotto region than the endpoint you’re using. How to fix:
- Confirm the region you selected at signup.
- Use the matching endpoint from Regional Endpoints above.
Next Steps
- Authentication — Learn how to generate and use API keys