Documentation

Travel Risk API is two products on one key: risk data under /api/v1 and aviation data under /api/v9, /adb and /ext/v1. All endpoints are served from https://api.travelriskapi.com and return JSON.

Quickstart

1. Get a key. Register on the home page or call the API — the key is returned at once and emailed to you.

curl -X POST https://api.travelriskapi.com/api/v1/register \
  -H "Content-Type: application/json" \
  -d '{"email": "you@company.com"}'

2. Send it in the X-API-Key header.

curl -H "X-API-Key: $KEY" https://api.travelriskapi.com/api/v1/risk-score/TUR

3. Add aviation data with the same key.

curl -H "X-API-Key: $KEY" https://api.travelriskapi.com/ext/v1/flight/UA1/wifi

References

	Covers	Base path
Risk API reference	Countries, risk scores, advisories, alerts, conflicts, usage, billing	`/api/v1`
Aviation API reference	Flights, schedules, airports, airlines, aircraft, airline safety, in-flight Wi-Fi, airport conditions, webhooks	`/api/v9`, `/adb`, `/ext/v1`
Risk OpenAPI · Aviation OpenAPI	Machine-readable specs for code generators and AI agents

Authentication

Every endpoint except /api/v1/health, /api/v1/register and /api/v1/billing/plans needs a key. Send it as the X-API-Key header. Aviation endpoints also accept ?api_key= in the query string for compatibility with existing clients.

Lost your key? POST /api/v1/recover-key with {"email": "..."} emails it to the address it was registered with.

Plans and limits

Plan	Price	Risk requests / day	Aviation calls / month	Burst / minute
Free	$0	100	3,000	60
Starter	$29 / month	2,000	60,000	120
Pro	$99 / month	10,000	300,000	600
Enterprise	$499 / month	unlimited	unlimited	3,000

Daily counters reset at 00:00 UTC. Over a limit, requests return 429 with a Retry-After header. Prepaid credits (from $10 per 10,000 requests) are spent only after the daily risk quota is used up. Manage your plan in the dashboard.

Conventions

Country codes: ISO 3166-1 alpha-3 (TUR) and alpha-2 (TR) are both accepted. GET /api/v1/countries/codes lists every supported code.
Airports and airlines: IATA codes; ICAO where the endpoint says so.
Timestamps: ISO 8601 in UTC.
Freshness: list responses carry data_updated_at (newest record we hold) and generated_at.
Changes: we add fields; we do not rename or remove them without notice. See the changelog.

Security and compliance

Security practices, data handling and compliance documents are published in the Travel Code Trust Center.

Support

Write to api@travel-code.com. Pro and Enterprise plans get priority answers.