The autorouter web interface is built on top of a RESTful API exporting the complete autorouter functionality. This application programming interface (API) is also available to 3rd party applications.<\/p>\n
Clients issue HTTPS requests to the autorouter server, making use of the HTTP request types GET, POST, PUT and DELETE with request specific URLs and passing input data as either HTTP parameters or JSON formatted messages in the request body. Responses can be HTTP status codes or JSON messages in the body.<\/p>\n
The API is structured around the following principal entities:<\/p>\n
Typically, operations are performed on these entities where GET retrieves information, POST creates an entity or performs an operation, PUT updates\/replaces an entity and DELETE removes an entity.<\/p>\n
The web frontend to autorouter contains an email \/ password authentication and uses session cookies to authenticate individual API calls during the lifetime of the session. This is typically not practical for API users which is why an additional method is offered.<\/p>\n
You will find more information on how to perform the authentication here: Authentication via OAuth 2.0<\/a><\/p>\n The RESTful API is located at<\/p>\n for example a HTTP POST to<\/p>\n to create a new route.<\/p>\n API requests return a HTTP status code. The following status codes are used:<\/p>\n In most cases you will get a more descriptive error message in the body of the response, formatted as a JSON object:<\/p>\n error<\/strong> is a human-readable message intended for display or logging. code<\/strong> is a stable, machine-readable identifier you can safely branch on in your application (for example The API is guaranteed to remain interface compatible in line with the Semantic Versioning<\/a> specification in which a version is comprised of 3 numbers in the format MAJOR.MINOR.PATCH where an increment of each component has the following meaning:<\/p>\n Some APIs are documented as “unstable<\/strong>“. For these APIs, the above interface stability guarantee does not apply. They may see incompatible changes between minor version updates. If you rely on an unstable API, please contact us to discuss your needs and how we can promote it to stable API. Some APIs are not documented at all and we strongly advise against inspecting the web frontend data exchange to determine the use of these undocumented APIs as we regularly perform incompatible changes to such APIs. Again, if you believe such functionality is relevant to you, contact us and ask for a stable and documented interface.<\/p>\n To query the current version of the API, perform the following request<\/p>\n This returns a JSON structure containing the major and minor version number.<\/p>\n All invocations of the API contain the major and minor number as part of the URL (https:\/\/api.autorouter.aero\/v1.0). This allows the platform to introduce changes to the API but maintain backwards compatibility by continuing to provide the previous version of the API which requires knowing which version of the API the client expects. If you omit the version number, the server will assume the latest version of the API. It is beneficial to check back regularly for the latest API revision and adapt your application to make use of it. This will both give you access to added capabilities and keep you close to development so that when a major update happens and a previous version is finally retired from service, you most likely won’t have to make any changes or only small changes to your application. The API changes for each version number are documented in the API changelog<\/a>.<\/p>\n Certain events trigger messages that clients can subscribe to using the message queue facility<\/a>.<\/p>\nAPI invocation<\/h1>\n
https:\/\/api.autorouter.aero\/v1.0\/<group>\/<request><\/pre>\n
https:\/\/api.autorouter.aero\/v1.0\/router<\/pre>\n
\n
\nRequest completed successfully.<\/li>\n
\nInvalid request data. Some of the data passed to the call is not valid.<\/li>\n
\nNot authorized. You did either supplier no credentials, expired credentials or invalid credentials. You can try the request again with correct credentials.<\/li>\n
\nAccess denied. You do not have permission to access the resource or perform the operation. Repeating the request will not help.<\/li>\n
\nObject not found. Most likely an object referenced through the request URL was not found or could not be accessed due to insufficient privileges (the API will not tell you that for security reasons).<\/li>\n
\nConflict. The request could not be completed because it conflicts with the current state of the resource, for example filing a flight plan that has already been filed, or creating an aircraft type that already exists. Repeating the request unchanged will not help; the underlying state must change first.<\/li>\n
\nUnprocessable entity. The request was well-formed but failed validation, for example a flight plan that does not pass IFPS validation or was rejected by Eurocontrol. The response body contains details on what failed.<\/li>\n
\nToo many requests. You have exceeded a rate limit or a plan limit. Wait before retrying.<\/li>\n
\nInternal error processing the request. This shouldn’t really happen so we’re grateful for reports and scenarios where this happens.<\/li>\n
\nBad gateway. An upstream system the request depends on (for example Eurocontrol\/IFPS) returned an invalid or unexpected response. The request can be retried.<\/li>\n
\nThe server cannot handle the request at the given time due to capacity issues. The request should be attempted again at a later time. If the issue is frequent or prevails over a longer period of time, a support ticket should be opened.<\/li>\n
\nGateway timeout. An upstream system the request depends on did not respond in time. The request can be retried.<\/li>\n<\/ul>\n{\n \"error\": \"human readable error message\",\n \"code\": \"STABLE_MACHINE_READABLE_CODE\",\n \"data\": null\n}<\/pre>\nDUPLICATE_FILING<\/code> or FILING_VALIDATION_FAILED<\/code>); it may be null<\/code> for generic errors. data<\/strong> carries optional structured detail relevant to the error, such as a list of validation failures, and may also be null<\/code>.<\/p>\nVersioning<\/h1>\n
\n
\nWhen incompatible API changes are made.<\/li>\n
\nWhen functionality is added in a backwards-compatible manner.<\/li>\n
\nWhen backwards-compatible bug fixes are applied.<\/li>\n<\/ul>\nHTTP GET https:\/\/api.autorouter.aero\/v1.0\/system\/version<\/pre>\n
{\n \"major\": 1,\n \"minor\": 0<\/span>,\n \"patch\": 19,\n \/* whether this is a production system (false for test\/sandbox system) *\/\n \"production\": true,\n \/* the minimum version of the API supported by the server *\/\n \"minVersion\":\n {\n \"major\": 1,\n \"minor\": 0\n },\n \/* whether the system considers the call to be authenticated *\/\n \"auth\": false\n}<\/pre>\nMessages<\/h1>\n
Samples<\/h1>\n