Description#
Event Name: prebooking.statusChangedPrevious and current status
Trigger Condition: When the status of a prebooking order changes (e.g., confirmed, cancelled, modified, redeemed).
Supported Modules#
Message Example#
{
"eventType":"prebooking.statusChanged",
"orderId": "PB00000000000001",
"programId": "1888000000000001",
"dpId": "8888000066668888",
"module": 1,
"previousStatus": 0,
"currentStatus": 1,
"statusChangedDate": "2025-01-01T10:00:00+00:00",
"remarks": null
}
Field Descriptions#
| Column | Description | Example |
|---|
| eventType | Specifies the type of push event. Used to distinguish between different kinds of notifications, e.g., walkin.redemption, prebooking.statusChanged. | prebooking.statusChanged |
| orderId | Unique identifier of the usage order, generated by DragonPass each time a user utilizes their Membership or E-pass. | DP00000000000001 |
| programId | Unique identifier of the program. Assigned by DragonPass when a new program was onboarded. | 1888000000000001 |
| dpId | Unique ID for the DragonPass Membership or E-pass. | 8888000066668888 |
| module | Specifies the module associated with the order(s), e.g. "Lounge", "Fast Track". | 1 |
| previousStatus | The status of the prebooking order before the change occurred. | 5 |
| currentStatus | The status of the prebooking order after the change occurred. | 2 |
| statusChangedDate | The timestamp when the prebooking order status transition took place (in UTC+0). | 2024-12-31T00:00:00+00:00 |
| remarks | Additional information provided only in special cases, initiated by DragonPass. For example, this field may contain details when certain resources become unavailable due to unexpected circumstances. | string |
Event Logic#
After the necessary steps are completed within DragonPass system, and the prebooking order status is updated, a status change notification will be sent to the client.In some cases, status change notifications may arrive out of sequence due to network latency or other unforeseen issues. To ensure consistency, clients must handle idempotency based on the combination of Order Id and Status Changed Date.
Response#
A push is considered successfully received only if the client returns HTTP status code 200 OK along with following JSON response: