API Reference
Monta.com

Patch charge key limit caps

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

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
int64
required
Body Params
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.

int32 | null

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.

int32 | null

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.

Responses

Updated 22 days ago

Did this page help you?
Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 22 days ago

Did this page help you?