Charge Key Limit Caps
Retrieve list of charge key limit caps
Required scope: charge-auth-tokens:read
Organization authorization: supported
An operator has one set of caps per team settings profile (Hub: Operator team settings); defaultForTeamType says which teams get the set by default. A charge key's own usage limits (rollingSpendLimit, dailyChargeCountLimit, concurrentChargesLimit) may not exceed the caps its team is bound by. A null cap is not configured, so the recommended value is the cap. Caps may not exceed max, Monta's ceiling.
Only operator-scoped consumers may read caps; a team-scoped consumer gets 403.
query Parameters
operatorIdRestrict the list to caps of this operator
pagepage number to retrieve (starts with 0)
perPagenumber of items per page (between 1 and 100, default 10)
Retrieve list of charge key limit caps › Responses
List of charge key limit caps
Retrieve charge key limit caps
Required scope: charge-auth-tokens:read
Organization authorization: supported
An operator has one set of caps per team settings profile (Hub: Operator team settings); defaultForTeamType says which teams get the set by default. A charge key's own usage limits (rollingSpendLimit, dailyChargeCountLimit, concurrentChargesLimit) may not exceed the caps its team is bound by. A null cap is not configured, so the recommended value is the cap. Caps may not exceed max, Monta's ceiling.
Only operator-scoped consumers may read caps; a team-scoped consumer gets 403.
path Parameters
chargeKeyLimitCapIdRetrieve charge key limit caps › Responses
Charge key limit caps with provided id
Monta's recommended values, used as the cap while none is configured
Monta's ceiling: the highest value each cap may be set to. null means no ceiling.
idId of this set of caps
operatorIdId of the operator these caps belong to
nameName of the team settings profile, as shown in the Hub
defaultForTeamTypeTeams of this type get these caps by default: professional, private, all, operator, default_private_team, none, or null when the caps apply only to teams assigned to the profile explicitly. Also sets which recommended and max values apply.
Cap on a charge key's rolling 30-day spend. null means no cap is configured, so recommended applies. Currently always in EUR. The write side takes a plain decimal amount in the same currency.
dailyChargeCountLimitCap on a charge key's daily charge count. null means no cap is configured, so recommended applies.
concurrentChargesLimitCap on a charge key's concurrent charges. null means no cap is configured, so recommended applies.
Patch charge key limit caps
Required scope: charge-key-limit-caps:write (not requestable by marketplace apps)
Organization authorization: supported
An operator has one set of caps per team settings profile (Hub: Operator team settings); defaultForTeamType says which teams get the set by default. A charge key's own usage limits (rollingSpendLimit, dailyChargeCountLimit, concurrentChargesLimit) may not exceed the caps its team is bound by. A null cap is not configured, so the recommended value is the cap. Caps may not exceed max, Monta's ceiling.
Raise a cap here before raising charge keys above it. Only operator-scoped consumers may change caps; a team-scoped consumer gets 403. Existing charge keys keep their limits when a cap changes.
path Parameters
chargeKeyLimitCapIdPatch charge key limit caps › Request Body
rollingSpendLimitCap on a charge key's rolling 30-day spend, as a plain decimal amount in the currency of rollingSpendLimit on read (currently always EUR). Send null to remove the cap (the recommended value then applies); omit the field to leave it unchanged. Must be strictly positive and may not exceed max.
dailyChargeCountLimitCap on a charge key's daily charge count. Send null to remove the cap; omit the field to leave it unchanged. Must be strictly positive and may not exceed max.
concurrentChargesLimitCap on a charge key's concurrent charges. Send null to remove the cap; omit the field to leave it unchanged. Must be strictly positive and may not exceed max.
Patch charge key limit caps › Responses
Charge key limit caps updated
Monta's recommended values, used as the cap while none is configured
Monta's ceiling: the highest value each cap may be set to. null means no ceiling.
idId of this set of caps
operatorIdId of the operator these caps belong to
nameName of the team settings profile, as shown in the Hub
defaultForTeamTypeTeams of this type get these caps by default: professional, private, all, operator, default_private_team, none, or null when the caps apply only to teams assigned to the profile explicitly. Also sets which recommended and max values apply.
Cap on a charge key's rolling 30-day spend. null means no cap is configured, so recommended applies. Currently always in EUR. The write side takes a plain decimal amount in the same currency.
dailyChargeCountLimitCap on a charge key's daily charge count. null means no cap is configured, so recommended applies.
concurrentChargesLimitCap on a charge key's concurrent charges. null means no cap is configured, so recommended applies.