Listing Workflow

Overview

The listing object contains static information of the listing such as basic details, location, description, photos, common facilities, unit types details, check-in/check-out options, etc.

Each listing can have multiple units (e.g. 1 room apartments, 2 room apartments, etc.) and these types are referred to as unit types.

Each unit type can have a description, facilities, maximum number of guests, etc.

Integration Steps

Available Endpoints

Available Endpoints
GET	`/v1/updates/listings`
GET	`/v1/listings/{listingId}`

Step 1: Fetching the Listing Updates

Make an API call to route GET /v1/updates/listings to fetch the latest listing updates.
As this is a paginated API, you have to pass the following parameters:

Parameter	Description

Parameter	Description
`cursor`	Each response contains a `next` cursor, that you can then use to retrieve the next page of updates.
`limit`	The maximum number of listing updates returned by API. (Maximum: `50`)

If you are integrating with this API for the first time, the cursor parameter should be omitted. Every subsequent request should contain the cursor that is provided to you in the previous call’s next field. That way you can efficiently poll for listing updates that happened after the last successful pull.

Sample Request

curl -X 'GET' \
  'https://chapi.holidu.com/v1/updates/listings?cursor=asJ34sgt&limit=3' \
  -H 'Accept: application/json'
  -H 'Authorization: Bearer SIGNED_JWT'

Sample Response

{
  "updates": [
    {
      "listingId": "21e63d96-41aa-471c-af61-965f85e7a22a",
      "listingUrl": "/listings/21e63d96-41aa-471c-af61-965f85e7a22a",
      "active": true,
      "version": "9"
    },
    {
      "listingId": "706b9f81-9c3b-4c1b-8bf9-9ee4489d4b3e",
      "listingUrl": "/listings/706b9f81-9c3b-4c1b-8bf9-9ee4489d4b3e",
      "active": true,
      "version": "11"
    },
    {
      "listingId": "2409f4e5-d4c8-4fda-a1a5-b5d49677191b",
      "listingUrl": "/listings/2409f4e5-d4c8-4fda-a1a5-b5d49677191b",
      "active": true,
      "version": "12"
    }
  ],
  "next": "RyNAJRykNaJRxJSMjIwtNQD1sykxRsjK0M"
}

Parameter	Description

Parameter	Description
`listingId`	Unique id of the listing
`listingUrl`	The listing URL which can be used to fetch the listing
`active`	Boolean field. `true`- The listing is active and accepts bookings. `false` - The Listing is inactive and does not accept any future bookings
`version`	An unique identifier, specifying the update version in a global incremental series for every update. If the version is 20, this means that this is the 20^thupdate on Listing or Pricing in our inventory

Step 2: Processing the Listing Update

After successfully fetching the listing updates, the content present at the listingUrl field needs to be processed.
The listingUrl field represents the API route for fetching listing content (i.e GET /v1/listings/{listingId}).

Sample Request

curl -X 'GET' \
  'https://chapi.holidu.com/v1/listings/21e63d96-41aa-471c-af61-965f85e7a22a' \
  -H 'Accept: application/json'
  -H 'Authorization: Bearer SIGNED_JWT'

Sample Response

Sync Frequency

To have the latest details for the listings, partners should poll the listing updates regularly. The listing updates API can be polled up to the interval provided in the Rate limiting. We recommend polling it at least every minute.