AccuWeather Go API Parameters
Request parameters | Basic response parameters | Premium response parameters
AccuWeather Go API Query String Parameters
Parameter | Description | Default value | |
api | Hostname to be used only in production: api.accuweather.com | N/A | Required |
apidev | Hostname to be used only in development: apidev.accuweather.com | N/A | Required |
version | Version of the API | v1 | Required |
format | Format of the response | JSON | Optional |
apikey | Unique code used to access the API | N/A | Required |
language | String indicating the language in which to return the resource | en-us | Optional |
waypoints |
A list of waypoints separated by the pipe character (|) and entered in chronological order. A single API call may contain up to 60 waypoints. A waypoint is a comma-delimited list indicating location, ETA, and optional heading: latitude,longitude,ETA,heading, where
|
N/A | Required |
AccuWeather Go Basic API response parameters
Parameters | Description |
Trip | Aggregated data for the entire trip. |
ExpiresEpoch | To help the caller reduce the number of unnecessary requests made to the AccuWeather Go API, the API monitors the weather in the vicinity of the route and provides guidance as to when the response should be updated based upon how active the weather is in the area. Each JSON response is accompanied with a TTL (time to live) expiration timestamp—ExpiresEpoch—after which the response is considered stale and the caller should make another request to update the response. If no impactful weather is present in that area, the timestamp will extend further into the future (up to one hour). Conversely, if the weather is very active and sudden impactful changes are expected, the timestamp could extend down to a minute into the figure indicating that a very frequent update cycle is necessary. The format of the response is in the number of seconds that have elapsed since midnight on January 1st, 1970. |
AccuWeather Go Premium API Response Parameters
Parameter | Description |
Waypoints | An array of data for each waypoint returned in the same order as specified in the URL. |
|
ExpiresEpoch | To help the caller reduce the number of unnecessary requests made to the AccuWeather Go API, the API monitors the weather in the vicinity of the route and provides guidance as to when the response should be updated based upon how active the weather is in the area. Each JSON response is accompanied with a TTL (time to live) expiration timestamp—ExpiresEpoch—after which the response is considered stale and the caller should make another request to update the response. If no impactful weather is present in that area, the timestamp will extend further into the future (up to one hour). Conversely, if the weather is very active and sudden impactful changes are expected, the timestamp could extend down to a minute into the figure indicating that a very frequent update cycle is necessary. The format of the response is in the number of seconds that have elapsed since midnight on January 1st, 1970. |