CiirusXML15025


General

Welcome to The CiiRUS API. To begin, please thoroughly review this documentation, and please be sure to contact CiiRUS, Inc to begin step one of the Steps to Success (Click Here to Contact Us Now).
API Additional Fn(x)s

Integration WorkFlow

High-level overview of how the Integration process should go:

Click to View Full Size Diagram:

Common WorkFlows

On Demand Requests & Delta Options

Click to View Full Size Diagram:

Note: This is not the only acceptable work flow for implementation, but this outlines the process for several of the most common API implementations.

Bulk Data Caching

Click to View Full Size Diagram:

Note: Bulk data caching assumes that you preform the bulk transfer of data in fewer requests between 1 and 4 times per day. The ondemand data flow can be used for updating individual units as required with respect to delta options available.

General Related Help Articles

Terminology:

Property Manager (PM), is the same as Management Company (MC).
Booking is the same as Reservation.
Property is the same as Unit. This differs slightly regarding AOA properties.
CalendarSync allows an account that distributes homes for another Property Manager to sync the calendars when a booking is placed.
AOA Property is a Property object representative of a type of unit. This AOA Property Object Instance represents a group of inventory from that type/category of inventory.Merchant of Record (MOR) - The Party that collects the funds from the Guest. In terms of this integration, is the MC/PM, Agent, or other, that is represented by a third party MOR service.
Note: ALL INPUT FIELDS MUST BE PASSED TO THE FUNCTION FOR EVERY REQUEST. - Optional Values have an optional value state that is required.
Note: - This means that this element/object is required

Steps to Success:

Please follow the following steps to Success in the order as numbered:

Note: No need to delay, get started today!

Updates:

Please check this area regularly for news about updates, additions, new versions, and bug fixes. This section is intended to help existing integrations see at a glance what has changed.

CiiRUS uses semantic version-ing to implement any breaking changes, so this should not present an issue; however, this section can also be used to determine if any future API changes coincide with any new errors.

Note: Please check back regularly. We are adding new functions and functionality through non-breaking changes almost everyday. Developers, please stay informed on CiiRUS API updates.

Obtaining API Support

CiiRUS is happy to support and stand behind its products and services, but CiiRUS does not support third party software or integrations created by third parties. If you would like to report an error, bug, or have technical questions, unless otherwise instructed, please submit your requests to CiiRUS Technical Support.

Please be sure to include:


Note: Failure to present some or all of this requested information regarding any issue(s) will result in delayed responses, and may result in a request for further information. If it cannot be replicated by a CiiRUS representative, it cannot be debugged or resolved. Please help us help you as efficiently and completely as possible.

Function Definitions

The following operations are supported. For a formal definition, please review the Service Description.