Wise spend-controls API
Control which card transactions are permitted by creating rules based on merchant category code (MCC) or transaction currency.An authorisation rule dictates whether transactions should be declined or approved based on a pre-determined set of rules. A transaction can only pass if it satisfies all the applied rules.Creating a rule has no practical implication until it is [applied](/api-reference/spend-controls/spendcontrolsruleapply). Applying a rule results in the authorisation rule being evaluated against every incoming card authorisation request.Rules are scoped at the application level. Use a [client credentials token](/api-reference/oauth-token/oauthtokencreate) to call these endpoints.
Wise spend-controls API is one of 47 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 spend-controls. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes 6 operations across 5 paths, and defines 1 schema. It is described by OpenAPI 3.1.0.
Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Wise spend-controls 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 6
Across 5 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Control which card transactions are permitted by creating rules based on merchant category code (MCC) or transaction currency. An authorisation rule dictates whether transactions…
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is rule (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wise 12
Other APIs Wise publishes across the network.