🔑 Transaction ID Guidelines

💡 This page defines the Transaction ID used across PolarHub APIs — its format, how to generate and propagate it, and how it is used when reporting issues.

1. Definition

A Transaction ID is a unique identifier that correlates all API calls belonging to the same session, so that a single booking flow can be traced end-to-end.

2. Purpose

The Transaction ID enables API flow tracking and continuity. It links multiple API calls in the same booking session, and serves as the primary tracking key when investigating issues.

3. Location

The Transaction ID is carried in HTTP headers, on both request and response.

Direction	Header	Required
Request	`[TBD: 헤더 키명 확인]`	Yes
Response	(same as request)	Echoed

⚠️ The same Transaction ID is echoed back in the response so it can be captured from logs for tracing.

4. Format

Max length: 32 characters

Uniqueness: must be unique per session

5. Generation & Propagation

Generation — Generate a unique value (e.g., a UUID with hyphens removed yields 32 characters).

Propagation — Before Booking

v2 AirShopping → Generate a new Transaction ID

v2 OfferPrice → use the same Transaction ID

v2 OrderCreate → use the same Transaction ID

Propagation — After Booking

v2 OrderRetrieve → Generate a new Transaction ID

v2 ServiceList / SeatAvailability / OrderChange / OrderReshop / OrderCancel → use the same Transaction ID from OrderRetrieve

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

6. Use in Issue Reporting

When reporting an error or incident, the Transaction ID is required. It is the key our support team uses to locate your request in the logs. For the full reporting procedure and other required fields, see Reporting an Issue (Operations & Support → Reporting an Issue).

7. Sample Codes

Java

Javascript

🔑 Transaction ID Guidelines

1. Definition#

2. Purpose#

3. Location#

4. Format#

5. Generation & Propagation#

6. Use in Issue Reporting#