Model the airport
Stands, gates, adjacencies and the constraints that bind them, described once and reused by every run.
/v1/stands
Full API documentation, built for and by developers. Integrate the optimizers directly into your own software, or build the planning interface your team actually wants, while the modelling, rules and solving run on our side.
Adjacency, tow windows, turnaround reality and the exceptions every airport carries, modelled by people who have run the problem before. That knowledge is inside the API, not something you have to supply.
Different resource problems need different formulations. We select and apply the right solver per problem rather than pointing one engine at every case.
Configured per customer and tuned for the requirements and preferences that never make it into a rule set, which is usually the difference between a plan that is optimal and one your planners will actually run.
Model the airport, manage the rules, run the optimization, resolve the exceptions. Each one is a documented endpoint you can build against.
Stands, gates, adjacencies and the constraints that bind them, described once and reused by every run.
/v1/stands
Create, manage and version the allocation rules the optimizer must respect, so policy is governed rather than hard-coded.
/v1/rules
Resource management optimization runs. Schedule and constraints in as JSON, an optimized allocation plan out.
/v1/optimize
A single-operation solve. Re-assign one flight after a disruption without re-running the whole plan.
/v1/resolve
One call runs a full stand and gate optimization against your model and your rules. No interface required.
Request
POST/v1/optimize/stand-gate
{
"horizon": "2026-09-03/P1D",
"schedule": [
{ "flight": "KL1234",
"in": "08:20",
"out": "10:35",
"type": "B738" }
],
"ruleset": "summer-2026"
}
Response
200 OK{
"allocation": [
{ "flight": "KL1234",
"stand": "A-03",
"gate": "A31" }
],
"conflicts": 0,
"tows": 12,
"audit_id": "chg_9f21c4"
}
Illustrative. The full reference, worked examples and SDKs are in the API documentation.
An API product is only as good as the path to going live. Onboarding, tutorials, documentation and direct access to the engineers who built it are all included.
Guides that get a first optimization run working before the kick-off meeting is over.
Our engineering team works alongside yours while the integration is being built.
Worked examples for the common paths, so going live is a short project rather than a long one.
Full reference, worked examples and SDKs, written for the people doing the integration rather than the people buying it.
Submit tickets and track resolution, with the same engineering team behind them once you are live.
We will walk you through the platform against your own constraints: stands, gates, counters or tows.