Daily Transaction Limits

The Daily Transaction Limit is a count of the total number of transactions users and share recipients on your ExaVault account can make during a 24-hour period. Those transactions may include file uploads, file downloads, making a shared folder, creating a user, and deleting files, to name a few examples.

Your Account's Transaction Limit

The Daily Transaction Limit is calculated in real-time. It is a sum of the total number of transactions made on your account over the previous twenty-four (24) hours. The number of daily transactions allowed on an account varies depending on your current subscription plan.

Account Name

Daily Transaction Limit


50,000 transactions


150,000 transactions


480,000 transactions


2,000,000 transactions

(Legacy plans may have different limits. See your Account Usage dashboard for details.)

Monitoring Account Transactions

Your account has the following tools for monitoring transaction activity:

What happens if you exceed your Daily Transaction Limit?

ExaVault accounts that conduct significantly more transactions than others can affect your ability to connect and use the normal file functions of ExaVault. The daily limit is meant to slow those accounts down so that others can use the system without interruption.

If you reach the daily transaction limit, you may encounter the following issues:

  • Error messages appear in the application or API instructing you to try the action again later.
  • S/FTP connections will queue actions until the account falls back under the daily limit.
  • Login attempts may fail.

Because the limit is calculated in real-time, most accounts will generally fall back below the daily threshold after a few minutes (pending the previous day's activity).

If you need more detail on your account's transaction usage or would like to upgrade your account, contact ExaVault support.

Troubleshooting Excessive Transactions

Our transaction limits have been set to reflect the typical activity based on the storage for your current plan and most accounts never exceed their limits. If you encounter issues, it is likely due to some kind of automated process on your account that is driving up transactions.

Use the notes below to help you identify and correct issues around high transactions:

  • Audit current account activity. By using the activity log and the account usage report, you can determine periods of high transaction volume and review activity during that time to identify actions, usernames, and/or connection types (web, API, or (S)FTP) that might be problematic.
  • Lock specific username. If there is unexpected or problematic transaction behavior from a specific username, you may consider locking the user. This will allow your total transaction count to decrease while you find a solution.
  • Remove redundant processes such as repeatedly downloading/uploading the same file(s). Check polling scripts to make sure that once files are downloaded, they are deleted or moved so that they don't get repeatedly downloaded with each script login.
  • Reduce the frequency of polling the system. Logins are expensive in terms of transaction usage. Simply reducing the frequency of automated logins can significantly reduce the number of transactions used.
  • Reduce reliance on polling. If you have the infrastructure, you can configure webhooks to send automated messages to a waiting application when particular events (especially uploads) take place on the system. This can then trigger scripted or API calls to handle those changed files. Webhook messages generated by ExaVault don't count against your transaction limit, so this uses far fewer transactions than logging in via script to check for file changes.
  • Fix broken scripts. Verify automated scripts and jobs to make sure they include a graceful exit option if things go wrong. Check for things like maximum authentication attempts or a maximum number of download failures.
  • If you are still unable to decrease transactions, contact ExaVault support for more information or consider upgrading your account for an increased limit.

Transactions Count Example

A single action can consume multiple transactions. For this reason it is very important to minimize redundant actions that might inflate your transaction count.

For instance, after entering your username/password and selecting “LOG IN”, ExaVault must load all the information associated with your account in the following 7 transactions:

1. Call to an /auth API endpoint with your credentials and to receive a token for subsequent calls

2. Call to the /users endpoint to get information about your user

3. Call /account to get your account settings

4. Call /recipients for previous share and notification recipients to later populate forms

5. Call /email-lists for email lists created to later populate forms

6. Call /resources/list to get the list of files and folders to display

7. Call /resources to get more detailed metadata on the current folder

Other Transaction Count Examples:




Selecting “My Account”


We already have your account settings from login. Some pages in “My Account” will trigger up to two calls to populate data.

Selecting “Activity Log”


Although the log loads all activity, only one call is made.

Opening a folder


We call /resources/list to get the list of files/folders to display and /resources to get more detailed metadata on the current folder.

Creating a new notification

Up to 6

When creating alerts from the Notification page, the type can trigger up to six API calls.

© 2022 ExaVault LLC. All Rights Reserved. ExaVault is a registered trademark of ExaVault LLC.