Skip to main content
Card endpoints live under /developer/company. Every request needs Authorization: Bearer <access_token> and X-On-Behalf-Of: <company_id> — see Authentication. Reading cards needs no specific permission beyond company membership. Freezing and unfreezing require the manage_cards permission, which owners, admins, and employees hold by default.

Endpoints

Use the v2 paths for reads. The older GET /developer/company/card list is also reachable but returns a different shape and is not documented here.

List cards

Response (truncated):
Cards are returned newest first. Terminated cards are excluded unless you pass includeTerminated=true or ask for them in status.

Filters and paging

Invalid values return 400 with { "error": "<field>: <message>" }.

Get a card

Returns the same card object as a list item, without the data wrapper. Unknown or other-company cards return 404 with { "error": "Card not found" }.

Card status

Only a frozen card can be unfrozen through the API.

Freeze a card

No request body. The response is the stored card record with status now frozen:
The action is idempotent. Freezing a card that is already frozen returns 200 with the unchanged record.

Unfreeze a card

Returns the card record with status back to active. Unfreezing a card that is already active returns 200 unchanged.

Errors

Card actions report problems in a common envelope: