Operto: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 14: | Line 14: | ||
'''Step 1. Allow API access''' | '''Step 1. Allow API access''' | ||
IMPORTANT: Do not connect the Beds24 Account to VRScheduler until STEP 2 is complete. | |||
If the Beds24 Account is connected without the correct length propKey's in place, all properties will need to be deleted from VRScheduler and reimported. | |||
*Go to {{#fas:cog}} (SETTINGS) ACCOUNT > ACCOUNT ACCESS. | *Go to {{#fas:cog}} (SETTINGS) ACCOUNT > ACCOUNT ACCESS. | ||
*Enter a | *Enter a 16 character API key into the API Key field. (You choose the APIKey. Create a random code, any combination of letters/numbers) | ||
*Set 'API Key Access' = 'allow | *Set 'API Key Access' = 'allow whitelist IP only'. | ||
* | *IP Whitelist = 34.210.109.50 52.27.242.23 52.88.133.148 54.68.231.215 | ||
*Set 'Allow Writes' = | *Set 'Allow Writes' = YES | ||
*Set Property Access = 'Owned by this account only' | *Set Property Access = 'Owned by this account only' | ||
*SAVE. | *SAVE. | ||
'''Step 2. Set your property keys ''' | '''Step 2. Set your property keys ''' | ||
| Line 31: | Line 34: | ||
*Repeat for each property you want to connect. | *Repeat for each property you want to connect. | ||
=How it works: | =How it works:= | ||
VRScheduler will import your bookings every 30 minutes. You can choose a status value to associate with a VRScheduler Task Rule so that anytime a task generated by that rule is complete, the unit status in Beds24 is updated to the associated status value. | VRScheduler will import your bookings every 30 minutes. You can choose a status value to associate with a VRScheduler Task Rule so that anytime a task generated by that rule is complete, the unit status in Beds24 is updated to the associated status value. | ||