A Guide to Decoding Error Messages

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.

Tip: Use browser developer tools (Console or Network tab) to get more detail on 400 errors, especially if submitting forms or configuration updates..

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.

Start with the API Docs for issues related to request structure or rate limits; contact support for issues you can’t resolve through documentation.

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

400 Bad Request

Meaning: Invalid/missing parameters
Resolution: Check parameter formatting and required fields.

401 Unauthorized

Meaning: Invalid or missing API key
Resolution: Validate API key/token and permissions.

402 Payment Required

Meaning: Insufficient tokens
Resolution: Upgrade or refill your plan as needed.

403 Forbidden

Meaning: Feature not enabled / plan limit reached
Resolution: Check if the endpoint requires a premium feature or if your token has limited scope.

404 Not Found

Meaning: The specified resource doesn’t exist
Resolution: Check resource ID or path.

500 Internal Server Error

Meaning: Server-side issue
Resolution: Retry or report to support if persistent.

503 Service Unavailable

Meaning: Temporary outage
Resolution: Retry later. Use Retry-After header if available.

Free plans are limited to a fixed number of daily and per-second requests. See API Rate Limits for details.

Each API response includes an X-Correlation-ID header for traceability.

Tip: When contacting support, include this value (visible in response headers in tools like Postman or browser DevTools) to speed up resolution.

Error Payload Example

A 403 error may return a response like this:

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.
Screenshot 2024-10-14 at 12.56.59.png

Note: You must create an account and be logged in to use this feature.

API Assistant

Interact with a context-aware assistant trained on Tomorrow.io’s models and documentation. Use it to:

Troubleshoot request errors
Understand field definitions
Explore API capabilities

The assistant leverages Tomorrow.io-specific data to offer more relevant and accurate guidance than general-purpose tools.

You can launch the assistant directly from here.

Still Need Help?

If you’re experiencing persistent issues or need support with advanced troubleshooting, contact us at support@tomorrow.io.