Weather APIs: All Them APIs endpoint contract

A coordinate-based hourly forecast with explicit units and timezone.

Endpoint and access

Contract preview · access requires enablement
Weather APIs contract endpoint
POST https://allthemapis.com/api/v1/weather/forecast

This is our proposed customer-facing interface. Provider fulfillment and category-specific keys are not enabled yet. Calls currently return 503 integration_not_enabled; they do not execute a query or spend credits. Existing Search API trial keys do not unlock this category.

Request access for your workload before connecting an application.

Request fields

Proposed request schema
FieldTypeMeaning
latitudenumber, requiredWGS84 latitude, -90 to 90.
longitudenumber, requiredWGS84 longitude, -180 to 180.
hoursinteger, requiredRequested hourly window, 1 to 48.
unitsmetric | imperialUse metric unless explicitly changed.
timezoneIANA timezoneUTC by default; retain offsets in returned timestamps.
Weather APIs example request
curl -X POST "https://allthemapis.com/api/v1/weather/forecast" \
  -H "Authorization: Bearer $ALLTHEMAPIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "latitude": 43.6532,
  "longitude": -79.3832,
  "hours": 24,
  "units": "metric",
  "timezone": "UTC"
}'

The example defines the contract; it is not a completed API call.

Response fields and errors

Intended response fields after access enablement
FieldMeaning
locationResolved coordinates, timezone and elevation when available.
hourly[]Timestamped temperature, precipitation and wind fields, with units and nulls for missing values.
issued_atForecast issue time, distinct from the request time.
request_idAn identifier for support and usage reconciliation.
Weather APIs current unavailable response
{
  "error": {
    "code": "integration_not_enabled",
    "message": "This API requires access enablement. No request has been executed or billed."
  },
  "access_url": "https://allthemapis.com/api-categories/weather/api#request-access"
}

No synthetic response is returned as live data. Pricing, production quotas and content-use rights must be confirmed before activation.

Give the contract to your coding agent

This prompt prepares an adapter without treating a fixture as a successful live request.

Weather APIs agent integration prompt
Prepare an integration for the All Them APIs weather apis contract.

Endpoint: POST https://allthemapis.com/api/v1/weather/forecast
Request shape:
{
  "latitude": 43.6532,
  "longitude": -79.3832,
  "hours": 24,
  "units": "metric",
  "timezone": "UTC"
}

This category requires access enablement and currently returns HTTP 503 integration_not_enabled. Do not execute requests or claim success until access is confirmed.
Read ALLTHEMAPIS_API_KEY from a server-side environment variable only. Never place it in browser code, URLs or logs. Use a bounded timeout, handle 401/429/503 explicitly, and keep null/missing fields distinct from valid zero values. Do not retry indefinitely.
Expected output fields:
- location: Resolved coordinates, timezone and elevation when available.
- hourly[]: Timestamped temperature, precipitation and wind fields, with units and nulls for missing values.
- issued_at: Forecast issue time, distinct from the request time.
- request_id: An identifier for support and usage reconciliation.

Build the adapter and unit tests against an explicitly labeled local fixture. Do not fabricate live results. Summarize what access and production verification are still required.

Request access to weather APIs

Tell us the coverage and volume you need. We will confirm availability and terms before enabling access. This request does not take a payment or create an API key.