The Integeration Guide offers a landing page for connecting external systems with the quintessence suite using the JSON api.
This guide describes the phases for integrating with the ASGARD API, as well as all required services
- requesting availabilities
- creating / updating and cancelling bookings
- requesting seat maps and booking seats
- checking SSR availabilities and booking extras
- performing payment
Implementation phases
The basic implementation for a new partner consists of three phases:
Phase 1: Base implementation using the ASGARD Reference Environment
When this is the first implementation of the partner to an ASGARD system, the first phase is to access the ASGARD API sandbox. This sandbox allows access to an API reference environment, hosted by quintessence. On this environment, no customer specific implementations are kept, flights all have the QA (quintessence Airlines) designator and the data is refreshed every week.
Phase 1 requires following steps:
- The partner requests access to the quintessence api documentation and playground.
- A mutual NDA between the partner and quintessence is signed.
- quintessence credentials (userCode, token, client) are sent to the partner.
- The partner connects to the customer test environment.
Phase 2: Connecting to the Test Environment
After the base implementation is finished, a connection to the customer test system can be done. This is necessary, because although the API is standard for all customers, certain customers might have additional information in the API and the customer needs to sign off the connection before a connection to the production environment is allowed.
Phase 2 requires following steps:
- The partner requests access to the customer test environment.
- quintessence requests permission from the customer that a connection can be made.
- If necessary, a VPN connection is set up between the partner and the system location.
- quintessence credentials (userCode, token, client) are sent to the partner.
- The partner connects to the customer test environment.
Phase 3: Connecting to the Production Environment
After successful implementation, the partner can connect to the customer production environment.
Phase 3 requires following steps:
- The partner requests access to the customer production environment.
- quintessence requests permission from the customer that a connection can be made. This requires signoff by quintessence and the customer.
- If necessary, a VPN connection is set up between the partner and the system location.
- quintessence credentials (userCode, token, client) are sent to the partner.
- The partner connects to the customer production environment.
Contact Information for API Connections
Any partner that connects to an ASGARD system needs to provide following contact information:
- Name and email to contact in case of planned events such as installations or other actions where it is to be expected that the system is not available.
- Name and email to contact in case of system disruption, such as system unavailability, known performance issues, connection issues with downstream systems such as NewSkies or Altea.
- Name and email to contact in case of network disruptions, such as problems with the VPN.
- Name and email to contact in case of changes to the API and release changes.
Questions concerning the API in any phase can be addressed to api-support@quintessence.net