Loading
Loading
Retrieve real-time weather conditions for up to 50 locations in a single POST request. Each location can be specified as a city name or address, GPS coordinates, or IP address. Responses follow the same structure as the single Live Weather API.
The request body must contain a locations array. Each element is an object specifying one location using one of the supported lookup methods: location (address or city name), lat/long (coordinates), or ip (IP address). Each result in the response bulk array contains the same location and current objects as the single endpoint, including full air quality and astronomical data.
Authorize every request with your API key, passed either as a header or as a query parameter:
X-apiKeyapiKeyThis is version v1.0 of the API.
Send a POST request with an optional timezone query parameter to set the default timezone for all results.
formatoptionalStringdefault: jsonResponse format: 'json'.
timezoneoptionalStringOverride timezone for all returned data. Defaults to each location's local timezone.
The request body must be a JSON object containing a locations array with up to 50 entries. Each item accepts a location, optional lat/long for coordinates, and optional timezone override.
{
"locations": [
{
"location": "London"
}
]
}locationsrequiredArray<Object>Array of location objects to query. Maximum 50 items per request.
Each object in the locations array supports the following fields:
locationoptionalStringCity name, address, or place name to query weather for.
latoptionalIntegerLatitude coordinate. Must be used with long.
longoptionalIntegerLongitude coordinate. Must be used with lat.
ipoptionalStringIP address to infer location from.
timezoneoptionalStringTimezone identifier (e.g., America/New_York) to override the resolved timezone.
A successful request returns a 200 OK response with a JSON object containing a bulk array. Each element mirrors a single live-weather response. See the response preview on the right for the full JSON structure.
bulkArray of weather result objects, one per requested location.
Besides the response body, every response carries custom headers you can use to track credit usage, and concurrency usage on endpoints that enforce a concurrency limit. See the Custom Response Headers documentation and the endpoints with concurrency limits for more details.
X-Concurrent-Threadsheaderconcurrency-limited endpointsSpecifies the maximum number of concurrent requests allowed.
X-Concurrent-Threads-Activeheaderconcurrency-limited endpointsIndicates the number of active concurrent requests being processed.
X-AF-Credits-Costheaderall responsesSpecifies the number of credits consumed by the current request.
Each object in the bulk array follows the same structure as the Live Weather API.
See the HTTP Status Codes documentation for a complete reference of common API errors and HTTP status codes.
Please provide data in required format in request body
"locations[0]" must be of type object