Subscriptions Collection

API methods to work with Subscriptions

DEPRECATED

This API is deprecated. Please, use Webhooks API instead.

You can create Subscriptions to be notified about any changes at Property ARI or about Booking changes. You can think about Subscriptions like Push-notifications. When any changes happens at Property ARI or bookings, we send a webhook to the provided endpoint and send the changed data.

Subscription List

Retrieve a list of Subscriptions associated with users Properties.

Request:

GET https://staging.channex.io/api/v1/subscriptions

Pagination

By default, this method returns the first 10 elements. To get more details, you should use Pagination arguments. Information about count of entities and current pagination position contained at meta section at response object.

Returns

Success Method can return a Success result with 200 OK HTTP Code if operation is successful. Will contain a list of Subscription objects in the answer. Unauthorised Error Method can return a Unauthorised Error result with 401 Unauthorized HTTP Code if wrong Bearer Token provided.

Get Subscription by ID

Retrieve specific subscription associated with User by ID.

Request:

GET https://staging.channex.io/api/v1/subscriptions/:id

Returns

Success Method can return a Success result with 200 OK HTTP Code if operation is successful. Will contain a Subscription object in the answer. Unauthorised Error Method can return a Unauthorised Error result with 401 Unauthorized HTTP Code if wrong Bearer Token provided or User not have access to requested Subscription.

Not Found Error Method can return a Not Found Error result with 404 Not Found HTTP Code if Subscription with provided ID is not exists.

Create Subscription

Create a new Subscription.

Request:

POST https://staging.channex.io/api/v1/subscriptions

Query body (JSON):

{
  "subscription": {
    "property_id": "716305c4-561a-4561-a187-7f5b8aeb5920",
    "callback_url": "https://YOUR-WEBSITE.COM/api/push_message",
    "event_mask": "*",
    "request_params": {},
    "headers": {},
    "is_active": true,
    "send_data": true
  }
}

Fields

property_id [required]

String with valid UUID of Property object what you would like to associate with created Subscription.

callback_url [required]

Valid URL address. Note: This URL will be called via POST request when trigger event is happened.

event_mask [required]

Non-empty string with event mask. Note: Right now we have two events, what can trigger Subscription - ari and booking. You can specify different endpoints for different events using event_mask field or subscribe to any event by passing * as event_mask. For ari event event mask support filtering by restriction, room type id and rate plan id. In that case, event mask should looks like: event:restrictions:room_type_ids:rate_plan_ids where restrictions, room_type_ids and rate_plan_ids can contain several comma separated values. Real example to listen rate changes at Rate Plan with ID equal to 96a44e07-2158-43e4-8baa-8f6f56922ba8: ari:rate:*:96a44e07-2158-43e4-8baa-8f6f56922ba8

request_params [optional]

JSON Object with specific GET arguments for query.

headers [optional]

JSON Object with request headers. Note: If you would like use URL endpoint protected via authentication, you can define request headers at this field. Example:{"Authorization": "Basic user:password"}

is_active [optional]

Boolean value. Note: This field represent active status of Subscription. Only Subscriptions with is_active field equal to true value can receive notifications. Receive false as default value.

send_data [optional]

Boolean value. Note: This field is a flag to send payload data in push callback. If value is false we are call callback url without any information about changes. Receive false as default value.

Returns

Success Method can return a Success result with 201 Created HTTP Code if operation is successful. Will contain a Subscription object in the answer.

Unauthorised Error Method can return a Unauthorised Error result with 401 Unauthorized HTTP Code if wrong Bearer Token provided.

Validation Error Method can return a Validation Error result with 422 Unprocessable Entity HTTP Code if any validation rule is failed.

Update Subscription

Update a Subscription.

Request:

PUT https://staging.channex.io/api/v1/subscriptions/:id

Query body (JSON):

{
  "subscription": {
    "property_id": "716305c4-561a-4561-a187-7f5b8aeb5920",
    "callback_url": "https://YOUR-WEBSITE.COM/api/push_message",
    "event_mask": "ari",
    "request_params": {},
    "headers": {},
    "is_active": true,
    "send_data": true
  }
}

Fields

This method use same fields as Create Subscription method.

Returns

Success Method can return a Success result with 200 OK HTTP Code if operation is successful. Will contain a Subscription object in the answer. Unauthorised Error Method can return a Unauthorised Error result with 401 Unauthorized HTTP Code if wrong Bearer Token provided.

Not Found Error Method can return a Not Found Error result with 404 Not Found HTTP Code if Subscription with provided ID is not present at system.

Validation Error Method can return a Validation Error result with 422 Unprocessable Entity HTTP Code if any validation rule is failed.

Remove Subscription

Remove a Subscription.

Request:

DELETE https://staging.channex.io/api/v1/subscriptions/:id

Returns

Success Method can return a Success result with 200 OK HTTP Code if operation is successful. Will contain a Meta object with message in the answer.

Unauthorised Error Method can return a Unauthorised Error result with 401 Unauthorized HTTP Code if wrong Bearer Token provided.

Not Found Error Method can return a Not Found Error result with 404 Not Found HTTP Code if Subscription with provided ID is not present at system.

Test Subscription

Test a Subscription by sending test query to your endpoint.

Request:

POST https://staging.channex.io/api/v1/subscriptions/test

Query body (JSON):

{
  "subscription": {
    "property_id": "716305c4-561a-4561-a187-7f5b8aeb5920",
    "callback_url": "https://YOUR-WEBSITE.COM/api/push_message",
    "event_mask": "*",
    "request_params": {},
    "headers": {},
    "is_active": true,
    "send_data": true
  }
}

Returns

Success Method can return a Success result with 200 OK HTTP Code with body and status code of request results to your endpoint.

Subscription Message Examples

ARI Changes without payload

{
  "subscription": {
    "property_id": "PROPERTY_ID",
    "callback_url": "https://your-service.com/api/webhook",
    "event_mask": "*",
    "request_params": {},
    "headers": {},
    "is_active": true,
    "send_data": false
  }
}

ARI Changes with payload

{
  "subscription": {
    "property_id": "PROPERTY_ID",
    "callback_url": "https://your-service.com/api/webhook",
    "event_mask": "*",
    "request_params": {},
    "headers": {},
    "is_active": true,
    "send_data": true
  }
}

ARI Changes webhook will contain information about User (user_id), who trigger that changes. This information will help you to identify should you apply this changes at your side or not.

Stop Sell and Manual Stop Sell

At Channex.io we have 2 levels of Stop Sell:

  • automatic (stop_sell)

  • manual (stop_sell_manual)

Automatic Stop Sell is calculated value and have true value if specific date not have available rooms, have 0 rate or have enabled manual Stop Sell.

Manual Stop Sell is represent values installed by User.

To prevent any potential problems, if you subscribe to ARI changes and apply it to your inventory state, please, ignore stop_sell values and use only stop_sell_manual which represent values installed by User.

Booking Message

{
  "subscription": {
    "property_id": "PROPERTY_ID",
    "callback_url": "https://your-service.com/api/webhook",
    "event_mask": "*",
    "request_params": {},
    "headers": {},
    "is_active": true,
    "send_data": false
  }
}

Please, keep in mind, by security reasons, we are not provide Full Booking info if send_data is true.

Last updated