Monta
Monta API

Charge Key Limit Caps


Retrieve list of charge key limit caps

GET
https://partner-api.monta.com
/api/v1/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.

Retrieve list of charge key limit caps › query Parameters

operatorId
​integer · int64

Restrict the list to caps of this operator

page
​integer · int32

page number to retrieve (starts with 0)

Default: 0
perPage
​integer · int32

number of items per page (between 1 and 100, default 10)

Default: 10

Retrieve list of charge key limit caps › Responses

List of charge key limit caps

​ChargeKeyLimitCap[] · required
​MontaPage.Meta · required

Retrieve charge key limit caps

GET
https://partner-api.monta.com
/api/v1/charge-key-limit-caps/{chargeKeyLimitCapId}

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.

Retrieve charge key limit caps › path Parameters

chargeKeyLimitCapId
​integer · int64 · required

Retrieve charge key limit caps › Responses

Charge key limit caps with provided id

A set of charge key usage limit caps: the highest usage limits a charge key may be given. An operator has one set per team settings profile (Hub: Operator team settings), and a charge key is bound by the set of the profile its team uses.
​object · required

Monta's recommended values, used as the cap while none is configured

​object · required

Monta's ceiling: the highest value each cap may be set to. null means no ceiling.

id
​integer · int64

Id of this set of caps

Example: 42
operatorId
​integer · int64

Id of the operator these caps belong to

Example: 1
name
​string | null

Name of the team settings profile, as shown in the Hub

Example: Fleet customers
defaultForTeamType
​string | null

Teams 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.

Example: professional
​object

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.

dailyChargeCountLimit
​integer | null · int32

Cap on a charge key's daily charge count. null means no cap is configured, so recommended applies.

Example: 20
concurrentChargesLimit
​integer | null · int32

Cap on a charge key's concurrent charges. null means no cap is configured, so recommended applies.

Example: 10

Patch charge key limit caps

PATCH
https://partner-api.monta.com
/api/v1/charge-key-limit-caps/{chargeKeyLimitCapId}

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.

Patch charge key limit caps › path Parameters

chargeKeyLimitCapId
​integer · int64 · required

Patch charge key limit caps › Request Body

rollingSpendLimit
​number | null

Cap 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.

Example: 1500
dailyChargeCountLimit
​integer | null · int32

Cap 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.

Example: 20
concurrentChargesLimit
​integer | null · int32

Cap 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.

Example: 10

Patch charge key limit caps › Responses

Charge key limit caps updated

A set of charge key usage limit caps: the highest usage limits a charge key may be given. An operator has one set per team settings profile (Hub: Operator team settings), and a charge key is bound by the set of the profile its team uses.
​object · required

Monta's recommended values, used as the cap while none is configured

​object · required

Monta's ceiling: the highest value each cap may be set to. null means no ceiling.

id
​integer · int64

Id of this set of caps

Example: 42
operatorId
​integer · int64

Id of the operator these caps belong to

Example: 1
name
​string | null

Name of the team settings profile, as shown in the Hub

Example: Fleet customers
defaultForTeamType
​string | null

Teams 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.

Example: professional
​object

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.

dailyChargeCountLimit
​integer | null · int32

Cap on a charge key's daily charge count. null means no cap is configured, so recommended applies.

Example: 20
concurrentChargesLimit
​integer | null · int32

Cap on a charge key's concurrent charges. null means no cap is configured, so recommended applies.

Example: 10