How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bridge Cards API

The Cards API from Bridge — 18 operation(s) for cards.

Bridge Cards API is one of 24 APIs that Bridge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cards. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 21 operations across 18 paths, and defines 37 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://api.bridge.xyz/v0.

21 operations 18 paths 37 schemas 10 GET10 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.bridge.xyz/v0
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Bridge Cards API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Key (ApiKey). By default, every request must be authenticated.

Paths & Operations 21

Across 18 paths, the API surfaces 21 operations — 10 GET, 10 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Cards 21
POST
/customers/{customerID}/card_accounts/{cardAccountID}/pin
Create Card PIN Update URL
3 params → 200401400500
POST
/customers/{customerID}/card_accounts/{cardAccountID}/ephemeral_keys
Generate an Ephemeral Key to Reveal Card Details
3 params body → 200401400500
GET
/developer/cards/summary
Get a summary of your card program
2 params → 200401400500
GET
/developer/cards/designs
Get a listing of your card program's card designs
→ 200401400500
GET
/customers/{customerID}/card_accounts/{cardAccountID}
Retrieve a card account
2 params → 200401500
PUT
/customers/{customerID}/card_accounts/{cardAccountID}
Update a card account
2 params body → 200401400500
GET
/customers/{customerID}/card_accounts
Get all card accounts
1 param → 200401500
POST
/customers/{customerID}/card_accountsdeprecated
Provision a card account
2 params body → 201401400500
POST
/customers/{customerID}/card_accounts/{cardAccountID}/freeze
Place a freeze on the card account
3 params body → 200401400500
POST
/customers/{customerID}/card_accounts/{cardAccountID}/unfreeze
Unfreeze the card account
3 params body → 200401400500
POST
/customers/{customerID}/card_accounts/{cardAccountID}/create_mobile_wallet_provisioning_request
Create a mobile wallet push provisioning request
3 params body → 200401400500
GET
/customers/{customerID}/card_accounts/{cardAccountID}/authorizations
Retrieve pending card authorizations
6 params → 200401500
GET
/customers/{customerID}/card_accounts/{cardAccountID}/transactions
Retrieve card transactions
10 params → 200401500
GET
/customers/{customerID}/card_accounts/{cardAccountID}/transactions/{transactionID}
Retrieve a card transaction
3 params → 200401500
GET
/customers/{customerID}/card_accounts/{cardAccountID}/auth_controls
Retrieve authorization controls
2 params → 200401500
POST
/customers/{customerID}/card_accounts/{cardAccountID}/deposit_addresses
Provision an additional top-up deposit address for the card account
3 params body → 200401400500
POST
/customers/{customerID}/card_accounts/{cardAccountID}/withdrawals
Create a funds withdrawal request
3 params body → 201401400500
GET
/customers/{customerID}/card_accounts/{cardAccountID}/withdrawals
Retrieve the withdrawal history of funds
5 params → 200401500
GET
/customers/{customerID}/card_accounts/{cardAccountID}/withdrawals/{cardWithdrawalID}
Retrieve a card withdrawal
3 params → 200401500
POST
/customers/{customerID}/card_accounts/{cardAccountID}/statements/{period}.pdf
Generate a card account statement
3 params → 200401400500
POST
/cardholders/{cardholderID}/cards/{cardID}/statements/{period}.pdf
Generate a card statement using Stripe IDs
3 params → 200401400500

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are CardTransaction (18 properties), CardAccount (14 properties), CardAuthorization (12 properties), CardProgramSummary (10 properties). Each schema is shown below with its type and property counts.

CardPinUpdateResponse
object
Response containing a secure URL to update a card's PIN
1 property 1 required
PostCardAccountsInput
object
5 properties 2 required
PostCardAccountDepositAddressInput
object
The details of the new deposit address to be provisioned.
1 property 1 required
CardAccount
object
14 properties 5 required
CardsCryptoCurrency
string
CardBalances
object
Balances of the card account
2 properties 2 required
GasFee
object
The gas fee for a crypto transaction
2 properties 2 required
CardAccountFundingInstructions
object
Funding instructions applicable only to the top-up card funding strategy, which is configured at the developer level
4 properties 3 required
CardCryptoAccount
object
The crypto account for a self-custodial card account. This field is not supported for a Bridge-custodial card funding setup (note that if you are on cards tria…
2 properties 2 required
CardLocalTransactionDetails
object
Details of a transaction processed in a local currency other than USD, with currency conversion applied
3 properties 3 required
CardBalance
object
2 properties 2 required
FiatCurrency
string
CardAccountEphemeralKeyResponse
object
A response containing the ephemeral key to reveal card details
1 property 1 required
Id
string
A UUID that uniquely identifies a resource
CardCryptoTransactionDetails
object
Details of the underlying crypto transaction for crypto funding, withdrawal, or return transactions
5 properties
CardPushProvisioningResponse
object
The mobile wallet push provisioning response
3 properties 5 required
OfframpChainForCards
string
PostCardUnfreezeInput
object
1 property 1 required
CardSpendingLimit
object
A spending limit for a card account
6 properties 3 required
CardProgramSummary
object
The summary of a card program for a given period
10 properties
PostCardFreezeInput
object
5 properties 2 required
PostCardPushProvisioningInput
object
3 properties 1 required
CardDesigns
object
A listing of the designs that you can use to issue a card with.
2 properties
CardFreezeInitiator
string
The party that initiated the freeze. A freeze can be initiated by either the customer or developer. Only one freeze per initiator can be active at a time. If a…
Error
object
3 properties 2 required
CardAuthorizationVerificationData
object
Information on verifications that were performed on information that the cardholder provided to the merchant.
5 properties
CardUnfreezeResponse
Card unfreeze response
5 required
CardTransaction
object
A posted transaction
18 properties 6 required
CardAuthorization
object
A pending card authorization
12 properties 7 required
CardholderName
object
The name of the cardholder associated to the card. By default, this will be the name of the associated customer. To override the cardholder name, you can conta…
3 properties 2 required
PostCardAccountEphemeralKeyInput
object
The request to create an ephemeral key to reveal card details
1 property 1 required
CardWalletProvider
string
The mobile wallet provider
CardWithdrawal
object
A card funds withdrawal
10 properties 8 required
CardFreeze
object
Card freeze
7 properties 5 required
CardFreezeReason
string
The reason of the freeze
CardWithdrawalDestination
object
5 properties 2 required
CardDetails
object
Details of the issued card. This object contains enough payment card details to identify the issued card, but only provides the last four digits of the card nu…
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bridge-cards-api-openapi.yml Raw ↑

Other APIs Bridge publishes across the network.

Bridge API Keys API
Bridge Associated Persons API
Bridge Batch Settlements API
Bridge Bridge Wallets API
Bridge Crypto Return Policies API
Bridge Customers API
Bridge Developers API
Bridge Exchange Rates API
Bridge External Accounts API
Bridge Fiat Payout Configuration API
Bridge Funds Requests API
Bridge KYC Links API
Where this information came from

This is an independent, third-party profile of Bridge Cards API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.