Pull reconstructed economics straight into your own models. A REST API over the same engine that powers the platform — predictable, versioned, and JSON throughout.
The API is in private preview. Keys are issued per engagement — request access through your account team, and outputs follow the same analytical-aid terms as the platform.
The AvioIQ™ API exposes the reconstruction and simulation engine over HTTPS. Every endpoint returns JSON, uses standard HTTP verbs and status codes, and is versioned in the path so your integration never breaks under you. Numbers come back as tabular, typed values — costs, load factors and probabilities — exactly as the platform computes them.
Authenticate with a bearer token in the Authorization header. Tokens are scoped to your organisation and never expire silently — they are rotated through your account settings.
# Pass your key as a bearer token Authorization: Bearer sk_live_a1b2c3d4e5f6
Send GET for reads and POST with a JSON body for reconstructions and simulations. All requests must be made over HTTPS; calls over plain HTTP are refused.
/routes/reconstruct/routes/{id}/simulations/aircraft/{type}/cost/airports/{iata}Reconstruct a route's economics for a given aircraft type:
# Request POST /v1/routes/reconstruct { "origin": "DEL", "destination": "LHR", "aircraft": "B788", "carrier": "generic-fsc" } # Response { "break_even_load_factor": 112.5, "contribution_margin": -4.2, "p_loss": 0.631, "verdict": "NO-GO" }
Preview keys are limited to 120 requests per minute. Every response carries X-RateLimit-Remaining so you can pace bulk reconstructions; exceeding the limit returns 429 with a Retry-After header.
Errors use conventional HTTP status codes — 400 for a malformed request, 401 for a bad key, 404 for an unknown resource, 429 when rate-limited. The JSON body always includes a code and a human-readable message so failures are easy to handle.