AeroModel
Documentation
plane, plane_iata, plane_icao
Selects the aircraft model. Three variants to express the same thing.
Variants
| Param | Mode | Accepted examples |
|---|---|---|
plane | Auto-detect: slug, IATA, ICAO, or fuzzy match | airbus-a320-200, A320, 320, a320 |
plane_iata | Strict IATA | 320 |
plane_icao | Strict ICAO | A320 |
plane auto-detection is slightly slower (~1 ms) than plane_iata / plane_icao but more tolerant of typos.
API examples
Canonical slug
GET https://api.aeromodel.dash-systems.fr/v1/images/plane?api-key=YOUR_KEY&plane=airbus-a320-200

IATA code
GET https://api.aeromodel.dash-systems.fr/v1/images/plane?api-key=YOUR_KEY&plane_iata=320
Same image as above — the API resolves to airbus-a320-200.
ICAO code
GET https://api.aeromodel.dash-systems.fr/v1/images/plane?api-key=YOUR_KEY&plane_icao=A320
JSON inspection
GET https://api.aeromodel.dash-systems.fr/v1/images/plane?api-key=YOUR_KEY&plane=B789&format=json
Unresolved aircraft
GET https://api.aeromodel.dash-systems.fr/v1/images/plane?api-key=YOUR_KEY&plane=concorde&format=json
{
"error": "plane not found",
"requested": "concorde",
"candidates": [
{ "slug": "boeing-777-300er", "score": 0.31 }
]
}
In image mode (without format=json), the API still returns an image (default default/base.jpg fallback).
Available models
31 Airbus + Boeing models. Full list:
curl -H "x-api-key: YOUR_KEY" \
"https://api.aeromodel.dash-systems.fr/v1/catalog/planes?limit=200"
See /v1/catalog/planes.
Precedence
If multiple are provided: plane_icao > plane_iata > plane. Never send more than one at a time: it is ambiguous and breaks the cache.
See also
airlinefor the same mechanism on the airline side/v1/resolveto validate user input