The following is reference documentation when using the AerisWeather API.
Endpoints refer to the types of data to request, such as a place, observation, forecast or advisory, and will be the basis for any request made to the weather API. The following endpoints are currently supported within AerisWeather.
The following are the supported actions with the AerisWeather API. Note that some actions are not supported for certain endpoints. Refer to each endpoint documentation for a list of supported actions for that endpoint.
When calling a weather API endpoint, normally a place/location is provided. The following are the supported place formats that can be passed, normally to the p parameter or used as the :id. All endpoints will allow the following formats, unless specified in the individual endpoint documentation.
Often times clients will need to gather weather data with automated scripting which typically comes with high volumes in a short time frame. The weather API is ready for your automated queries, but there are a few tips outlined below to help optimize your requests.
The weather for each period is provided in a coded format to allow for more custom implementations where the provided weather phrasing and icons are not desired. The weatherCoded field provides the complete listing of weather codes broken up by time periods within its parent period, which gives the start times when a particular weather type is expected to begin. A single weather code is given for the entire period in the weatherCodedPrimary field, which is the weather type across all periods with the highest priority.
Below is a list of icons that will correlate with the icon property within the AerisWeather API. You will find our legacy icons in addition to our current icons. To download the list of icons, please visit our downloads page.
Use cases where custom icon mapping is required can use the API's weatherCodedPrimary values seen in the Coded Weather docs. These values correlate with the [weather] code which can be either Cloud Codes or Weather Codes. Alternatively, you can use the icon value to map directly to custom icons. The full list of icons available in the API are listed on the Icon List page. There are 3 main ways to go about this listed below.
AerisWeather API data can also be consumed via server-push instead of polling for data. Webhooks are particularly useful when your application needs to consume large amounts of data efficiently and in a timely manner. With this push strategy, AerisWeather can send data to your application with as little delay and latency as possible.
Last modified: July 30, 2020