Billing Overview

When you sign a license agreement with Realtracs, it will specify the monetary consideration that must be paid for the license. In addition, there are metered costs for acquiring data from our API.

You can think of this like renting a car: you pay a daily rate for the right to drive the car (this is your licensing fee), and you also have to pay for the gasoline (this is your metered usage).

The purpose of our metered billing is to encourage consumers of the data to be efficient in how they replicate and pull data and to cover our costs in producing the API results and transmitting them to you. Our most efficient customers can keep their data current for less than two dollars a day.

Metered Usage

Each API request can result in one or more transactions. Transactions are categorized into four classes: A, B, C, and D, each with its own credit cost.

We also charge for data transfer, which is measured in API credits. As of Feb 2026, an API credit costs $1 USD.

Transaction Credits

Transaction Class	Number of Transactions per Credit
Class A	75,000
Class B	20,000
Class C	10,000
Class D	100

Each transaction counts toward your metered usage. The number of transactions per API credit determines how many credits your usage consumes.

Data Transfer Credits

Data Type	Amount per Credit
Structured Data (JSON)	1 GB
Media Data	10 GB

You are not charged for header payload size (only the HTTP body content).
Structured data includes JSON and XML payloads received from our api endpoints.
Many of our media downloads may redirect you to one of our CDNs. You are charged for the size of the media download that would occur if you follow the redirect, regardless of whether your client code follows the redirect or not.

Each API credit covers either 1 GB of structured data or 10 GB of media data.

How Credits Are Consumed

Most requests will result in one transaction. However, each resource expanded will result in additional transactions for the request, so a single request may generate multiple transactions.
Each transaction is assigned a class (A–D) and consumes credits according to the table above.
Data transfer consumes credits separately, using the structured/media rules above.
Your total API usage cost in credits = sum of transaction credits + sum of data transfer credits.

ℹ️ Tip: Keep an eye on your API usage in the developer portal to understand how many credits each request consumes.

Class A Transactions

Fetch of any record by Primary Key
All OData Requests against Lookup Resource
Bad Request or Rate Limited Request
Not Implemented Errors (501)
Forbidden Requests (403)
Requests for Metadata

Class B Transactions

Query any resource by Primary Key
Query any resource by ModificationTimestamp
Query Property resource by PhotosChangeTimestamp or DocumentsChangeTimestamp
Query OpenHouse By ListingKey (other criteria AND’d with the ListingKey is permitted)
Query HistoryTransactional By ListingKey (other criteria AND’d with the ListingKey is permitted)
Query Media By ListingKey (other criteria AND’d with the ListingKey is permitted)
Expand of OpenHouses recordsfrom the Property Resource
Expand of Media records from the Property Resource
Expand of HistoryTransactional records from the Property Resource

Class C Transactions

All other OData $filter requests

Class D Transactions

Any request for a count of records

Requests incurring data transfer fees only

Media download requests

Free Transactions

Service Document Request
All Server side errors (500 series), except 501
Unauthenticated requests (401)
Requests denied for billing purposes (402)

Note, there is no extra transaction incurred for expansion of PropertyRooms or PropertyUnits on the Property resource