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": 5,
"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 the Dragonpass system, and the prebooking order status is updated, a status change notification will be sent to the client.In some cases, notifications may be delivered more than once or arrive out of order.Duplicate Notifications#
Clients should use the combination of orderId and statusChangedDate to identify duplicate notifications. A notification that has already been processed must not be processed again.Out-of-Order Notifications#
For each order, clients should retain the latest applied statusChangedDate:If an incoming notification has a later timestamp, update the order to its currentStatus.
If it has an earlier timestamp, do not overwrite the current order status.
If it has the same timestamp and the same currentStatus, treat it as a duplicate.
If it has the same timestamp but a different currentStatus, retrieve the latest order status through the order query API to reconcile the conflict.
Clients should acknowledge duplicate and older notifications using the same success response described below.Response#
A push is considered successfully received only if the client returns HTTP status code 200 OK along with following JSON response: