Capabilities

GET /v1/capabilities reports which product surfaces are available on this API version. It is authenticated — send any valid key — and requires no specific scope.

Use it at startup to decide which features to expose, rather than probing endpoints and handling 501s.

Endpoint

Method	Path	Scope	Success
GET	/v1/capabilities	none beyond a valid key	200

curl https://api.nuansis.co/v1/capabilities \
  -H "Authorization: Bearer $NUANSIS_API_KEY"

{
  "data": {
    "verification": "live",
    "collections": "live",
    "reserved_accounts": "live",
    "payouts": "live",
    "balances": "live",
    "transactions": "live",
    "channels": "live",
    "recipients": "live",
    "beneficiaries": "live",
    "deposits": "live",
    "withdrawals": "live",
    "cards": "coming_soon"
  },
  "meta": { "request_id": "f6a7b8c9-d0e1-4f2a-9b3c-4d5e6f708192" }
}

Reading the map

Key	Value	Meaning
verification	live	/v1/verifications is available
collections	live	/v1/collections is available
reserved_accounts	live	/v1/reserved-accounts is available
payouts	live	/v1/transfers and /v1/withdrawals are available
balances	live	/v1/balances is available
transactions	live	/v1/transactions is available
channels	live	/v1/channels is available
recipients	live	/v1/recipients is available
beneficiaries	live	/v1/beneficiaries is available
deposits	live	/v1/deposits is available
withdrawals	live	/v1/withdrawals is available
cards	coming_soon	Card issuing is not available

live means the route exists and is wired to a provider path. It does not override per-deployment channel configuration: GET /v1/channels is the authority for whether a specific money-in channel (card, collection_va, reserved_va, open_banking) is currently usable, and currency availability comes from the wallet catalog.

Cards

There is a cards route, but only to return a clear machine-readable response:

POST /v1/cards

{
  "error": { "code": "coming_soon", "message": "Cards are coming soon" },
  "request_id": "0a1b2c3d-4e5f-4a6b-7c8d-9e0f1a2b3c4d"
}

HTTP status is 501 Not Implemented. No card is created, and no card data is stored.

Caching

The map is static for an API version. Cache it for the lifetime of your process (or a few hours) — it will not change between deploys of your integration, and calling it on every request wastes rate limit budget. Re-read it after a Nuansis API version change.