API calls return an error 401

You can get the error 401 in the following cases:

• You did not specify your API key in API request.

• Your API key is not activated yet. Within the next couple of hours, it will be activated and ready to use.

• You are using wrong API key in API request. Please, check your right API key in personal account.

• You have free subscription and try to get access to our paid services (for example, 16 days/daily forecast API, any historical weather data, Weather maps 2.0, etc). Please, check your tariff in your personal account and pay attention at our price and condition.

Starting from 9 October 2015 our API requires a valid APPID for access. Note that this does not mean that our API is subscription-only now - please take a minute to register a free account to receive a key.

For FOSS developers: we welcome free and open source software and are willing to help you. If you want to use OpenWeather data in your free software application please register an API key and file a ticket describing your application and API key registered. OpenWeather will review your request lift access limits for your key if used in open source application.

API calls return an error 404

You can get this error in the following cases:

• You make a wrong API request. Please, check your API request. The detail documentation about any our weather services is here.

• You specify wrong city name, ZIP-code or city ID.
  This list contains the following data by locations in our system:

  • City name

  • City ID

  • Geographical coordinates of the city (lon, lat)

  • Zoom, etc

API calls return an error 429

You will get the error 429 if you have free tariff and make more than 60 API calls per minute.

Please switch to a subscription plan that meets your needs or reduce the number of API calls in accordance with the established limits.

HTTP Codes

Here is a list of all supported HTTP status codes. Many non-200 responses include a sample response for development purposes, but it will always be in a "sample" field as to not conflict with successful fulfillment workflows.

200 Success

Normal success response for the requested resource.

204 No Data

This occurs when the data source doesn't return a report for the requested station or the station is known to not submit reports to the data source. This second field is usually static, so subsequent calls will also return a 204 code.

400 Client Error

Most 400 client errors are due to invalid URL parameters or unknown ICAO codes. AVWX only accepts 4-character ICAO codes of currently operating stations. Closed airports, IATA codes, and non-ICAO GPS codes are not recognized.

You may also receive this if no report is found from the data sources and nothing is available in the cache.

401 Missing Authorization

The endpoint requires authorization to access. Be sure to include your API token in the request header or as a URL parameter.

403 Unauthorized

The API token was rejected for one of the following reasons:

• Token value could not be found

• Token has been disabled by the user or admin

• User's plan type does not have access to the requested resource

429 Too Many Requests

The user's account or token has hit it's daily call limit. You can view your recent usage from the account portal. If you need to increase your call limit, you can upgrade your plan or opt-in to overage billing.

500 Unknown Server Error

Error representing a code error not handled by any other HTTP code. Bug reports are automatically submitted for review. Subsequent retries are likely to fail.

502 Cannot Connect to Data Source

There was an issue fetching a report from the data source. This is usually a temporary issue and retries can be made shortly after.

503 Server Rebooting

The server is being updated and the request has been cancelled. Retry your connection immediately for the request to be queued.