How is my usage calculated?

Propexo makes requests to PMS APIs on your behalf. We do what we can to ensure that only necessary records are returned by implementing date filters on records returned during regular syncs - with only backsyncs always fetching all historical data. The date filters implemented during regular syncs have been carefully chosen to ensure the balance between reducing data volume and ensuring all relevant records are brought in.

When we get a response from a PMS API, we check each record received to ensure it is not a record to be created or updated in Propexo's endpoints. These are called "records seen" in your Propexo dashboard, and these are what are used for usage calculations.

It's also important to note that some models require multiple API calls to be fully hydrated, amongst other particularities. As a result, you shouldn't assume a 1:1 relationship between a real-world entity and a single API record or call - for example, 1 property does not necessarily equal 1 record, and 1 unit does not necessarily equal 1 record. A single property or unit may require several requests across multiple endpoints to be fully hydrated, and each of those requests can contribute to "records seen."

Strategies to reduce records seen include:

• Disabling unwanted properties

• Avoiding unnecessary backsyncing

• Turning down your sync frequency

• Using custom sync schedules

• Ensuring only necessary models are enabled