Cirium FlightStats FIDS API

Name: Cirium FlightStats FIDS API API
Brand: Cirium FlightStats FIDS API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

Fetch real-time arrival and departure boards for any airport from Cirium FlightStats with a simple appId and appKey API-key pair. Two endpoints power FIDS-style screens, travel apps, and flight-status agents.

Quickstart

Get started with Cirium FlightStats FIDS API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get airport arrivals from Cirium FlightStats"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cirium FlightStats FIDS API API.

Retrieve real-time arrivals for a specific airport by IATA or ICAO code

Retrieve real-time departures for a specific airport in JSON or XML format

Filter the FIDS feed by airport code path parameter for terminal-board displays

Authenticate using appId and appKey via either query parameters or HTTP headers

GET STARTED

Start building with Cirium FlightStats FIDS API API

Explore with Jentic

View OpenAPI Document

The Cirium FlightStats FIDS API powers airport flight information display systems by returning real-time arrivals and departures for a given airport. The API exposes two endpoints under https://api.flightstats.com — /flex/fids/rest/v1/{format}/{airport}/arrivals and /flex/fids/rest/v1/{format}/{airport}/departures — designed to feed terminal screens, mobile apps, and travel-itinerary tools. Authentication uses an appId plus appKey credential pair, supplied either as query parameters or HTTP headers, and the format path parameter selects JSON or XML responses.

Use Cases

Patterns agents use Cirium FlightStats FIDS API API for, with concrete tasks.

★ Powering an Airport Information Display

Airports and lounges run digital screens showing live arrivals and departures. The Cirium FIDS API returns the structured feed that drives those boards, by airport code and format, refreshed at the cadence the integrator polls. This replaces brittle scraping with a contract-backed feed used across hundreds of FIDS deployments.

GET /flex/fids/rest/v1/json/LHR/arrivals with appId and appKey and render the next 20 arrivals on the lounge screen.

Travel App Flight Status Page

Consumer travel apps embed an airport-board view inside their itinerary screen. Calling the departures endpoint for the user's home airport gives the app a curated set of flights for that day, including scheduled and actual times, gate, and status, so a frequent flyer can monitor their next departure without leaving the app.

GET /flex/fids/rest/v1/json/SFO/departures and surface the user's flight UA123 with current gate and status.

Operations Alerting on Delays

An airline ground-ops team can poll the arrivals endpoint for their hub on a fixed interval to detect flights that have slipped from on-time to delayed, then trigger an alert into Slack or PagerDuty. With only two endpoints to manage, the integration is light enough to run from a small scheduled job.

Every 5 minutes, GET /flex/fids/rest/v1/json/ORD/arrivals and post a delayed-flight summary into the ops channel.

AI Agent Travel Assistant

An AI travel assistant invoked through Jentic can take a user's airport code and return a short narrative summary of arrivals or departures. Jentic isolates the appId and appKey in MAXsystem, so the agent never sees the raw credential, and the search-by-intent flow surfaces the right FIDS endpoint without the agent reading Cirium docs.

Search Jentic for 'get airport arrivals from Cirium', load GET /flex/fids/rest/v1/{format}/{airport}/arrivals, and return a one-paragraph summary of LHR arrivals.

Key Endpoints

2 endpoints — the cirium flightstats fids api powers airport flight information display systems by returning real-time arrivals and departures for a given airport.

METHOD

PATH

DESCRIPTION

GET

/flex/fids/rest/v1/{format}/{airport}/arrivals

Real-time arrivals for an airport

GET

/flex/fids/rest/v1/{format}/{airport}/departures

Real-time departures for an airport

GET

/flex/fids/rest/v1/{format}/{airport}/arrivals

Real-time arrivals for an airport

GET

/flex/fids/rest/v1/{format}/{airport}/departures

Real-time departures for an airport

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Cirium FIDS appId and appKey are stored encrypted in the Jentic vault (MAXsystem). Agents never see the raw key pair; Jentic injects them as query parameters or headers at execution time, isolating credentials per tenant.

Intent-based discovery

Agents search Jentic by intent (e.g., 'get arrivals at an airport') and Jentic returns the matching FIDS endpoint with airport and format parameters already in the schema, so the agent does not need to read Cirium developer documentation.

Time to first call

Direct Cirium FIDS integration: half a day for credential plumbing and response parsing. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cirium FlightStats FIDS API (Studios)

Mirror FIDS spec served from the Cirium Studios developer portal.

Both expose the same arrivals and departures endpoints — choose whichever entry point matches your Cirium contract and developer portal access.

Complementary

Cisco API

Cisco signage and infrastructure APIs can power the screens that render Cirium FIDS data.

Use Cisco for the digital-signage delivery layer and Cirium FIDS for the underlying flight data.

Complementary

Circle Community API

Circle hosts traveller communities that consume Cirium flight-board summaries.

Use Circle to publish a daily flight-disruption recap; use Cirium FIDS to source the underlying real-time data.

FAQs

Specific to using Cirium FlightStats FIDS API API through Jentic.

What authentication does the Cirium FlightStats FIDS API use?

The FIDS API uses an appId and appKey credential pair. They can be supplied as query parameters (appId, appKey) or as HTTP headers with the same names. Through Jentic, both values are stored encrypted in the MAXsystem vault and never enter the agent's prompt.

Can I get both arrivals and departures from one call?

No — the FIDS API uses two separate endpoints. Call GET /flex/fids/rest/v1/{format}/{airport}/arrivals for arrivals and GET /flex/fids/rest/v1/{format}/{airport}/departures for departures. An integration that needs both should call them in parallel.

What are the rate limits for the FIDS API?

Rate limits are not defined in the OpenAPI spec; they are governed by your Cirium FlightStats subscription tier. Coordinate polling frequency with your account agreement and let Jentic surface 429 responses if the limit is exceeded.

How do I fetch an airport board through Jentic?

Run pip install jentic, then search Jentic for 'get airport arrivals from Cirium'. Jentic returns the GET /flex/fids/rest/v1/{format}/{airport}/arrivals operation. Supply format=json and airport=LHR and execute. Sign up at https://app.jentic.com/sign-up.

Which response formats does the FIDS API support?

The format path parameter accepts json or xml. JSON is the typical choice for modern integrations; XML is supported for legacy signage systems.

Can I filter by terminal or airline?

The two FIDS endpoints scope by airport code only. To filter by airline or terminal, post-process the response client-side, or look at other Cirium FlightStats APIs that expose schedule and operational detail.