Weather Underground Historical Airport Temperature Series

https://api.sandbase.ai/v1/api/weather-underground/historical-airport-temperature-series

Retrieve a complete year-scale airport observation temperature series for settlement calibration. Returns every observation within the requested local-date range (up to 366 days), preserving the full intraday path.

Price
$0.01USD / callFirst 100 calls per day free (shared per organization)
Method
POST
Response
Async JSON
Parameters
5 required · 0 optional

Try the model

Playground

Open playground
Input
End date in YYYYMMDD format, inclusive local calendar date.
Start date in YYYYMMDD format, interpreted as a local calendar date.
Airport station ICAO code (e.g. EFHK, KJFK). Obtain from search endpoint's icaoCode field.
Two-letter ISO country code for the station (e.g. FI, US).
IANA timezone name for local date grouping (e.g. Europe/Helsinki, America/New_York). DST transitions are handled automatically.
OutputReady

Your output will appear here

Complete the inputs, then click Run.

Model card

Specifications

Pricing

Base price
$0.01 / run
Daily free calls
First 100 calls per day free (shared per organization)

Request & response

Method
POST
Request body
application/json
Response
application/json
Execution
async

Parameters

end_date
string · required
start_date
string · required
station_id
string · required
country_code
string · required
timezone_name
string · required

Access

Provider
Weather Underground
API
Platform API
Base URL
https://api.sandbase.ai
Endpoint
/v1/api/weather-underground/historical-airport-temperature-series
Authentication
Bearer API key

API README

Weather Underground Historical Airport Temperature Series

Retrieve a complete year-scale airport observation temperature series for settlement calibration. Returns every observation within the requested local-date range (up to 366 days), preserving the full intraday path.

Start building

Send your first request

Platform API endpoint with unified authentication and usage tracking.

Production API
Platform API endpoint
https://api.sandbase.ai/v1/api/weather-underground/historical-airport-temperature-series
Authorization header
Authorization: Bearer $SANDBASE_API_KEY
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
  -X POST "https://api.sandbase.ai/v1/api/weather-underground/historical-airport-temperature-series" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'SANDBASE_JSON'
{}
SANDBASE_JSON
)
printf '%s\n' "$result"

Explore more

Related APIs

All APIs
APIPriceResponseReleased
Weather Underground$0.01 per callAsync JSONOct 30, 2026

Questions

FAQ

How do I use the Weather Underground Historical Airport Temperature Series API?

Send a POST request to https://api.sandbase.ai/v1/api/weather-underground/historical-airport-temperature-series with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.

How much does the Weather Underground Historical Airport Temperature Series API cost?

$0.01 per call. Every organization gets 100 free calls per UTC day, shared across eligible SandBase APIs including this one; after that each call is billed at this price from your SandBase balance. There is no subscription.

What parameters does the Weather Underground Historical Airport Temperature Series API accept?

Required: end_date (string), start_date (string), station_id (string), country_code (string) and timezone_name (string). The Parameters table and the Playground on this page list every field.

What does the Weather Underground Historical Airport Temperature Series API return?

A JSON result. This endpoint runs asynchronously, so the response tells you how to fetch the finished result.

Do I need a Weather Underground developer account or API key?

No. Weather Underground Historical Airport Temperature Series runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Weather Underground API access separately.