You can set limits at the Account, Account Number, or Card level. Limits applied to Accounts will apply to all Account Numbers and Cards in the Account. You can specify any number of Limits and they will all be applied to inbound debits and card authorizations. Volume and count Limits are designed to prevent unauthorized debits.
The ISO 8601 date and time at which the limit was created.
The Limit identifier.
The idempotency key you chose for this object. This value is unique across Increase and is used to ensure that a request is only processed once. Learn more about idempotency.
The interval for the metric. This is required if metric is count or volume.
The metric for the Limit.
The identifier of the Account Number, Account, or Card the Limit applies to.
The type of the model you wish to associate the Limit with.
The current status of the Limit.
A constant representing the object’s type. For this resource it will always be limit.
The value to evaluate the Limit against.
The model to retrieve limits for.
The status to retrieve limits for.
Filter records to the one with the specified idempotency_key you chose for that object. This value is unique across Increase and is used to ensure that a request is only processed once. Learn more about idempotency.
The interval for the metric. Required if metric is count or volume.
transactionThe metric for the limit.
The identifier of the Account or Account Number you wish to associate the limit with.
The value to test the limit against.
The identifier of the Limit to retrieve.
The limit to update.
The status to update the limit with.