curl --request PATCH \
--url https://api.next.orenda.finance/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/limits \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"limitGroupId": "lg_123",
"cardType": "VIRTUAL"
}
'{
"success": true,
"message": "Card limit group updated successfully",
"data": {
"status": "success"
}
}Update card limit group
Moves a card to one of the program’s limit presets. Only on accounts whose cards.limits.mode is preset in capabilities; on a custom account this returns 501 not_available, and you use Update this card’s policy instead.
The fields depend on the program: send a limitGroupId (plus cardType) to move the card to an existing limit group, or a limit amount (plus type period) to set a limit directly. See the request examples below. Limit presets are configured per program; if you don’t know your group ids, contact the team.
curl --request PATCH \
--url https://api.next.orenda.finance/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/limits \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"limitGroupId": "lg_123",
"cardType": "VIRTUAL"
}
'{
"success": true,
"message": "Card limit group updated successfully",
"data": {
"status": "success"
}
}Authorizations
The user's access_token from authentication. The program and environment come from the token.
Path Parameters
The customer's id.
The account the card belongs to. A customer can have several accounts; cards are issued against one.
The card id from create / get cards.
Body
Move the card to this existing limit group. Send with cardType.
The card format, sent with limitGroupId.
VIRTUAL, PHYSICAL Set a limit amount directly. Send with type.
"1000.00"
The limit period, sent with limit.
DAY, WEEK, MONTH, YEAR, LIFETIME