API referenceCards

Everything asked of this card

Approved and refused alike — AC1's "logs a card.declined event" is also a row here, because a decline nobody can look up is a cardholder we cannot answer.

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

Approved and refused alike — AC1's "logs a card.declined event" is also a row here, because a decline nobody can look up is a cardholder we cannot answer.

Authorization

OAuth2PasswordBearer
AuthorizationBearer <token>

In: header

Path Parameters

card_id*Card Id
Formatuuid

Query Parameters

limit?Limit
Range1 <= value <= 500
Default100
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/authorizations"
{  "authorizations": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "amount_minor": 0,      "currency": "string",      "merchant_country": "string",      "merchant": "string",      "status": "string",      "decline_reason": "string",      "settled_minor": 0,      "authorized_at": "2019-08-24T14:15:22Z",      "settled_at": "2019-08-24T14:15:22Z"    }  ]}

Off for good POST

The row stays. Its spend is part of the book.

Create a group POST

Create a reporting group and put the current business in it. A group is a lens, not a container: it holds no money, verifies nothing, and grants nobody access to anything. Each entity keeps its own KYB, tier and wallet.