Navigating through Tomorrow.io's platform and API is typically straightforward, but occasionally, users may encounter error messages. This guide explains what these errors mean and how to resolve them effectively—whether you’re using the platform or integrating via API.
For Platform Users
HTTP 400 – Bad Request
What it means: The request sent didn’t make sense to our servers—likely due to a formatting issue or missing required fields.
How to fix: Double-check form entries and ensure all required fields are complete and correctly formatted.
HTTP 401 – Unauthorized
What it means: You’re trying to access a resource that requires authentication, but you’re either not logged in or lack permissions.
How to fix: Log in with valid credentials. If you're logged in and still see this error, contact your account administrator to verify your access level.
HTTP 404 – Not Found
What it means: The URL or resource you're trying to access doesn't exist.
How to fix: Verify the link is correct. If the issue persists, the resource may have been moved or deleted.
HTTP 500 – Internal Server Error
What it means: An unexpected error occurred on our servers.
How to fix: Try again after a short while. If the problem continues, contact support at support@tomorrow.io.
For API Users
Tomorrow.io’s API uses standard HTTP response codes to indicate request outcomes. Below is a summary of common errors and links to our API documentation for full detail.
See full error handling section in the API Docs here.
Hard vs. Soft Errors
-
Hard Errors stop the request completely (e.g., invalid parameters or unauthorized access).
-
Soft Errors are warnings returned within a successful response (e.g., partial data availability).
Common API HTTP Errors
| Status Code | Meaning | Resolution |
|---|---|---|
| 400 Bad Request | Invalid/missing parameters | Check parameter formatting and required fields. |
| 401 Unauthorized | Invalid or missing API key | Validate API key/token and permissions. |
| 402 Payment Required | Insufficient tokens | Upgrade or refill your plan as needed. |
| 403 Forbidden | Feature not enabled / plan limit reached | Review plan entitlements or contact support. |
| 404 Not Found | The specified resource doesn’t exist | Check resource ID or path. |
| 500 Internal Server Error | Server-side issue | Retry or report to support if persistent. |
| 503 Service Unavailable | Temporary outage | Retry later. Use Retry-After header if available. |
Each API response includes a X-Correlation-ID header for traceability—include it when contacting support to speed up resolution.
Developer Tools and Support
-
Smart Search in API Docs
Use natural language to ask questions in our developer documentation, powered by AI search.
-
QA Tool for API Calls
Validate your requests before deployment.
Note: You must create an account and be logged in to use this feature.
-
Learn how to structure API requests
How to Use the Tomorrow.io API -
Understand API Rate Limits
Free Plan API Rate Limits -
Understand How API Calls Are Counted
How API Calls Are Counted
Still Need Help?
If you’re experiencing persistent issues or need support with advanced troubleshooting, contact us at support@tomorrow.io.
Comments
0 comments
Please sign in to leave a comment.