API referenceCards

One card

GET
/api/b/v1/cards/{card_id}

Authorization

OAuth2PasswordBearer
AuthorizationBearer <token>

In: header

Path Parameters

card_id*Card Id
Formatuuid
admin_access_token?string|null

Response Body

application/json

application/json

curl -X GET "https://example.com/api/b/v1/cards/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",  "label": "string",  "holder_user_id": "0945901a-0f71-46d3-9812-de7afb578bb4",  "currency": "string",  "status": "string",  "last_four": "string",  "expiry": "string",  "per_transaction_minor": 0,  "daily_minor": 0,  "monthly_minor": 0,  "allowed_categories": [    "string"  ],  "blocked_categories": [    "string"  ],  "allowed_countries": [    "string"  ],  "blocked_countries": [    "string"  ],  "frozen_reason": "string",  "created_at": "2019-08-24T14:15:22Z"}

Issue POST

Request a card. It cannot spend until the provider issues it. At least one limit is required. A card with none is a standing instruction to move a business's money without a ceiling, and the absence of a decision is not the same as deciding to allow everything.

Change the limits PUT

Takes effect on the next authorisation. Deliberately not retroactive: lowering a limit below what has already been spent today refuses the next spend rather than clawing anything back. Anything else would be reversing a purchase somebody has made.