API Transaction Charges
An API (Application Programming Interface) allows another application or service to communicate with your account. Every time information is requested from or sent to your account through the API, it is counted as an API transaction.
What Doesn't Count Toward API Charges
Most customers will never generate billable API transactions during normal day-to-day use of Rental Software.
The following are included with your subscription and do not generate billable API transactions:
- Using Rental Software normally
- Managing inventory and categories
- Processing reservations and orders
- Using the Rental Software WordPress plugin
- Normal communication between your website and Rental Software
These activities are part of the normal operation of your account and are already included with your plan.
What Creates Billable API Transactions
API transaction charges only apply when an API key has been created and is being used by another application, service, or custom integration.
You can manage your API keys here:
Anything communicating with Rental Software using one of the API keys shown on this page will generate API transactions.
Common examples include:
- Connecting EventHawk using an API key.
- Using Zapier automations.
- Creating your own custom software or integration.
- Connecting AI assistants or AI agents to your account.
- Any third-party software that uses your Rental Software API key.
If you created or supplied an API key to another application, that application is responsible for the API requests being made on your account.
API Transaction Pricing
- The first 500 API transactions each month are included at no additional charge.
- The next 3,000 transactions are billed at $0.01 per transaction.
- Any transactions beyond that are billed at $0.001 per transaction.
API transaction charges appear on your invoice as:
API Charges = $X.XX
If Your Transaction Counts Seem High
The software does not limit or modify the information requested by applications using your API key. Once an API key has been provided, the connected application determines what information it requests and how frequently it requests it.
Because of this, transaction counts can vary significantly depending on how a third-party application has been configured.
For example, some applications may:
- Request the same information every few minutes.
- Download large lists of records instead of requesting only new or updated data.
- Repeatedly query information that has not changed.
- Perform multiple API requests when a single request would accomplish the same task.
If you notice unexpectedly high transaction counts, we recommend reviewing the configuration of the application using your API key. Custom software, AI agents, automation platforms, and third-party integrations can often be adjusted to request only the information they actually need or to poll less frequently, reducing unnecessary API usage.
Monitoring the Transaction Counts log regularly can help identify inefficient integrations and prevent unnecessary API charges.
Viewing Your API Usage
If you would like to see exactly where your API transactions are coming from, you can review the transaction log for each API key.
Step 1 - Open the API Keys Page
Navigate to:
👉 https://rental.software/account/#/settings/api
This page displays every API key associated with your account, including both active and inactive keys.
Step 2 - Open an API Key
Click any API key to open its details page.
For the purposes of reviewing API usage, the most important section is the Transaction Counts area located on the left side of the page.
Step 3 - View Transaction Counts
Click either:
- Transaction Counts in the left navigation menu, or
- Show Transaction Counts
This expands the daily transaction log for that API key.
Understanding the Transaction Log
The transaction log groups API usage by day and shows which API endpoints were accessed.
Each entry contains:
- Date — the day the requests occurred.
- Endpoint — the type of information being requested (for example,
leads_list,
rentals_list, or
leads).
- Transaction Count — the number of API requests made to that endpoint on that day.
For example:
- YYYY-MM-DD
-
leads_list— 2,363 transactions
-
rentals_list— 96 transactions
-
leads— 57 transactions
Reviewing this log is the easiest way to identify which connected application is generating API traffic and how much activity it is creating each day.