Frequently Asked Questions

General overview

About the company: what is OpenWeather?

OpenWeather (headquartered in London) is a team of IT-intellectuals that create pivotal products for business using climate data. For each point on the globe, OpenWeather provides hyperlocal minutely forecast, historical data, current state, and from short-term to annual forecasted weather data. All data is available via industry standard APIs.

OpenWeather Ltd. has more than 3 million customers including Fortune 500 companies and thousands of other businesses globally.

APIs

What are the minimum/maximum temperature fields in the Current Weather API and Forecast Weather API?

In the Current Weather API and Hourly Forecast API:

As it is a current weather data that reflect weather conditions only for the current moment, we add optional statistical parameters the temp_min and temp_max fields to show dispersion of temperature at this current moment. This is the minimum/maximum currently observed temperature or forecast temperature (within large megalopolises and urban areas).

In the 16-Day Forecast API and 30-Day Forecast

The list.temp.min and list.temp.max fields are minimum/maximum daily temperature, and show the minimum and maximum temperatures in the day.

Which time format and timezone are used?

OpenWeather uses Unix time and the UTC/GMT time zone for all API calls, including current weather, forecast and historical weather data. The timezone_offset parameter shows the shift in seconds from UTC. In a One Call API response, there is also a timezone parameter that shows the time zone name for the requested location.

Why I do not see some parameters in the API response?

If you do not see some of the parameters in your API response, it means that these weather phenomena just have not happened for the selected location at the time of measurement. Only actually measured or calculated data is displayed in an API response.

What is the format of the API response?

The JSON format is used by default. To get data in the XML or HTML format, just use “xml” or “html” for the mode parameter. The HTML format is available for Current Weather API only. For the One Call API, data is only available in the JSON format. If the mode parameter is omitted, the format is JSON by default.

Examples of API calls:

  • JSON: api.openweathermap.org/data/2.5/weather?q=London&{YOUR_API_KEY}
  • XML: api.openweathermap.org/data/2.5/weather?q=London&mode=xml&{YOUR_API_KEY}
  • HTML: api.openweathermap.org/data/2.5/weather?q=London&mode=html&{YOUR_API_KEY}

How can I switch between temperature units in API calls?

Temperature is available in Fahrenheit, Celsius and Kelvin units. Kelvin is used by default, with no need to use the units parameter in API calls.

For temperature in Fahrenheit, use "units=imperial".

For temperature in Celsius, use "units=metric".

You can find examples of API calls in the documentation for the service you are interested in.

A full list of all API parameters, with units, can be found here.

What are the weather condition codes and icons?

A list of weather condition codes with icons (range of thunderstorm, drizzle, rain, snow, clouds, atmosphere including extreme conditions such as tornado or hurricane) can be found here.

You are free to use these icons in your own solutions.

Where can I find a list of City IDs?

For current and forecast products (Current API, Hourly Forecast API, Daily Forecast for 16 days, Climatic forecast for 30 days, 5 day/3 hour forecast data) can be downloaded here.

Please note that you can also make requests to our APIs by using coordinates, ZIP codes, etc. Please refer to documentation of specific API to see all available options.

API errors

API calls return an error 401

You can get the error 401 in the following cases:

API calls return an error 404

You can get this error when you specified the wrong city name, ZIP-code or city ID. For your reference, this list contains City name, City ID, Geographical coordinates of the city (lon, lat), Zoom, etc.

You can also get the error 404 if the format of your API request is incorrect. In this case, please review it and check for any mistakes. To see examples of correct API requests, please visit the Documentation of a specific API and read the examples of API calls there.

API calls return an error 429

You will get the error 429 if you are a user of a Free subscription and make more than 60 API calls per minute (surpassing the limit of your subscription).

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

API calls return errors 500, 502, 503 or 504

In case you receive one of the following errors 500, 502, 503 or 504 please contact us for assistance. Please enclose an example of your API request that receives this error into your email to let us analyze it and find a solution for you promptly.