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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Wise

Wise card API

Manage your customers' cards programmatically. These APIs allow you to list cards, retrieve card details, control card status, and manage spending permissions.**Key capabilities:**- List and retrieve card details for a profile- Update card status (active, frozen, blocked)- Control spending permissions (e-commerce, ATM, contactless, magnetic stripe, etc.)- Reset PIN attempt counter after incorrect PIN entries- Update card phone number for verification purposes{% admonition type="info" %}For accessing sensitive card data (PAN, CVV, PIN), see the [Sensitive Card Details API](/api-reference/card-sensitive-details). For ordering new cards, see the [Card Orders API](/api-reference/card-order). For transaction history, see the [Card Transactions API](/api-reference/card-transaction).{% /admonition %}

Documentation Provider Profile APIs.io OpenAPI GitHub

Wise card API is one of 48 APIs that Wise publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Card. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 8 operations across 7 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0.

Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.

8 operations 7 paths 3 schemas 3 GET2 PATCH1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.wise.com/v2
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 4

Wise card API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (UserToken). It accepts HTTP bearer tokens (JWT) (PersonalToken). It accepts HTTP bearer tokens (JWT) (ClientCredentialsToken). It accepts HTTP basic authentication (BasicAuth).

  • UserToken — User Access Token for making API calls on behalf of a Wise user. Can be obtained via two OAuth 2.0 flows: - registrationcode grant: For partners creating users…
  • PersonalToken — Personal API Token for individual personal or small business users. Generated from Wise.com Settings Connect and manage apps API tokens. Has limited API access…
  • ClientCredentialsToken — Application-level token for partner operations that don't require a specific user context, such as bulk settlement and card spend controls. Obtained via POST /…
  • BasicAuth — Basic Authentication using your Client ID and Client Secret as the username and password. Client credentials are provided by Wise when your partnership begins.…

Paths & Operations 8

Across 7 paths, the API surfaces 8 operations — 3 GET, 2 PATCH, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

card 8

Manage your customers' cards programmatically. These APIs allow you to list cards, retrieve card details, control card status, and manage spending permissions. Key capabilities: -…

GET
/v3/spend/profiles/{profileId}/cards
List cards for a profile
cardList 4 params → 200429
GET
/v3/spend/profiles/{profileId}/cards/{cardToken}
Get card details
cardGet 3 params → 200429
PUT
/v3/spend/profiles/{profileId}/cards/{cardToken}/status
Update card status
cardStatusUpdate 3 params body → 200429
POST
/v3/spend/profiles/{profileId}/cards/{cardToken}/reset-pin-count
Reset PIN count
cardPinCountReset 3 params → 200429
GET
/v3/spend/profiles/{profileId}/cards/{cardToken}/spending-permissions
Get card spending permissions
cardPermissionsGet 3 params → 200429
PATCH
/v3/spend/profiles/{profileId}/cards/{cardToken}/spending-permissionsdeprecated
Update a single card permission
cardPermissionsUpdate 3 params body → 200429
PATCH
/v4/spend/profiles/{profileId}/cards/{cardToken}/spending-permissions
Bulk update card permissions
cardPermissionsBulkUpdate 3 params body → 200429
PUT
/v3/spend/profiles/{profileId}/cards/{cardToken}/phone-numberdeprecated
Update phone number
cardPhoneNumberUpdate 3 params body → 200429

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Card (13 properties), v2.0.0-4 (5 properties), Permission (3 properties). Each schema is shown below with its type and property counts.

Permission
object
Spending permission configuration for a card.
3 properties
v2.0.0-4
object
5 properties
Card
object
The Card resource represents a Wise card linked to a profile.
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wise-card-api-openapi.yml Raw ↑

Other APIs Wise publishes across the network.

Wise 3ds API
AE Profile APIs.io
Wise activity API
AE Profile APIs.io
Wise address API
AE Profile APIs.io
Wise balance API
AE Profile APIs.io
Wise balance-statement API
AE Profile APIs.io
Wise bank-account-details API
AE Profile APIs.io
Wise batch-group API
AE Profile APIs.io
Wise bulk-settlement API
AE Profile APIs.io
Wise card-kiosk-collection API
AE Profile APIs.io
Wise card-order API
AE Profile APIs.io
Wise card-sensitive-details API
AE Profile APIs.io
Wise card-transaction API
AE Profile APIs.io
#Card
← Back to W APIs
API Details
ID
wise:wise-card-api
Base URL
https://api.wise.com/v2
Docs
https://docs.wise.com/api-docs/api-reference/profile
Provider
Wise
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=wise-card-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/wise-card-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Wise card 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.