Flight upload · API reference
IGC upload (server to server, with the consent version).
POST /v1/flights
Upload a flight track (IGC, GPX or FIT)
Authentication: X-Api-Key header; required scope: scope table.
Request body
multipart/form-data → Body_upload_flight_v1_flights_post
Responses
| Status | Description | Content |
|---|---|---|
200 | Same file already stored (duplicate) | application/json → FlightReceipt |
202 | Successful Response | application/json → FlightReceipt |
401 | code: auth_missing, auth_invalid, auth_revoked | application/json → ErrorBody |
403 | code: auth_scope | application/json → ErrorBody |
409 | code: flight_deleted | application/json → ErrorBody |
413 | code: file_too_large | application/json → ErrorBody |
422 | code: request_invalid, igc_empty, igc_no_fix_records, igc_missing_date, igc_corrupt, igc_no_valid_fix, gpx_invalid, gpx_no_fix_records, gpx_missing_time, gpx_corrupt, gpx_no_valid_fix, fit_invalid, fit_checksum, fit_not_activity, fit_no_fix_records, fit_corrupt, fit_no_valid_fix, flight_date_future | application/json → ErrorBody |
429 | code: rate_limited, quota_exceeded (Retry-After seconds)Headers: Retry-After — Seconds until the exhausted window resets | application/json → ErrorBody |
503 | code: queue_unavailable, storage_unavailable | application/json → ErrorBody |