DragonPass API Developer Platform
v2
  • v2
  • v1
Homepage
Official SiteContact Us
Homepage
Official SiteContact Us
API Version
v2
  • v2
  • v1
v2
  • v2
  • v1
  1. Push Event
  • Implementation Guide
    • Get Started
    • Our API Solution
    • DragonPass Modules
  • Development Guide
    • Authentication
    • Response Format
    • Error Codes
    • Order Lifecycle
    • Multiple Language Support and Fallback
    • Sandbox Order Simulation
    • UI Design Guidelines
  • Using the API
    • Search for Resources
      • Search for Resources
      • Check Prebooking Resource & Option Availability
      • Pricing Query
      • Image Parameters
    • E-pass
      • Issuing, Querying, and Cancelling an E-pass
      • Querying E-pass Usage Orders and Details
      • Utilizing The E-pass
        • Lounge
        • Fast Track
        • Dining
        • Cross Module
        • Fitness
        • eSIM
    • Membership
      • Manage Memberships & Entitlements
      • Querying Membership Usage Orders and Details
      • Utilizing DragonPass Membership
        • Lounge
        • Fast Track
        • Dining
        • Fitness
        • eSIM
    • User
      • User Management
  • Push Event
    • Lounge/Dining Walk-in Redemption Event
    • Prebooking Order Status Change Event
    • Instructions
    • Resource Update Push Service
  • Release Notes
    • 2025
    • 2026
  • Migration Guide
    • From V1 to V2
  • API Reference
    • Authentication
      • Generate Access Token
    • Search
      • Aggregated Search by Keyword
      • Retrieve Available Modules by Location
    • Transport Hubs
      • Retrieve Transport Hub
      • Retrieve Transport Hub Details
    • Resources
      • Resource List
        • Retrieve Resources List
      • Resource Details
        • Retrieve Resource Details
      • Check Resource Availability
        • Check Prebooking Resource Availability
        • Check Prebooking Option Availability
      • Fitness
        • Retrieve Fitness Resource Option Details
        • Retrieve Fitness Resources Schedule
      • eSIM
        • Retrieve eSIM Resource Option Details
        • Retrieve eSIM Resouces Options
      • Pricing
        • Retrieve Resource Pricing Information
        • Retrieve Prebooking Option Pricing Information
    • User Management
      • User Creation
      • Update User Information
      • Delete A User
      • Retrieve User Information
      • Retrieve User Memberships List
      • Retrieve User E-passes List
    • E-pass
      • E-pass Management
        • Create E-pass Order
        • Retrieve E-pass Details
        • Cancel an E-pass
      • Orders & Usage
        • Create Orders
          • Lounge Prebooking
            • Create E-pass Prebooking Order - Lounge
            • Create E-pass with Prebooking Order - Lounge
          • Fast Track
            • Create E-pass Prebooking Order - Fast Track
            • Create E-pass with Prebooking Order - Fast Track
          • Fitness
            • Create E-pass Prebooking Order - Fitness
            • Create E-pass with Prebooking Order - Fitness
          • eSIM
            • Create E-pass Prebooking Order - eSIM
            • Top up eSIM data package - E-pass
            • Create E-pass with Prebooking Order - eSIM
        • Retrieve Order List
          • Retrieve E-pass Order List
        • Cancel Orders
          • Cancel an Order
        • Module Specific APIs
          • Fitness
            • Fitness Order Check-In
          • eSIM
            • Retrieve eSIM Data Packages
            • Check eSIM Top-up Availability
            • Retrieve eSIM Order Live Extended Details
        • Usage Details
          • Retrieve E-pass Usage Order Details
    • Membership & Entitlement
      • Membership Lifecycle
        • Membership Registration
        • Update A Membership
        • Retrieve Membership Information
        • Generate Membership Dynamic QR Codes
      • Entitlement Management
        • Update Membership Entitlements
        • Retrieve Membership Entitlement Information
      • Orders & Usage
        • Preview Orders
          • Preview Membership Prebooking Order
        • Create Orders
          • Create Membership Prebooking Order - Lounge
          • Create Membership Prebooking Order - Fast Track
          • Create Membership Prebooking Order - Fitness
          • Create Membership Prebooking Order - eSIM
          • Top up eSIM data package - Membership
        • Cancel Orders
          • Cancel an Order
        • Retrieve Order List
          • Retrieve Membership Order List
        • Usage Details
          • Retrieve Membership Usage Order Details
        • Module Specific APIs
          • Fitness
            • Fitness Order Check-In
          • eSIM
            • Retrieve eSIM Order Live Extended Details
            • Check eSIM Top-up Availability
            • Retrieve eSIM Data Packages
    • Push Event Recovery
      • Push Event Recovery
    • [Sandbox Only] Simulation
      • Lounge
        • Simulate Lounge Redemption - Walk in
        • Simulate Lounge Redemption - Prebooking
        • Simulate Lounge Order Cancellation
      • Fast Track
        • Simulate Fast Track Redemption - Prebooking
        • Simulate Fast Track Order Cancellation
  • Our Team
Homepage
Official SiteContact Us
Homepage
Official SiteContact Us
API Version
v2
  • v2
  • v1
v2
  • v2
  • v1
  1. Push Event

Resource Update Push Service

Overview#

To help clients stay in sync with the latest resource data, we provide a Resource Update Push Service.
This service bundles the following three event topics into a single push subscription. Once the service is enabled, all three event topics will be delivered automatically; they cannot be enabled or disabled individually.
Supported Event Topics
resource.metadata.updated
transportHub.metadata.updated
resource.availability.changed

resource.metadata.updated#

This event notifies clients when resource metadata is updated, allowing real-time synchronization of the latest resource details.
Triggered when metadata of available resources under a specific program is updated.

Delivery Rules#

Resources are returned by module.
Each batch may contain multiple push messages.
Each push message includes up to 100 resources.
Only one module is included per push message.

Message Example#

{
  "eventType": "resource.metadata.updated",
  "batchId": "20251028T010000Z",
  "sequence": 1,
  "totalSequence": 3,
  "updatedAt": "2024-12-31T00:00:00+00:00",
  "programId": "123321",
  "module": 1,
  "resources": [
    "N00003",
    "N00004"
  ]
}

Field Descriptions#

ColumnDescriptionExample
eventTypeSpecifies the type of push event. Used to distinguish between different kinds of notifications, e.g., walkin.redemption, prebooking.statusChanged.resource.metadata.updated
batchIdUnique identifier of the callback batch used for recovery or synchronization.20251028T010000Z
sequenceCurrent sequence number within the batch, starting from 1.1
totalSequenceTotal number of sequences in this batch, used to ensure complete data retrieval.3
updatedAtTimestamp when the resource data was last updated.2024-12-31T00:00:00+00:00
programIdUnique identifier of the program. Assigned by DragonPass when a new program was onboarded.1888000000000001
moduleSpecifies the module associated with the order(s), e.g. "Lounge", "Fast Track".1
resourcesList of resource IDs that were updated in this batch.["N00001","N00002"]

Response#

A push notification is considered successfully received only when the client responds with HTTP 200 OK and returns the following JSON payload, echoing back the corresponding batchId and sequence values:
{
  "batchId": "20251028T010000Z",
  "sequence": 1,
  "status": "success"
}

transportHub.metadata.updated#

This event notifies clients when transport hub metadata is updated, enabling real-time synchronization of the latest transport hub details.
Triggered when metadata of transport hubs associated with available resources under a specific program is updated.

Delivery Rules#

Each batch may contain multiple push messages.
Each push message includes up to 100 transport hubs.

Message Example#

{
  "eventType": "transportHub.metadata.updated",
  "batchId": "20251028T010000Z",
  "sequence": 1,
  "totalSequence": 3,
  "updatedAt": "2024-12-31T00:00:00+00:00",
  "programId": "123321",
  "transportHubs": [
    "A00003",
    "A00004"
  ]
}

Field Descriptions#

ColumnDescriptionExample
eventTypeSpecifies the type of push event. Used to distinguish between different kinds of notifications, e.g., walkin.redemption, prebooking.statusChanged.transportHub.metadata.updated
batchIdUnique identifier of the callback batch used for recovery or synchronization.20251028T010000Z
sequenceCurrent sequence number within the batch, starting from 1.1
totalSequenceTotal number of sequences in this batch, used to ensure complete data retrieval.3
updatedAtTimestamp when the resource data was last updated.2024-12-31T00:00:00+00:00
programIdUnique identifier of the program. Assigned by DragonPass when a new program was onboarded.1888000000000001
transportHubsList of transport hub IDs that were updated in this batch.["A00001","A00002"]

Response#

A push notification is considered successfully received only when the client responds with HTTP 200 OK and returns the following JSON payload, echoing back the corresponding batchId and sequence values:
{
  "batchId": "20251028T010000Z",
  "sequence": 1,
  "status": "success"
}

resource.availability.changed#

This event notifies clients when the availability of resources changes, allowing them to keep an up-to-date view of which resources are currently usable.
Triggered when changes in resource availability are detected, including resources being added to or removed from the available list.

Delivery Rules#

Resources are returned by module.
Only one module is included per push message.
Each push message may include up to:
50 added resources
50 removed resources

Message Example#

{
  "eventType": "resource.availability.changed",
  "batchId": "20251028T010000Z",
  "sequence": 1,
  "totalSequence": 3,
  "updatedAt": "2024-12-31T00:00:00+00:00",
  "programId": "123321",
  "module": 1,
  "data": [
    {
      "changeAction": "added",
      "resources": [
        "N00003",
        "N00004"
      ]
    },
    {
      "changeAction": "removed",
      "resources": [
        "N00001",
        "N00002"
      ]
    }
  ]
}

Field Descriptions#

ColumnDescriptionExample
eventTypeSpecifies the type of push event. Used to distinguish between different kinds of notifications, e.g., walkin.redemption, prebooking.statusChanged.resource.availability.changed
batchIdUnique identifier of the callback batch used for recovery or synchronization.20251028T010000Z
sequenceCurrent sequence number within the batch, starting from 1.1
totalSequenceTotal number of sequences in this batch, used to ensure complete data retrieval.3
updatedAtTimestamp when the resource data was last updated.2024-12-31T00:00:00+00:00
programIdUnique identifier of the program. Assigned by DragonPass when a new program was onboarded.1888000000000001
moduleSpecifies the module associated with the order(s), e.g. "Lounge", "Fast Track".1
dataList of resource availability changes grouped by change action.
changeActionType of availability change applied to the resources. Possible values: added, removed.added
resourcesList of resource IDs affected by the corresponding change action.["N00003", "N00004"]

Response#

A push notification is considered successfully received only when the client responds with HTTP 200 OK and returns the following JSON payload, echoing back the corresponding batchId and sequence values:
{
  "batchId": "20251028T010000Z",
  "sequence": 1,
  "status": "success"
}

Event Recovery API#

To improve delivery reliability, a Recovery API is provided for the following event types:
resource.metadata.updated
transportHub.metadata.updated
resource.availability.changed is not recoverable via this API.
Typical Use Cases:
Callback endpoint timeout or failure
Temporary network interruption
Manual reconciliation or data verification

Endpoint#

→ /v2/event this API allows clients to re-fetch historical push events in case of delivery failures, network issues, or missed callbacks.
The recovery API returns exactly the same payload structure as the original push event.
This ensures clients can reuse the same processing logic for both push and recovery scenarios.

Time Limitation#

Only events generated within the last 48 hours are available for recovery.
Requests outside this time window will not return any data.
Modified at 2025-12-19 08:39:04
Previous
Instructions
Next
Release Notes