3rd Party Requests

1- Push Account Details

3rd party sends a push request to HotelRunner to inform that property wants to use HotelRunner services.

• In some cases, we redirect user to the 3rd party's endpoint to complete their eligiblity for the campaign, with 'hr_id' suffix. When property become eligible for the campaign, we expect 3rd party send an API call to our endpoint that says the property which is identified by 'hr_id' has become eligible for the campaign (campaign_code).

POST https://app.hotelrunner.com/api/v1/apps/notifications/new_account

Content-Type: application/json

Parameters (Restful):

1- property_name 2- contact_email 3- hr_id 4- campaign_code 5- eligible 6- uid

Success Response (JSON):

{ status: 'ok', campaign_link: 'https://HOTEL_CODE.hotelrunner.com/target?campaign_code' }

Fail Response:

{status: 'property_not_found', campaign_link: 'https://app.hotelrunner.com/signup?target={{ CAMPAIGN_CODE }}'}

2- Property Sign Up Link

If property doesn't have a HotelRunnner account, then please redirect him to this path:

https://app.hotelrunner.com/signup?target={{ _CAMPAIGN_CODE_ }}&tpidentifier={{ _UNIQUE_ID_ON_PARTNER }}&partner_code={{ PARTNER_CODE }}

3- Property Subscription Link

If property has a HotelRunnner account, then please redirect him to this path:

https://app.hotelrunner.com/login?target={{ _CAMPAIGN_CODE_ }}&tpidentifier={{ _UNIQUE_ID_ON_PARTNER }}&partner_code={{ PARTNER_CODE }}