Skip to main content

Documentation Index

Fetch the complete documentation index at: https://teardowns.aero/docs/llms.txt

Use this file to discover all available pages before exploring further.

Teardowns on the public API support two asset_type values today aircraft and engine so there are two vocabularies you’ll work with. Where the web UI shows you a dropdown of these, the API takes the human-readable name directly.
APU and landing-gear flows are UI-only at the moment. The public API doesn’t accept asset_type=apu or asset_type=landing_gear on teardown writes, and the matching vocabulary fields aren’t on the public request schema. Listings still accept apu_model names for APU listings see the listings docs.

​
The two vocabularies

asset_typeVocabulary field on the bodyExample values
aircraftaircraft_typeA320-200, 737-700, A350-1000
engineengine_modelCFM56-5B, Trent 1000, GEnx-1B
You set exactly one per teardown, matching the asset_type you chose. The other is ignored if you send it.

​
How resolution works

When you POST or PATCH a teardown:
  1. The server reads asset_type first.
  2. It then reads the matching vocabulary field (e.g., aircraft_type).
  3. It looks up the active row in the corresponding table whose name matches your value, case-insensitively.
So "aircraft_type": "a320-200" and "aircraft_type": "A320-200" both resolve to the same row. Inactive vocabulary rows are not accepted.

​
Unknown values are friendly errors

If you send a name that doesn’t match any active row, the response is a 400 unknown_vocabulary with the full allowed list in the body: 
{
  "detail": {
    "error_code": "unknown_vocabulary",
    "field": "aircraft_type",
    "value": "A320-poo",
    "valid_values": [
      "737-700",
      "737-800",
      "747-400",
      "A320-200",
      "A321-200",
      "A350-900",
      "A350-1000",
      ...
    ],
    "message": "Unknown aircraft_type: 'A320-poo'. See valid_values."
  }
}
This is self-correcting your ERP can dump valid_values into its config, prompt the user to pick the right one, retry. No docs lookup needed.

​
Discovering valid values up front

You don’t have to wait for an unknown_vocabulary error to find out what’s accepted. The full active lists are below, grouped by manufacturer. All values are matched case-insensitively, send them exactly as written. The Aircraft types and Engine models tabs apply to both teardowns and listings. The APU models tab applies to listings only (listing_type=apu) the teardown surface doesn’t accept APU asset types today.
Airbus
  • A300
  • A310-300
  • A318
  • A319
  • A320
  • A320-200
  • A321
  • A321-200
  • A330
  • A330-200
  • A330-300
  • A340-300
  • A340-600
  • A350-900
  • A350-1000
  • A380
Boeing
  • 737-200
  • 737-200 VIP
  • 737-300
  • 737-400
  • 737-500
  • 737-600
  • 737-700
  • 737-800
  • 737-900
  • 737 MAX 8
  • 737 MAX 9
  • 747-400
  • 747-8
  • 757-200
  • 757-300
  • 767-200
  • 767-300ER
  • 777-200
  • 777-200ER
  • 777-300
  • 777-300ER
  • 787-8
  • 787-9
Embraer
  • E170
  • E175
  • E190
  • E195
  • ERJ-135
  • ERJ-145
  • ERJ-145LR
Bombardier
  • CRJ-100
  • CRJ-200
  • CRJ-700
  • CRJ-900
  • CRJ-900ER
  • CRJ-1000
  • Challenger 604
  • Challenger 605
  • Global 5000
  • Global Express
  • Learjet 45
De Havilland Canada
  • DHC-8 Q100
  • DHC-8 Q200
  • DHC-8 Q300
  • DHC-8 Q400
  • DHC 8-400
ATR
  • ATR 42
  • ATR 72
McDonnell Douglas
  • DC-9
  • DC-10
  • MD-11
  • MD-80
  • MD-90
Lockheed
  • L-1011
Fokker
  • Fokker 50
  • Fokker 100
Saab
  • Saab 340
  • Saab 2000
Gulfstream
  • Gulfstream G550
  • Gulfstream G650
  • Gulfstream GV
Dassault
  • Falcon 900
  • Falcon 2000
Cessna
  • Citation X
These lists are sourced directly from the active vocabulary tables and may drift over time as new types are added. If your ERP sees an unknown_vocabulary error, branch on the valid_values array returned in the response body, that array is always current.