AeroDataBox website screenshot

AeroDataBox

AeroDataBox is an affordable aviation and flight data API platform tailored for small and medium businesses, individual developers, researchers, and students. Founded in 2019, the platform provides real-time and historical flight status, aircraft information, airport data, delay statistics, and flight alert webhooks through a RESTful API available on RapidAPI and API.Market. AeroDataBox covers global aviation data across airlines, aircraft, airports, and flight operations.

5 APIs 9 Features
AviationFlightsAerospaceFlight DataAirport Data

APIs

AeroDataBox Flight API

Provides real-time and historical flight status information including departure and arrival times, delays, codeshares, and flight number lookups. Supports FIDS (Flight Informati...

AeroDataBox Aircraft API

Search and retrieve aircraft information by tail number, registration, or ICAO24 hex code. Includes airline fleet lookups, aircraft registration history, and aircraft images. Su...

AeroDataBox Airport API

Retrieve airport information by IATA/ICAO code including runway data, local time, solar time, and distance calculations between airports. Search airports by geographic location,...

AeroDataBox Statistical API

Access current and historical airport delay statistics, global delay summaries, daily route statistics, and flight delay data by flight number. Supports date range queries for t...

AeroDataBox Flight Alert API

Create, manage, and monitor webhook subscriptions for real-time flight status alerts. Subscribe to flight events by flight number or airport and receive push notifications to yo...

Collections

Pricing Plans

Rate Limits

Aerodatabox Rate Limits

2 limits

RATE LIMITS

FinOps

Features

Real-Time Flight Status

Live flight tracking with departure and arrival times, current status, and delay information for flights worldwide.

FIDS Airport Departures and Arrivals

Flight Information Display System data showing all departures and arrivals at any airport for a given time window.

Aircraft Search and Profiles

Lookup aircraft by tail number, registration, or ICAO24 hex code with fleet data, registration history, and images.

Airport Search by Location

Find airports by geographic coordinates, IP address geolocation, or free-text search with runway data included.

Flight Delay Statistics

Current and historical delay data for airports and specific flight numbers enabling trend analysis and SLA monitoring.

Webhook Flight Alerts

Push notification subscriptions for real-time flight status changes, supporting event-driven application architectures.

FAA LADD Status

FAA Limiting Aircraft Data Displayed (LADD) status lookup to determine if an aircraft is opted out of public tracking.

Solar Time Calculations

Sunrise, sunset, and solar position data for any airport and date, useful for scheduling and operations planning.

Route Statistics

Daily route statistics for airports showing which routes operate and their frequency.

Use Cases

Flight Tracking Applications

Build consumer or enterprise flight tracking apps using real-time status data for specific flights or all flights at an airport.

Travel Booking Notifications

Send flight status alerts to travelers by integrating webhook subscriptions for departure and arrival updates.

Airport Operations Intelligence

Monitor airport performance, delay patterns, and route activity for operations research and capacity planning.

Airline Research and Analysis

Analyze fleet composition, route networks, and on-time performance for competitive intelligence and market research.

Aviation Data Journalism

Access historical delay and route statistics for data-driven journalism and research on aviation trends.

Aircraft Valuation and Tracking

Track aircraft registrations and history for aviation finance, insurance, and asset management applications.

Trip Planning Tools

Integrate airport search, local time, and solar data into travel planning applications to enhance itinerary building.

Integrations

RapidAPI

Available on RapidAPI Hub with interactive API playground and usage metering for easy developer onboarding.

API.Market

Available on API.Market marketplace with official OpenAPI v3 specifications for download and code generation.

Webhook Endpoints

Integrates with any webhook-capable endpoint for real-time flight status push notifications.

Semantic Vocabularies

Aerodatabox Context

80 classes · 200 properties

JSON-LD

API Governance Rules

AeroDataBox API Rules

22 rules · 11 errors 8 warnings 3 info

SPECTRAL

JSON Structure

Aerodatabox Aircraft Contract Structure

26 properties

JSON STRUCTURE

Aerodatabox Aircraft Search By Enum Structure

0 properties

JSON STRUCTURE

Aerodatabox Airport Codes By Enum Structure

0 properties

JSON STRUCTURE

Aerodatabox Airport Contract Structure

14 properties

JSON STRUCTURE

Aerodatabox Airport Delay Contract Structure

5 properties

JSON STRUCTURE

Aerodatabox Airport Fids Contract Structure

2 properties

JSON STRUCTURE

Aerodatabox Airport Flight Contract Structure

11 properties

JSON STRUCTURE

Aerodatabox Airport Urls Contract Structure

6 properties

JSON STRUCTURE

Aerodatabox Angle Structure

2 properties

JSON STRUCTURE

Aerodatabox Azimuth Structure

2 properties

JSON STRUCTURE

Aerodatabox Codeshare Status Structure

0 properties

JSON STRUCTURE

Aerodatabox Continent Contract Structure

2 properties

JSON STRUCTURE

Aerodatabox Country Contract Structure

2 properties

JSON STRUCTURE

Aerodatabox Date Time Contract Structure

2 properties

JSON STRUCTURE

Aerodatabox Day Time Structure

0 properties

JSON STRUCTURE

Aerodatabox Delay Bracket Contract Structure

4 properties

JSON STRUCTURE

Aerodatabox Distance Structure

5 properties

JSON STRUCTURE

Aerodatabox Engine Type Structure

0 properties

JSON STRUCTURE

Aerodatabox Error Contract Structure

1 properties

JSON STRUCTURE

Aerodatabox Feed Service Enum Structure

0 properties

JSON STRUCTURE

Aerodatabox Feed Service Status Structure

0 properties

JSON STRUCTURE

Aerodatabox Flight Airline Contract Structure

3 properties

JSON STRUCTURE

Aerodatabox Flight Contract Structure

13 properties

JSON STRUCTURE

Aerodatabox Flight Delay Contract Structure

9 properties

JSON STRUCTURE

Aerodatabox Flight Direction Structure

0 properties

JSON STRUCTURE

Aerodatabox Flight Plan Contract Structure

8 properties

JSON STRUCTURE

Aerodatabox Flight Plan Status Structure

0 properties

JSON STRUCTURE

Aerodatabox Flight Rules Structure

0 properties

JSON STRUCTURE

Aerodatabox Flight Search By Enum Structure

0 properties

JSON STRUCTURE

Aerodatabox Flight Status Structure

0 properties

JSON STRUCTURE

Aerodatabox Flight Type Structure

0 properties

JSON STRUCTURE

Aerodatabox License Type Structure

0 properties

JSON STRUCTURE

Aerodatabox Model Flight Time Enum Structure

0 properties

JSON STRUCTURE

Aerodatabox Pressure Structure

3 properties

JSON STRUCTURE

Aerodatabox Resource Contract Structure

7 properties

JSON STRUCTURE

Aerodatabox Runway Contract Structure

9 properties

JSON STRUCTURE

Aerodatabox Solar State Contract Structure

13 properties

JSON STRUCTURE

Aerodatabox Speed Structure

4 properties

JSON STRUCTURE

Aerodatabox Statistic Class Structure

0 properties

JSON STRUCTURE

Aerodatabox Structure

0 properties

JSON STRUCTURE

Aerodatabox Subscriber Contract Structure

2 properties

JSON STRUCTURE

Aerodatabox Subscription Contract Structure

9 properties

JSON STRUCTURE

Aerodatabox Surface Type Structure

0 properties

JSON STRUCTURE

Example Payloads

Aerodatabox Angle Example

2 fields

EXAMPLE

Aerodatabox Azimuth Example

2 fields

EXAMPLE

Aerodatabox Distance Example

5 fields

EXAMPLE

Aerodatabox Pressure Example

3 fields

EXAMPLE

Aerodatabox Speed Example

4 fields

EXAMPLE

Resources

🔗
Documentation
Documentation
🌐
Portal
Portal
🔗
RapidAPI
Marketplace
🔗
API.Market
Marketplace
💰
Pricing
Pricing
📜
TermsOfService
TermsOfService
📜
PrivacyPolicy
PrivacyPolicy
🔗
Contact
Contact
🔗
SpectralRules
SpectralRules
🔗
Vocabulary
Vocabulary
🔗
JSONLD
JSONLD

Sources

Raw ↑
opencollection: 1.0.0
info:
  name: AeroDataBox API - Aviation and Flight API
  version: 1.14.0.0
items:
- info:
    name: Aircraft API
    type: folder
  items:
  - info:
      name: AeroDataBox Single Aircraft (by Tail-number, Mode-S or ID) / TIER 1
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/aircrafts/:searchBy/:searchParam
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: searchBy
        value: ''
        type: path
        description: Criteria to search aircraft by
      - name: searchParam
        value: ''
        type: path
        description: "Value of the search criteria. If `searchBy` is: \r\n* `id`: then this field should be an ID of an aircraft\
          \ (as specified in the database of this API);\r\n* `reg`: then this field should be a tail-number of an aircraft\
          \ (with or without spaces or dashes, any case formats are acceptable, e.g.PH-BXO, DeMhJ), multiple matches are possible\
          \ - see below;\r\n* `icao24`, then this field should be a ICAO 24-bit Mode-S address of an aircraft specified in\
          \ hexadecimal format (e.g. 484161, 483EFD), multiple matches are possible - see below.\r\n\r\n*If multiple matches\
          \ are possible:*\r\n\r\nThere cannot be more than one aircraft actively flying with the same tail-number or ICAO\
          \ 24-bit Mode-S address at any moment of time. \r\nHowever, historically aircraft tail-numbers or addresses may\
          \ be used multiple times by different aircraft.\r\nThis endpoint is supposed to return a **single** aircraft data.\
          \ In case if multiple aircraft satisfy the search criteria, the best match will be chosen as follows:\r\n* If an\
          \ active aircraft is found according to the requested critera, it is returned.\r\n* Otherwise, an aircraft that\
          \ used requested tail-number/address the most recently is returned. \r\n* If usage time may not be determined, the\
          \ aircraft stored in the database the most recently is returned."
      - name: withImage
        value: ''
        type: query
        description: 'Should include aircraft image (default: false).'
      - name: withRegistrations
        value: ''
        type: query
        description: 'Should include the history of aircraft registrations (default: false).'
    docs: '*Returns:* Single aircraft, *best* matching specified search criteria, if found. Please note that all found aircraft
      will be impersonated with registration information matching the requested tail number or Mode-S even though an aircraft
      might be flying under a different registration right now.'
  - info:
      name: AeroDataBox Single Aircraft Registration History (by Tail-number, Mode-S or ID) / TIER 1
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/aircrafts/:searchBy/:searchParam/registrations
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: searchBy
        value: ''
        type: path
        description: Criteria to search aircraft by
      - name: searchParam
        value: ''
        type: path
        description: "Value of the search criteria. If `searchBy` is: \r\n* `id`, then this field should be an ID of an aircraft\
          \ (as specified in the database of this API);\r\n* `reg`, then this field should be a tail-number of an aircraft\
          \ (with or without spaces or dashes, any case formats are acceptable, e.g.PH-BXO, DeMhJ), multiple matches are possible\
          \ - see below;\r\n* `icao24`, then this field should be a ICAO 24-bit Mode-S address of an aircraft specified in\
          \ hexadecimal format (e.g. 484161, 483EFD), multiple matches are possible - see below.\r\n\r\n*If multiple matches\
          \ are possible:* see similar remark to `Single aircraft` endpoint."
    docs: '*Returns:* A list of all known registrations of a single aircraft, *best* matching specified search criteria, if
      found'
  - info:
      name: AeroDataBox Aircraft by Tail-number, Mode-S or ID / TIER 1
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/aircrafts/:searchBy/:searchParam/all
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: searchBy
        value: ''
        type: path
        description: Criteria to search aircraft by
      - name: searchParam
        value: ''
        type: path
        description: "Value of the search criteria. If `searchBy` is: \r\n* `id`, then this field should be an ID of an aircraft\
          \ (as specified in the database of this API);\r\n* `reg`, then this field should be a tail-number of an aircraft\
          \ (with or without spaces or dashes, any case formats are acceptable, e.g.PH-BXO, DeMhJ);\r\n* `icao24`, then this\
          \ field should be a ICAO 24-bit Mode-S address of an aircraft specified in hexadecimal format (e.g. 484161, 483EFD)."
      - name: withImage
        value: ''
        type: query
        description: 'Should include aircraft image (default: false).'
      - name: withRegistrations
        value: ''
        type: query
        description: 'Should include the history of aircraft registrations (default: false).'
    docs: '*Returns:* A list of all aircraft ever matched the requested criteria. Please note that all found aircraft will
      be impersonated with registration information matching the requested tail number or Mode-S even though an aircraft might
      be flying under a different registration right now.'
  - info:
      name: AeroDataBox Airline Fleet / Aircraft List by Airline Code (BETA) / TIER 3
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/airlines/:airlineCode/aircrafts
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: airlineCode
        value: ''
        type: path
        description: "3-character ICAO-code of the airliner (e.g., KLM, ACA); or\r\n2-character IATA-code of the airline (e.g.,\
          \ KL, AC).\r\n            \r\nPlease note that more than one active airline may have the same IATA code, therefore\
          \ IATA codes are not recommended for this endpoint."
      - name: pageSize
        value: ''
        type: query
        description: "The number of returned records will be capped at this value.\r\nMust be a positive value and not exceed\
          \ the limit stipulated by your pricing plan."
      - name: pageOffset
        value: ''
        type: query
        description: The number of records to skip before listing a page of records. In conjunction with `pageSize` effectively
          determines the page number (default  - 0).
      - name: withRegistrations
        value: ''
        type: query
        description: 'Should include the history of aircraft registrations (default: false).'
    docs: "*Returns:* A paged list of aircraft in the fleet of the specified airline. \r\n\r\nThat will include *active* aircraft\
      \ currently flying in an *active* airline, verfified through more than one source.\r\nUnconfirmed sightings of an aircraft\
      \ will not qualify said aircraft to be listed in the fleet."
  - info:
      name: AeroDataBox Aircraft Image by Tail-number / TIER 2
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/aircrafts/reg/:reg/image/beta
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: reg
        value: ''
        type: path
        description: Tail-number of the aircraft (full, stripped and any case formats are acceptable).
    docs: "**What is the aircraft photo?**\r\n\r\nAircraft images are being searched in external sources by certain criteria\
      \ without any manual intervention. \r\nTherefore, false matches may be returned. Only images with licenses approved\
      \ for commercial use are returned. Please be advised that you may be required to mention author attribution before using\
      \ the image.\r\n\r\n*Returns:* Image data with medium-sized direct image URL and licence approved for commercial use\r\
      \nis returned."
  - info:
      name: AeroDataBox Search Active Aircraft Tail Numbers by Term / TIER 2
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/aircrafts/search/term
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: q
        value: ''
        type: query
        description: Search term (min. 4 non whitespace characters length)
      - name: limit
        value: ''
        type: query
        description: Maximum number of items to be returned (max. 10, defaut = 5)
    docs: '*Returns:* List of active aircraft registrations with tail numbers starting from the term.'
- info:
    name: Airport API
    type: folder
  items:
  - info:
      name: AeroDataBox Airport by Code / TIER 1
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/airports/:codeType/:code
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: codeType
        value: ''
        type: path
        description: Type of code to search airport by (`iata` or `icao`)
      - name: code
        value: ''
        type: path
        description: "If `codeType` is:\r\n* `icao`, then this field must be a 4-character ICAO-code of the airport (e.g.:\
          \ EHAM, KLAX, UUEE, etc.);\r\n* `iata`, then this field must be a 3-character IATA-code of the airport (e.g.: AMS,\
          \ SFO, LAX, etc.).\r\n\r\nFull, stripped and any case formats are acceptable."
      - name: withRunways
        value: ''
        type: query
        description: Include runways data (default - false)
      - name: withTime
        value: ''
        type: query
        description: Include current local time (default - false)
    docs: "At the moment airports having both ICAO and IATA code are present in database only.\r\n\r\n*Returns*: Single airport\
      \ data, if found."
  - info:
      name: AeroDataBox Airport Runways / TIER 1
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/airports/:codeType/:code/runways
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: codeType
        value: ''
        type: path
        description: Type of code to search airport by (`iata` or `icao`)
      - name: code
        value: ''
        type: path
        description: "If `codeType` is:\r\n* `icao`, then this field must be a 4-character ICAO-code of the airport (e.g.:\
          \ EHAM, KLAX, UUEE, etc.);\r\n* `iata`, then this field must be a 3-character IATA-code of the airport (e.g.: AMS,\
          \ SFO, LAX, etc.).\r\n\r\nFull, stripped and any case formats are acceptable."
    docs: "**Which runways does this airport have?**\r\n\r\nAt the moment airports having both ICAO and IATA code are present\
      \ in database only.\r\n\r\n*Returns*: Collection of runway data items."
  - info:
      name: AeroDataBox Search Airports by Location / TIER 2
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/airports/search/location
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: lat
        value: ''
        type: query
        description: Latitude location coordinate in decimal format (between -90 and 90)
      - name: lon
        value: ''
        type: query
        description: Longitude location coordinate in decimal format (between -180 and 180)
      - name: radiusKm
        value: ''
        type: query
        description: Radius of search around specified location in kilometers (max. 1000 km)
      - name: limit
        value: ''
        type: query
        description: Maximum number of airports to be returned (max. 250)
      - name: withFlightInfoOnly
        value: ''
        type: query
        description: If set to true, will only return airports which have flight data (scheduled or live) available. Default
          = false.
    docs: "**What are the airports closest to the location?**\r\n\r\nAt the moment airports having both ICAO and IATA code\
      \ and flight schedules are present available only.\r\n\r\n*Returns:* A list of airports found within the specified radius\
      \ around the specified location."
  - info:
      name: AeroDataBox Search Airports by IP Address Geolocation / TIER 2
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/airports/search/ip
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: q
        value: ''
        type: query
        description: A valid public IP v4 address
      - name: radiusKm
        value: ''
        type: query
        description: Radius of search around specified location in kilometers (max. 1000 km)
      - name: limit
        value: ''
        type: query
        description: Maximum number of airports to be returned (max. 250)
      - name: withFlightInfoOnly
        value: ''
        type: query
        description: If set to true, will only return airports which have flight data (scheduled or live) available. Default
          = false.
    docs: "**What are the airports closest to the customer, based on their IP address?**\r\n**What are the airports closest\
      \ to the location determined (geo-located) by a IP address?**\r\n\r\nThis endpoint determines the location by the IP\
      \ address provided and then returns the list of the nearest airports\r\nin the same way as `Search airports by location`\
      \ endpoint does. \r\n\r\nPlease note:\r\n* IP geo-location is not a precise method and it determines an approximate\
      \ location only.\r\n* At the moment airports having both "
  - info:
      name: AeroDataBox Search Airports by Free Text / TIER 2
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/airports/search/term
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: q
        value: ''
        type: query
        description: Search query (min. 3 non whitespace characters length)
      - name: limit
        value: ''
        type: query
        description: Maximum number of airports to be returned (max. 250, defaut = 10)
      - name: withFlightInfoOnly
        value: ''
        type: query
        description: If set to true, will only return airports which have flight data (scheduled or live) available. Default
          = false.
      - name: withSearchByCode
        value: ''
        type: query
        description: "If set to true, will attempt to interpret short words within the search query as IATA or ICAO code\r\
          \nand prioritize exact matches by these codes (they will appear higher than others). \r\nOtherwise, the search by\
          \ code will be completely excluded (only the name of an airport or its city will be searched). \r\nDefault = true."
    docs: "At the moment airports having both ICAO and IATA code and flight schedules are present available only.\r\n\r\n\
      *Returns:* List of airports with names and city names (and IATA/ICAO code, if enabled) matching the search term."
- info:
    name: Flight Alert API
    type: folder
  items:
  - info:
      name: AeroDataBox Create Web-hook Subscription / TIER 4
      type: http
    http:
      method: POST
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/subscriptions/webhook/:subjectType/:subjectId
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: subjectType
        value: ''
        type: path
        description: Subject type
      - name: subjectId
        value: ''
        type: path
        description: "Subject ID. If `subjectType` is: \r\n* `FlightByNumber`, then this field must be a flight number (with\
          \ or without spaces, IATA or ICAO, any case formats are acceptable, e.g. KL1395, Klm 1395);\r\n* `FlightByAirportIcao`,\
          \ then this field must be a 4-character ICAO-code of the airport where flights are operated (e.g.: EHAM, KLAX, UUEE,\
          \ etc.);"
      - name: useCredits
        value: ''
        type: query
        description: "THIS IS A TEMPORARY MIGRATION PARAMETER FOR EASIER TRANSITION. \r\nDefault value: false.\r\nSet to true\
          \ to create a web-hook subscription under the new, credit-based billing model.In this case, the call will be free\
          \ of charge despite Tier 4.\r\nAfter transition this parameter will be ignored as all subscriptions will be created\
          \ as credit-based and you will be able to remove it."
      body:
        type: json
        data: '{}'
    docs: "*This endpoitns is a part of Flight alert PUSH API currently powered by webhooks.  \r\nIf you are running your\
      \ own web service, you can subscribe to flights by number or airport code. \r\nAfter that, your HTTP endpoint will be\
      \ called (notified) whenever the flight information gets \r\nupdated.*\r\n\r\nCreates a web-hook subscription on a subject\
      \ (e.g., flight alerts by number or by airport code).\r\nReturns information about created subscription. Subscription\
      \ ID contained in it\r\ncan be used to refresh or re"
  - info:
      name: AeroDataBox Get Web-hook Subscription / FREE TIER
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/subscriptions/webhook/:subscriptionId
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: subscriptionId
        value: ''
        type: path
        description: Subscription ID
    docs: "*This endpoint is a part of Flight alert PUSH API currently powered by webhooks.  \r\nIf you are running your own\
      \ web service, you can subscribe to flights by number or airport code. \r\nAfter that, your HTTP endpoint will be called\
      \ (notified) whenever the flight information gets \r\nupdated.*\r\n\r\nGets information about an existing active web-hook\
      \ subscription."
  - info:
      name: AeroDataBox Remove Web-hook Subscription / FREE TIER
      type: http
    http:
      method: DELETE
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/subscriptions/webhook/:subscriptionId
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: subscriptionId
        value: ''
        type: path
        description: Subscription ID
    docs: "*This endpoitns is a part of Flight alert PUSH API currently powered by webhooks.  \r\nIf you are running your\
      \ own web service, you can subscribe to flights by number or airport code. \r\nAfter that, your HTTP endpoint will be\
      \ called (notified) whenever the flight information gets \r\nupdated.*\r\n\r\nRemoves the subscription"
  - info:
      name: AeroDataBox List Web-hook Subscriptions / FREE TIER
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/subscriptions/webhook
      headers:
      - name: x-api-market-key
        value: ''
    docs: "*This endpoitns is a part of Flight alert PUSH API currently powered by webhooks.  \r\nIf you are running your\
      \ own web service, you can subscribe to flights by number or airport code. \r\nAfter that, your HTTP endpoint will be\
      \ called (notified) whenever the flight information gets \r\nupdated.*\r\n\r\nGet the list of existing active web-hook\
      \ subscriptions"
  - info:
      name: AeroDataBox Refresh Web-hook Subscription (DEPRECATED) / TIER 4
      type: http
    http:
      method: PATCH
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/subscriptions/webhook/:subscriptionId/refresh
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: subscriptionId
        value: ''
        type: path
        description: Subscription ID
      - name: useCredits
        value: ''
        type: query
        description: "THIS IS A TEMPORARY MIGRATION PARAMETER FOR EASIER TRANSITION. \r\nDefault value: false.\r\nSet to true\
          \ to refresh an existing web-hook subscription under the new, credit-based billing model. In this case, the call\
          \ will be free of charge despite Tier 4."
    docs: " *This endpoitns is a part of Flight alert PUSH API currently powered by webhooks.  \r\n If you are running your\
      \ own web service, you can subscribe to flights by number or airport code. \r\n After that, your HTTP endpoint will\
      \ be called (notified) whenever the flight information gets \r\n updated.*\r\n \r\n Refreshes an existing web-hook subscription\r\
      \n \r\n If the subscription had an expiration date-time set when created, this endpoint \r\n will extend it by the same\
      \ period of time as the one it was originall"
  - info:
      name: AeroDataBox Get Web-hook Subscription Balance / FREE TIER
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/subscriptions/balance
      headers:
      - name: x-api-market-key
        value: ''
    docs: "The current web-hook subscription balance information.\r\nThis is separate from your API marketplace quota and\
      \ is used solely for billing of web-hook subscriptions.\r\nFor more details about how flight alert API billing works,\
      \ refer to our guide at https://aerodatabox.com/flight-alert-api-2026/"
  - info:
      name: AeroDataBox Refill Web-hook Subscription Balance / TIER 1
      type: http
    http:
      method: POST
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/subscriptions/balance/refill
      headers:
      - name: x-api-market-key
        value: ''
      body:
        type: json
        data: '{}'
    docs: "Performs refill operation on the web-hook subscription balance by the specified amount of credits.\r\nThis balance\
      \ is separate from your API marketplace quota and is used solely for billing of web-hook subscriptions.\r\n\r\nIn the\
      \ request body, you specify how many credits you want to add. This is a variable-rate endpoint and the amount of API\
      \ units \r\ndeducted from your API quota depends on the amount of flight alerts credits requested.\r\nThe conversion\
      \ rate is: 1 credit = 1 API unit.\r\n\r\nAdditional lim"
- info:
    name: Flight API
    type: folder
  items:
  - info:
      name: AeroDataBox Flight Status (single Day) / TIER 2
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/flights/:searchBy/:searchParam
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: searchBy
        value: ''
        type: path
        description: Criteria to search flight by
      - name: searchParam
        value: ''
        type: path
        description: "Value of the search criteria. If `searchBy` is: \r\n* `number`, then this field shoud be Flight number\
          \ (with or without spaces, IATA or ICAO, any case formats are acceptable, e.g. KL1395, Klm 1395)\r\n* `callsign`,\
          \ then this field should be ATC call-sign of the flight (with or without spaces, any case formats are acceptable,\
          \ e.g.AFL1482, nca 008X);\r\n* `reg`, then this field should be Aircraft tail-number (with or without spaces or\
          \ dashes, any case formats are acceptable, e.g.PH-BXO, DeMhJ);\r\n* `icao24`, then this field should be Aircraft\
          \ ICAO 24-bit Mode-S address specified in hexadecimal format (e.g. 484161, 483EFD)."
      - name: dateLocalRole
        value: ''
        type: query
        description: "* If set to `Both` (default, recommended for best results) then the dateLocal parameter shall be considered\
          \ as both departure and arrival date. If a flight departs OR arrives on that date (in the local timezone of the\
          \ origin or destination, respectively), it will be returned.\r\n* If set to `Departure` then the dateLocal parameter\
          \ shall be considered as departure date only. Only the flights departing on that date (in the local timezone of\
          \ origin) will be returned.\r\n* If set to `Arrival` then the dateLocal parameter shall be considered as arrival\
          \ date only. Only the flights arriving on that date (in the local timezone of destination) will be returned."
      - name: withAircraftImage
        value: ''
        type: query
        description: "Should include aircraft image (default: false).\r\n\r\nAircraft images are being searched in external\
          \ sources by certain criteria without any manual intervention. \r\nTherefore, false matches may be returned. Only\
          \ images with licenses approved for commercial use are returned. \r\nPlease be advised that you may be required\
          \ to mention author attribution before using the image."
      - name: withLocation
        value: ''
        type: query
        description: 'Should include real-time positional data, e.g.: location, speed, altitude, etc., if available (default:
          false).'
      - name: withFlightPlan
        value: ''
        type: query
        description: "Should include the flight plan filed with the ATC for the flight (default: false).\r\n\r\n* NOTE 1:\
          \ Generally availabe to flights departing from, arriving to or crossing the mainland U.S. airspace.\r\n* NOTE 2:\
          \ Only available on Basic and Ultra, Ultra-2 and Mega pricing plans.\r\n* NOTE 3: If set to true and the flight\
          \ plan is found for one or more flights returned, **the request will be billed as 2 requests** against your API\
          \ quota (except on Mega plan)."
    docs: "**What is the status of a specific flight?**\r\n**What is the historical status or schedule of a specific flight\
      \ on a specific date in past or in future?**\r\n\r\nThis endpoint returns data about a specific flight  live flight\
      \ status (if the flight is within the coverage and not in distant future), \r\nor flight schedule data otherwise.\r\n\
      \r\nIf `dateLocal` is specified, gets data about flight(s) departing or arriving on the day specified (local time).\r\
      \nOtherwise, gets data about the status of flight(s) op"
  - info:
      name: AeroDataBox Flight Status (single Day) / TIER 2
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/flights/:searchBy/:searchParam/:dateLocal
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: searchBy
        value: ''
        type: path
        description: Criteria to search flight by
      - name: searchParam
        value: ''
        type: path
        description: "Value of the search criteria. If `searchBy` is: \r\n* `number`, then this field shoud be Flight number\
          \ (with or without spaces, IATA or ICAO, any case formats are acceptable, e.g. KL1395, Klm 1395)\r\n* `callsign`,\
          \ then this field should be ATC call-sign of the flight (with or without spaces, any case formats are acceptable,\
          \ e.g.AFL1482, nca 008X);\r\n* `reg`, then this field should be Aircraft tail-number (with or without spaces or\
          \ dashes, any case formats are acceptable, e.g.PH-BXO, DeMhJ);\r\n* `icao24`, then this field should be Aircraft\
          \ ICAO 24-bit Mode-S address specified in hexadecimal format (e.g. 484161, 483EFD)."
      - name: dateLocal
        value: ''
        type: path
        description: 'Local date of departure or arrival (in format: YYYY-MM-DD, e.g.: 2019-08-29). Maximum/minimum allowable
          date is determined by the current data coverage limitations and your pricing plan.'
      - name: dateLocalRole
        value: ''
        type: query
        description: "* If set to `Both` (default, recommended for best results) then the dateLocal parameter shall be considered\
          \ as both departure and arrival date. If a flight departs OR arrives on that date (in the local timezone of the\
          \ origin or destination, respectively), it will be returned.\r\n* If set to `Departure` then the dateLocal parameter\
          \ shall be considered as departure date only. Only the flights departing on that date (in the local timezone of\
          \ origin) will be returned.\r\n* If set to `Arrival` then the dateLocal parameter shall be considered as arrival\
          \ date only. Only the flights arriving on that date (in the local timezone of destination) will be returned."
      - name: withAircraftImage
        value: ''
        type: query
        description: "Should include aircraft image (default: false).\r\n\r\nAircraft images are being searched in external\
          \ sources by certain criteria without any manual intervention. \r\nTherefore, false matches may be returned. Only\
          \ images with licenses approved for commercial use are returned. \r\nPlease be advised that you may be required\
          \ to mention author attribution before using the image."
      - name: withLocation
        value: ''
        type: query
        description: 'Should include real-time positional data, e.g.: location, speed, altitude, etc., if available (default:
          false).'
      - name: withFlightPlan
        value: ''
        type: query
        description: "Should include the flight plan filed with the ATC for the flight (default: false).\r\n\r\n* NOTE 1:\
          \ Generally availabe to flights departing from, arriving to or crossing the mainland U.S. airspace.\r\n* NOTE 2:\
          \ Only available on Basic and Ultra, Ultra-2 and Mega pricing plans.\r\n* NOTE 3: If set to true and the flight\
          \ plan is found for one or more flights returned, **the request will be billed as 2 requests** against your API\
          \ quota (except on Mega plan)."
    docs: "**What is the status of a specific flight?**\r\n**What is the historical status or schedule of a specific flight\
      \ on a specific date in past or in future?**\r\n\r\nThis endpoint returns data about a specific flight  live flight\
      \ status (if the flight is within the coverage and not in distant future), \r\nor flight schedule data otherwise.\r\n\
      \r\nIf `dateLocal` is specified, gets data about flight(s) departing or arriving on the day specified (local time).\r\
      \nOtherwise, gets data about the status of flight(s) op"
  - info:
      name: AeroDataBox Flight History and Schedule (range of Days) / TIER 3
      type: http
    http:
      method: GET
      url: https://prod.api.market/api/v1/aedbx/aerodatabox/flights/:searchBy/:searchParam/:dateFromLocal/:dateToLocal
      headers:
      - name: x-api-market-key
        value: ''
      params:
      - name: searchBy
        value: ''
        type: path
        description: Criteria to search flight by
      - name: searchParam
        value: ''
        type: path
        description: "Value of the search criteria. If `searchBy` is: \r\n* `number`, then this field shoud be Flight number\
          \ (with or without spaces, IATA or ICAO, any case formats are acceptable, e.g. KL1395, Klm 1395)\r\n* `callsign`,\
          \ then this field should be ATC call-sign of the flight (with or without spaces, any case formats are acceptable,\
          \ e.g.AFL1482, nca 008X);\r\n* `reg`, then this field should be Aircraft tail-number (with or without spaces or\
          \ dashes, any case formats are acceptable, e.g.PH-BXO, DeMhJ);\r\n* `icao24`, then this field should be Aircraft\
          \ ICAO 24-bit Mode-S address specified in hexadecimal format (e.g. 484161, 483EFD)."
      - name: dateFromLocal
        value: ''
        type: path
        description: 'Beginning of the range of local dates of departure or arrival (in format: YYYY-MM-DD, e.g.: 2019-08-29).
          Maximum/minimum allowable value is determined by the current data coverage limitations and your pricing plan.'
      - name: dateToLocal
        value: ''
        type: path
        description: 'End of the range of local dates of departure or arrival (in format: YYYY-MM-DD, e.g.: 2019-08-29). Maximum/minimum
          allowable value is determined by the current data coverage limitations and your pricing plan. This date must be
          bigger than the dateFromLocal. The maximum difference between this date and dateFromLocal is limited and is determined
          by your pricing plan (ranging from 7 to 30 days as per

# --- truncated at 32 KB (65 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/aerodatabox/refs/heads/main/apis.yml