You'll find separate lists for our Sandbox and Production environments, allowing you to easily identify which carriers are available for development, testing, and live deployment.
βCarrier Coverage#
| Airline Code | Full Name | Environment |
|---|
| AA | American Airlines | Sandbox + Production |
| AF | Air France | Sandbox + Production |
| AY | Finnair | Sandbox + Production |
| BA | British Airways | Sandbox + Production |
| EK | Emirates | Sandbox + Production |
| HA | Hawaiian Airlines | Sandbox + Production |
| KL | KLM | Sandbox + Production |
| LH | Lufthansa | Sandbox + Production |
| LX | Swiss Air | Sandbox + Production |
| OS | Austrian Airlines | Sandbox + Production |
| QR | Qatar Airways | Sandbox + Production |
| SQ | Singapore Airlines | Sandbox + Production |
| TR | Scoot | Sandbox + Production |
| TK | Turkish Air | Sandbox + Production |
| AS | Alaska Airlines | Sandbox + Production (POS US only) |
This guide outlines the step-by-step process for integrating with our PolarHub API. Itβs designed to help you get connected quickly and efficiently, from initial setup to going live. Weβll walk you through the necessary steps for accessing our sandbox environment, conducting tests, and moving your integration into production. Our goal is to make the process as smooth as possible so you can start leveraging our multi-airline connectivity with minimal friction.
The HaloSync application form and contract must be signed before proceeding with the following steps.
Sandbox Integration Process#
1
Submit Credential Request
2
Receive Sandbox Package
You will receive:
Albus admin account informationYou can check PolarHub Sandbox Credential
Luna account could be created through the Albus
3
Connection Verification
Confirm successful API connection using the provided credentials
4
Develop and Teat in Sandbox
Follow the integration guide and implement APIs. Contact halosync_support@halocorp.kr if you need technical help.
5
Submit Sandbox UAT Results
Please refer to the PolarHub UAT cases below and submit the results for verification.
π Reference:
PolarHub UAT Cases6
UAT Approval
HaloSync team verifies if all UAT cases are successful. Once approved, you will receive production credentials and related UAT cases.
Moving to Production#
1
Receive Production Credential
You can check PolarHub production credential through the Albus
2
Verify Connection
Test connectivity with production credentials
3
Develop & Test in Production
Implement and test all required APIs in production
4
Submit Production UAT Results
Please refer to the PolarHub UAT cases below and provide UAT test results for Production.
π Reference:
PolarHub UAT Cases5
UAT Approval
HaloSync team validates results and approves production usage
6
Go Live
β
Start selling NDC content in production!