Skip to main content
GET
Get card

Authorizations

Authorization
string
header
required

API key as Bearer token

Headers

Reap-Version
enum<string>
required

API version (YYYY-MM-DD)

Available options:
2025-02-14
Example:

"2025-02-14"

Path Parameters

id
string<uuid>
required

Response

Card resource with directly-attached spend policies

id
string<uuid>
required

Unique card identifier

accountId
string<uuid>
required

ID of the account the card belongs to

userId
string<uuid>
required

ID of the user the card belongs to

type
enum<string>
required

Card type (VIRTUAL or PHYSICAL)

Available options:
VIRTUAL,
PHYSICAL
Example:

"VIRTUAL"

status
enum<string>
required

Current card status

Available options:
ACTIVE,
FROZEN,
BLOCKED,
EXPIRED
Example:

"ACTIVE"

blockReason
CardBlockReason · object | null
required

Block reason details (only present when status is BLOCKED)

cardholderName
string
required

Cardholder name displayed on card

last4
string
required

Last 4 digits of the card number. Use reveal endpoint for full details.

3dsChallengeMethod
enum<string>
required

3DS challenge verification method

Available options:
SMS,
WEBHOOK
Example:

"SMS"

physicalCardStatus
enum<string> | null
required

Physical lifecycle of the card (production + shipping + activation rollup). Defaults to NOT_ORDERED for newly created physical cards. null for virtual cards, which have no physical lifecycle.

Available options:
NOT_ORDERED,
REQUESTED,
IN_PRODUCTION,
PRODUCTION_COMPLETED,
IN_TRANSIT,
OUT_FOR_DELIVERY,
DELIVERED,
ACTIVATED,
CANCELED,
DELIVERY_FAILED,
EXCEPTION
Example:

"NOT_ORDERED"

createdAt
string
required

ISO 8601 timestamp of creation

updatedAt
string
required

ISO 8601 timestamp of last update

policies
(MerchantRestriction · object | ChannelRestriction · object | TransactionAmountLimit · object | SpendLimit · object | AuthorizationCountLimit · object)[]
required

Active spend policies attached directly to this card. Only directly-attached policies are included - those attached at other scopes and platform-enforced limits are not.

Policy resource