🔑 Transaction ID Guidelines

💡

This page provides guidance on how to use the Transaction ID required in PolarHub.
It explains the proper usage and handling of Transaction IDs within API requests to ensure accurate processing and system consistency.

1. Purpose

Transaction ID is required for API flow tracking and continuity.
It ensures that multiple API calls belonging to the same booking session can be linked together.

2. Generation Rules

Max Length: 32 characters

Must be unique

3. Usage Rules

Before Booking

v2 AirShopping → Generate a new Transaction ID

v2 OfferPrice → Use the same Transaction ID

v2 OrderCreate → Use the same Transaction ID

After Booking

v2 OrderRetrieve → Generate a new Transaction ID

Use the same Transaction ID from OrderRetrieve for all subsequent APIs:

v2 ServiceList

v2 SeatAvailability

v2 OrderChange

v2 OrderReshop

v2 OrderCancel

⚠️ Note

If you perform OrderRetrieve for a different booking, you must generate a new Transaction ID.

4. Sample Codes

Java

Javascript

🔑 Transaction ID Guidelines

1. Purpose#

2. Generation Rules#

3. Usage Rules#

4. Sample Codes#

1. Purpose

2. Generation Rules

3. Usage Rules

4. Sample Codes