Answers whether more cards can be issued to the given cardholder on the given BIN. A cardholder may hold a limited number of live cards at a time, so the caller must pin a specific `cardholderId`. Ask about a bulk issue with `cards`; the answer covers that many at once. Read `canIssue`. `true` means the cardholder has room for the cards asked about — subject to the usual checks at issue time (funds, KYC, whether the BIN is enabled for you), which this endpoint does not speak for. `false` means it has not: close a live card to free a slot, or register another cardholder. This endpoint used to also report `hasLimit`, `used`, `max` and `remaining`. Those are gone: they described an internal limit that is ours to set and to move, and no caller could act on it.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
bin |
path | string |
yes | BIN code (e.g. `5449`, `4938`). |
cardholderId |
query | string (uuid) |
yes | Cardholder UUID, as returned when the cardholder was created. It must be registered for this BIN — otherwise the request is rejected. |
cards |
query | integer (int64) |
no | How many cards you intend to issue at once. `canIssue` answers for that many together, so a bulk request can be checked before it is sent. Defaults to 1. |
Responses
| Status | Body | Description |
|---|---|---|
200 |
BinCapacityResponse |
Capacity retrieved. |
400 |
Error |
Cardholder belongs to a different BIN's cardTypeId. |
404 |
Error |
BIN or cardholder not found. |
Specification
This page is generated from the OpenAPI specification, which remains the authoritative machine-readable source.