Fast Track

Fast Track Prebooking

For transport hub–related services, including lounge and Fast Track prebooking, each service point (e.g., a specific lounge or Fast Track lane) is treated as an individual resource. The prebooking process is resource-specific and follows these main steps:

Availability Check

Query the availability of a specific resource for the desired date and time.

Prebooking Creation

If available, a prebooking order can be created. The order remains cancellable within the applicable cancellation policy window.

Service Access

At the prebooking time, the user can access the service by presenting the credential provided in the order confirmation.

Voucher Generation & Presentation

For Fast Track prebooking, voucher presentation is based on the vouchersList returned in the order response. A single order may share one voucher across all passengers, or it may include separate vouchers for each passenger, depending on the Fast Track lane and partner configuration.

Dragonpass will split and return the voucher information in a passenger-friendly structure. Clients do not need to determine whether the voucher is shared or unique by themselves. They only need to render each voucher object according to the returned vouchersList.

For prebooking orders, always use the voucher value from vouchersList. Using the E-pass ID may lead to service denial.

Example:

Shared Voucher Example

Separate Voucher Example

"vouchersList": [
    {
        "firstName": "Dragonpass",
        "lastName": "Dragonpass",
        "voucher": "668800008888",
        "voucherType": 1
    },
    {
        "firstName": "Dragonpass",
        "lastName": "Dragonpass",
        "voucher": "668800008888",
        "voucherType": 0
    }
]

Different resources may return different voucher types, the way to present the voucher depends on voucherType:

voucherType	Type	Instruction
1	QR Code	Convert the voucher into a QR code and display
2	Barcode	Convert the voucher into a barcode and display
3	Image	Display the image directly
4	Verification Code	Show the code directly to staff

You may also refer to the UI Design Guidelines for voucher rendering.

Asynchronous Order Processing

When creating an order, clients can enable asynchronous processing by setting the async parameter to true.

With asynchronous processing enabled, Dragonpass will first perform the required validations, such as entitlement/usage eligibility, available balance, pricing, and other mandatory checks. Once these validations are completed and the order has been successfully accepted, the API may return the order with a 5-Pending status.

"status": 5

A 5-Pending status means that the order request has been successfully received and accepted by Dragonpass for further processing. It does not mean that the service has been confirmed or is ready for use. Clients should not present the order to the end user as a confirmed notification while it remains in this status.

The order becomes valid for service usage only after the processing is completed successfully and the order status changes to 1-Confirmed.

For Fast Track Module, clients can use resources at Suvarnabhumi Airport(BKK) to test the Pending status flow. Orders created for these resources will initially remain in Pending status approximately 30 seconds.

Clients can obtain the latest order status using either of the following approaches:

Order Status Polling
Periodically call the Order Details API using the orderId until the order reaches a final or actionable status, such as 1-Confirmed or 10-Failed.
→ Retrieve E-pass Usage Order Details
→ Retrieve Membership Usage Order Details

Webhook Notification
Subscribe to DP webhook notifications. Dragonpass will send an order status update notification when the order status changes, allowing the client to update the order without continuously polling the API.
→ Prebooking Order Status Change Event

For the best integration experience, webhook notifications are recommended as the primary mechanism, while the Order Details API can be used as a fallback or for status reconciliation.

Create Prebooking Orders

→ Use /orders/fastTrack/ePasses/prebooking to place a Fast Track prebooking order with an E-pass.

Request

In our API body, we separate basic information and order specific information using the extra object.

Create E-pass Prebooking Order - Fast Track - Request

As required by airports and partners, certain resource prebooking orders will need the passenger's name, email, phone number, or flight number for booking information.
For the required information at specific locations, please refer to theprebookingRequiredInfoprovided in the /resources/{resourceId} response.

According to the requirements of the service resources, Dragonpass only collects the necessary personally identifiable information (PII) for each order. Even if clients provide additional or unnecessary PII, we will not store it. Such data will be discarded and displayed as null in the order details.

{
    "module": 2,
    "ePassId": "1788000066668888",
    "extra": {
        "prebookingToken": "85c69b8e790befc7e94870ec269c3f1d",
        "passengers": [
            {
                "firstName": "Dragonpass",
                "lastName": "Dragonpass",
                "passengersType": 1,
                "leadPassenger": true
            }
        ],
        "prebookingRequiredInfo": {
            "firstName": "Dragonpass",
            "lastName": "Dragonpass",
            "email": "developer@dragonpass.com",
            "phoneNumber": "8081966002",
            "callingCode": "44",
            "transportNumber": "EK0001"
        }
    }
}

Response

Create E-pass Prebooking Order - Fast Track - Response

{
    "code": 0,
    "data": {
        "status": 1,
        "module": 2,
        "ePassId": "1788000066668888",
        "category": 2,
        "orderId": "DP00000000000001",
        "orderCreatedDate": "2024-12-31T00:00:00+00:00",
        "orderCancelledDate": null,
        "extra": {
            "prebookingDate": "2025-10-01T10:30",
            "usageDate": "",
            "usedUsages": 1,
            "resourceId": "C00001",
            "resourceName": "Dragonpass Fast Track Service",
            "iata": "MAN",
            "transportHubName": "Manchester Airport",
            "terminal": "Terminal 1",
            "city": "Manchester",
            "countryOrRegion": "GB",
            "passengers": [
                {
                    "firstName": "Dragonpass",
                    "lastName": "Dragonpass",
                    "passengersType": 1,
                    "leadPassenger": true
                }
            ],
            "vouchersList": [
                {
                    "firstName": "Dragonpass",
                    "lastName": "Dragonpass",
                    "voucher": "668800008888",
                    "voucherType": 1
                }
            ],
            "prebookingRequiredInfo": {
                "firstName": "Dragonpass",
                "lastName": "Dragonpass",
                "email": "developer@dragonpass.com",
                "phoneNumber": "8081966002",
                "callingCode": "44",
                "flightNumber": "EK0001"
            }
        }
    }
}

Cancel Prebooking Orders

→ Use the /orders endpoint to cancel a prebooking order by order ID.

A prebooking order can be cancelled in accordance with the cancellation policy. Once cancelled, the corresponding usages will be refunded to the E-pass.

Whether a prebooking order can be canceled depends on the cancellation policy provided in the /resources/{resourceId} response, usually:

24-72 hours before the service time.

Please note that once a prebooking order is cancelled, it cannot be recovered.

Fast Track Prebooking#

Voucher Generation & Presentation#

Asynchronous Order Processing#

Create Prebooking Orders#

Cancel Prebooking Orders#

Fast Track Prebooking

Voucher Generation & Presentation

Asynchronous Order Processing

Create Prebooking Orders

Cancel Prebooking Orders