Get started with the API
REST access to D-ATIS, transcribed ATIS and AWOS, METAR, TAF, airports, NOTAMs, SIGMET, AIRMET, PIREP, NAS status, and live traffic. Operated by Torrey Systems, LLC. Unofficial. Not for operational use. Confirm on frequency.
What you can build
These boxes read the same serializers as the public API. They do not use an API key and they do not count against plan limits. Not for operational use.
Live data loads when this section is on screen.
Quick start
- Create a free ATIS Relay account and issue a key under Account, API key.
- Send that key on every request:
X-Api-Key: $ATIS_RELAY_API_KEY
One key per account. Keys can be revoked from the same page.
First request
Read the latest D-ATIS for San Francisco International. Available on Free, ATIS Relay Plus, and Commercial.
curl "https://atisrelay.com/api/atis?icao=KSFO" \
-H "X-Api-Key: $ATIS_RELAY_API_KEY"
Response:
{
"atis": {
"airportID": "KSFO",
"atisCode": "B",
"letter": "B",
"dataBody": "SFO ATIS INFO B 1656Z. ..."
},
"departure": null,
"arrival": null,
"official": false,
"notice": "Unofficial. Not for operational use. Confirm on frequency."
}
Code examples
These calls read ATIS_RELAY_API_KEY from the environment. Do not hardcode keys.
curl "https://atisrelay.com/api/atis?icao=KSFO" \
-H "X-Api-Key: $ATIS_RELAY_API_KEY"
const key = process.env.ATIS_RELAY_API_KEY;
const response = await fetch("https://atisrelay.com/api/atis?icao=KSFO", {
headers: { "X-Api-Key": key }
});
const data = await response.json();
console.log(data);
import os
import requests
response = requests.get(
"https://atisrelay.com/api/atis",
params={"icao": "KSFO"},
headers={"X-Api-Key": os.environ["ATIS_RELAY_API_KEY"]},
timeout=30,
)
response.raise_for_status()
print(response.json())
require "net/http"
require "json"
require "uri"
uri = URI("https://atisrelay.com/api/atis?icao=KSFO")
request = Net::HTTP::Get.new(uri)
request["X-Api-Key"] = ENV.fetch("ATIS_RELAY_API_KEY")
response = Net::HTTP.start(uri.host, uri.port, use_ssl: true) do |http|
http.request(request)
end
puts JSON.parse(response.body)
MCP for AI assistants
A read-only remote MCP server is at https://atisrelay.com/mcp using Streamable HTTP. It exposes 30 read-only tools that map to GET endpoints. Discovery methods initialize, notifications/initialized, tools/list, and ping work without a key. Tool calls require your ATIS Relay API key as X-Api-Key or Authorization: Bearer. The MCP server never starts a phone-line dial and never creates subscriptions or webhooks.
{
"mcpServers": {
"atis-relay": {
"url": "https://atisrelay.com/mcp",
"headers": {
"X-Api-Key": "$ATIS_RELAY_API_KEY"
}
}
}
}
Plans and limits
Personal API keys are limited by plan. These caps apply to the key.
| Plan | Per minute | Per day | Phone-line dials |
|---|---|---|---|
| Free | 10 | 500 | Cannot start a new phone-line dial |
| ATIS Relay Plus | 30 | 1000 | 100 new dials per UTC month |
| Commercial | 60 | No daily included allowance | No monthly dial cap |
ATIS Relay Plus is $5.99/month. Commercial is usage-based. See API and Commercial plans and the rate card.
Next steps
- Full API docs for every endpoint, status codes, and API Terms.
- OpenAPI spec (JSON) and YAML.
- API and Commercial plans to choose Free, ATIS Relay Plus, or Commercial.