Set monthly amount limit

Set Monthly Amount Limit

The Set Monthly Amount Limit endpoint allows users to define a maximum total amount that can be spent from a payment card within a given calendar month. This spend rule enhances budgeting and financial management by preventing expenditures from exceeding a predefined threshold. The limit can be updated at any time, providing flexibility as financial needs change.

Endpoint

POST /api/spendRules/amountLimitMonthly

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when you need to enforce monthly expenditure caps on a payment card, such as setting budget limits for business cardholders or personal spending controls. It is particularly useful for partners building expense management features, enabling automated enforcement of monthly budgets without manual intervention. Call this endpoint whenever a cardholder or administrator wishes to establish or revise a card's monthly spending ceiling.

Request Body

FieldTypeRequiredDescription
paymentCardIdstringYesUnique identifier of the payment card to which the monthly limit will be applied. Minimum length: 1 character.
valueinteger (int32)NoThe monthly spending limit amount in cents (e.g., 50000 = $500.00). Set to 0 or omit to remove an existing limit.
{
  "paymentCardId": "card_a1b2c3d4e5f6g7h8",
  "value": 50000
}

Response

200 OK

A 200 OK response indicates the monthly amount limit spend rule was successfully created or updated for the specified payment card. The response body may be empty on success.

{}

Error Codes

CodeWhen it happens
400Missing required fields or validation error (e.g., paymentCardId is absent or empty)
401Token missing, expired, or invalid
403Insufficient permissions to apply spend rules to the specified card
404Payment card not found for the provided paymentCardId
500Internal server error

Common Mistakes

  • Omitting paymentCardId — this field is required; the request will fail with a 400 error if it is missing or an empty string.
  • Passing value as a decimal (e.g., 500.00) instead of an integer in cents (e.g., 50000) — the field is int32 and fractional values will be rejected or truncated.
  • Using an expired or invalid Bearer token — tokens have a 10-minute lifetime and must be refreshed before expiry.
  • Applying a monthly limit to a card that does not belong to the authenticated partner's customer — this will result in a 403 or 404 response.

Related Endpoints

  • POST /api/spendRules/amountLimitDaily — Set a daily spending limit for a payment card
  • POST /api/spendRules/amountLimitTransaction — Set a per-transaction spending limit for a payment card
  • GET /api/spendRules — Retrieve all active spend rules for a payment card
  • DELETE /api/spendRules/{spendRuleId} — Remove an existing spend rule from a payment card

Example

curl -X POST https://api.banking.netevia.dev/api/spendRules/amountLimitMonthly \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentCardId": "card_a1b2c3d4e5f6g7h8",
    "value": 50000
  }'
Body Params
int32
string
required
length ≥ 1
Headers
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Response
200

Success

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!