WeatherAPI · Arazzo Workflow

WeatherAPI Historical Weather

Version 1.0.0

Resolve a location, then fetch historical weather for a past date.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub WeatherForecastHistoryMarineAstronomyGeolocationSportsAlertsPublic APIsArazzoWorkflows

Provider

weatherapi

Workflows

historical-weather
Search a location and return its historical weather for a date.
Resolves the query into a location and retrieves historical weather for the supplied past date.
2 steps inputs: date, query outputs: forecastDays, matchedName
1
searchLocation
Resolve the free-text query into the best matching location.
2
getHistory
Fetch historical weather for the resolved location on the requested past date, including the hourly breakdown.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: WeatherAPI Historical Weather
  summary: Resolve a location, then fetch historical weather for a past date.
  description: >-
    Pulls observed weather for a date in the past. A free-text query is resolved
    through the search/autocomplete endpoint, and the history endpoint returns
    the hourly and daily breakdown for the resolved location on the requested
    date (on or after 1 January 2010). Every step spells out its request inline
    so the flow can be read and executed without opening the underlying OpenAPI
    description.
  version: 1.0.0
sourceDescriptions:
- name: geoApi
  url: ../openapi/weatherapi-geo-api-openapi.yml
  type: openapi
- name: historyApi
  url: ../openapi/weatherapi-history-api-openapi.yml
  type: openapi
workflows:
- workflowId: historical-weather
  summary: Search a location and return its historical weather for a date.
  description: >-
    Resolves the query into a location and retrieves historical weather for the
    supplied past date.
  inputs:
    type: object
    required:
    - query
    - date
    properties:
      query:
        type: string
        description: Partial city name, postcode, or coordinates to search for.
      date:
        type: string
        description: Past date in yyyy-MM-dd format, on or after 2010-01-01.
  steps:
  - stepId: searchLocation
    description: Resolve the free-text query into the best matching location.
    operationId: searchLocations
    parameters:
    - name: q
      in: query
      value: $inputs.query
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      matchedId: $response.body#/0/id
      matchedName: $response.body#/0/name
  - stepId: getHistory
    description: >-
      Fetch historical weather for the resolved location on the requested past
      date, including the hourly breakdown.
    operationId: getHistory
    parameters:
    - name: q
      in: query
      value: id:$steps.searchLocation.outputs.matchedId
    - name: dt
      in: query
      value: $inputs.date
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      locationName: $response.body#/location/name
      forecastDays: $response.body#/forecast/forecastday
  outputs:
    matchedName: $steps.searchLocation.outputs.matchedName
    forecastDays: $steps.getHistory.outputs.forecastDays

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/weatherapi-historical-weather-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.