Rainmaker Interface IMPLEMENTATION for Agilysys Visual One

Owned by Kel Hill
Last updated: May 18, 2018
2 min read

b4 IP addresses to white-list


To enable b4checkin products to communicate with your systems, with interfaced products,
your IT team must white-list our IP addresses on port 443 of your web server. 

1) 173.252.62.122 (testing/staging)
2) 192.175.96.6 (production)
3) 192.175.96.7 (production)
4) 174.142.199.37 (production)
5) 174.142.199.38 (production)

Europe only:

1) 52.232.73.156 (production)


Interfaced Rainmaker Products


The interface for Rainmaker by b4checkin works with Rainmaker's GuestRev and RevIntel products, but not with GroupRev or RevCaster.



Rainmaker Interface Installation Steps


As b4checkin simply provides an interface, there is no requirement to connect with the property team. The Agilysys Project Manager will field the questions from the property and liaise with b4checkin when required. Communication to the property is owned by the Agilysys Project Manager.


  1. The Agilysys Project Manager schedules a kick-off call with the property and Agilysys IT. b4checkin is not required.

    The Agilysys Project Manager must provide the b4checkin API document to the property after this call.

  2. Agilysys creates and grants SQL access to b4checkin.

    The SQL login must have read/write/execute permissions for the V1 catalog.

  3. The Agilysys PM will send the property the following items to be sent to b4checkin. The property is also able to obtain this information from their Rainmaker representative:

    1. The resort ID from Rainmaker.

    2. All known IP addresses from Rainmaker, including those in test environments. Multiples can be comma delimited to accept more than one. This is the IP of the Rainmaker system that is sending requests to the b4checkin API.

      If needed, contact Rainmaker to obtain the IP address to be white-listed by sending an email to revbisupport@letitrain.com which will create a ticket in Rainmaker's salesforce system.

    3. The Property Code

    4. The Horizon Days. This is the number of days into the future that b4checkin will provide data to Rainmaker.

    5. The domain name where the property will have b4checkin install the b4checkin API.

      Note: If the property has purchased and installed any products requiring the BN Web Service, b4checkin will already have this.

  4. b4checkin will build the API with the Rainmaker interface, and will create a username and password for the b4checkin API configuration.

  5. b4checkin will install the API with the property IT person.

    Ensure that the b4checkin Professional Services team provides the b4checkin Account Manager with the login credentials for the Rainmaker API. Log these credentials & URL in the shared Confluence page for future reference.

  6. b4checkin will update 3 stored procedures.

  7. Note: The property must create original rates for the chosen Tariff before the property can send updates from Rainmaker. Even if BAR is created, they need rates for each month before they can update that month. Derived rates will operate.

  8. b4checkin provides the API Endpoint URL, username and password to the Agilysys Project Manager, who will forward it along to the property, who will send it to their Rainmaker representative. Billing can begin.

  9. Rainmaker turns the application on.


© 2024 b4checkin