How to use content API

This document provides an overall specification for the Dida API, which encompasses three types of APIs: Static Content Data API, PriceSearch, and BookingCreation.

The Dida API supports both JSON and XML formats, though we recommend using JSON for its ease of use and readability.

Communication is facilitated through HTTP Post, ensuring secure and reliable data transfer.

Each request should include a header that contains the ClientID and LicenseKey. For security purposes, the IP of the service server needs to be white-listed.

By default, the Queries Per Second (QPS) limit is set to 30. If the QPS quota is exceeded, requests may be rejected to prevent server overload. However, this setting is flexible. If your needs require a higher QPS, please contact us for adjustment.

To optimize data transfer, all requests should accept gzip encoding. Similarly, all response messages are returned in gzip encoding to ensure efficient and fast data delivery.

Json format header:

{
    "Header":{
        "ClientID":"DidaApiTestID",
        "LicenseKey":"TestKey"
    }
}

XML format header:

<Header>
    <ClientID>DidaApiTestID</ClientID>
    <LicenseKey>TestKey</LicenseKey>
</Header>