Developers

Build on the SwiftVCC API.

Automate everything the dashboard does, issue cards, set limits, read balances and transactions, and subscribe to webhooks. Clean REST, JSON, and a single token.

Get an API key →View endpoints

curl https://api.swiftvcc.com/v1/cards \
  -H "Authorization: Bearer $SWIFTVCC_TOKEN" \
  -d design=iris \
  -d limit=500 \
  -d currency=USD

Quickstart

One token, and you’re calling the API.

Create an API key in dashboard settings, send it in the Authorization header, and you’re set. Here’s what a card-issue response looks like.

Base URL	https://api.swiftvcc.com
Authentication	Bearer token (sw_live_…)
Format	JSON request & response
Rate limit	300 requests / minute
Versioning	Pinned in the path (/v1)

Response200 OK

{
  "id": "card_8f2a1c",
  "pan": "4821 •••• •••• 7390",
  "design": "iris",
  "status": "active",
  "limit": 500.00,
  "balance": 500.00,
  "currency": "USD",
  "created": 1793160000
}

How to use it

Connected in three steps.

Keys unlock once your account has added funds and issued a card. Follow the order below.

Add funds, create a card

API keys bind to a real card account. Add funds and issue a card in the dashboard first, that unlocks key creation.

Create a key in the dashboard

Go to Settings → API and mint a Bearer token (sw_live_…). It’s shown once, so store it somewhere safe.

Send it in the header

Attach the token to the Authorization header on every request. Copy the sample above and make your first call.

Reference

Endpoints

The core endpoints for cards and balances. They all use the same token.

POST/v1/cardsIssue a virtual card

GET/v1/cardsList your cards

GET/v1/cards/{id}Retrieve a card

POST/v1/cards/{id}/freezeFreeze or unfreeze a card

DELETE/v1/cards/{id}Close a card

GET/v1/balanceGet your account balance

GET/v1/transactionsList transactions

POST/v1/webhooksRegister a webhook endpoint

Webhooks

Get events in real time.

card.createdcard.frozentransaction.authorizedtransaction.declinedcashback.earnedbalance.low

Error codes

Clear status codes.

Standard HTTP codes throughout, so a failure always tells you why.

`401`	Missing or invalid token
`402`	Insufficient balance
`404`	Resource not found
`422`	Invalid request parameters
`429`	Rate limit exceeded

Grab a key and make your first call.

One account token, and an API key is minutes away.

Get an API key →