This article lists the quotas and limits that apply to Crassula.
We impose quotas and limits on different requests in order to safeguard the system from an excess of data it cannot process and to maintain a fair allocation of system resources. The limits and quotas are subject to change.
The number of registrations per hour
Quota on the number of registrations per hour from a single IP and the total number of registrations per hour:
In case of exceeding the quota, the API returns an error with code
Quota for SMS messages based on phone number, IP address, and client ID:
This quota enhances security to prevent unauthorized use of number generation on the same IP or client profile.
Other quotas and limits
To see the limit set for a particular card, navigate to Admin panel>Card Issuing>Issued cards, click the card from the list, and open the Limits tab.
For information on issued cards, see Card Issuing:
Transfers and transactions
For information on limits applied to transfers and transactions, see Limits.
Limits configured by the
The default value is
Other eCommerce limits:
client_limit_allowed_currencies: [ EUR ]
transaction: '180 days'
withdrawal: '30 days'
/reports/transactions endpoints the parameter is configured as follows:
The Huntli functionality involves passing the limit value, which is either provided by the client or set as the default value:
API error codes
Below are the API error codes that apply to limits in Crassula: