List all Cards

GET

issuing

card

Headers

api-key

string

required

API key is required to call Solid APIs. You can view and manage your API keys in the Solid dashboard.

Query Parameters

sub_account_id

string

unique id of the sub account

card_holder_id

string

unique id of the card holder

limit

number

number of records to return

starting_after

string

A cursor for use in pagination. starting_after is an ID that defines your place in the list. For instance, if you make a list request and receive 50 records, ending with Y2xpXzAxOGY4NjEzMDEyYjdlNTFiOTZjNmVlYWJiNmRiZTky, your subsequent call can include starting_after=Y2xpXzAxOGY4NjEzMDEyYjdlNTFiOTZjNmVlYWJiNmRiZTky in order to fetch the next page of the list.

ending_before

string

A cursor for use in pagination. ending_before is an ID that defines your place in the list. For instance, if you make a list request and receive 50 records, starting with Y2xpXzAxOGY4NjEzMDEyYjdlNTFiOTZjNmVlYWJiNmRiZTky, your subsequent call can include ending_before= Y2xpXzAxOGY4NjEzMDEyYjdlNTFiOTZjNmVlYWJiNmRiZTky in order to fetch the previous page of the list.

Response

200 - application/json

total

number

total number of records

data

object[]

data.id

string

unique id of the card

data.client_id

string

unique id of the client that created the card

data.master_account_holder_id

string

unique id of the master account holder

data.master_account_id

string

unique id of the master account

data.sub_account_holder_id

string

unique id of the sub account holder

data.sub_account_id

string

unique id of the sub account under which the card was created

data.cardholder_id

string

unique id of the card holder

data.label

string

label of the card

data.product

enum<string>

type of card product configured based on the client's use case

Available options:

business_spend,

consumer_debit,

business_debit,

consumer_gpr,

consumer_gpnr,

consumer_payroll,

consumer_hsa,

consumer_fsa,

consumer_govt_benefits

data.theme

string

theme of the card configured as part of the client use case

data.type

enum<string>

type of card

Available options:

physical,

virtual

data.expiry_month

string

expiration month of the card

data.expiry_year

string

expiration year of the card

data.last4

string

last 4 digits of the card number

data.card_fulfilment

object

data.controls

object

data.external_reference_id

string

unique id to cross-reference records with external systems

data.attachments

object[]

data.metadata

object

Metadata takes free-form key-value pairs. You may send metadata when you create an object (POST) and when updating the object (PATCH). If you would like to remove metadata that is already on an object, you can unset it by passing in the key-value pair with an empty string, like this: {"key": ""}

data.status

enum<string>

status of the card

Available options:

open,

closed,

blocked,

locked

data.timestamps

object

has_more

enum<string>

if there are more records to iterate or not

Available options:

true,

false

starting_after

string

ending_before

string

Update a Card Holder Create a Card

Getting Started

Master Accounts

Sub Account Holders

Sub Accounts

Counterparties

Card Holders

Cards

Transactions

Attachments

Webhooks

Simulation

List all Cards

Headers

Query Parameters

Response