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

Weavr Spend Controls API

Manage spend rules and authorisation forwarding to approve or reject card payments in real time.

Weavr Spend Controls API is one of 54 APIs that Weavr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Spend Controls. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 1 path, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version v3.

Requests are made against a single base URL, https://sandbox.weavr.io/multi.

4 operations 1 paths 21 schemas 1 DELETE1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://api.weavr.io/multi
Authentication
API Key, HTTP Bearer, API Key
Contact
Resource Areas
1

Authentication & Security 3

Weavr Spend Controls API declares 3 security schemes for authenticating requests. An API key is passed in the header as api-key (api-key). It accepts HTTP bearer tokens (JWT) (auth_token). An API key is passed in the header as webhooks-key (webhooks_key).

  • api-key — An API key defined in your User API Client (or Delegate API Client - this feature is available only to customers enabled with delegation functionality). API Cl…
  • auth_token — The authentication token representing the user. This will be included in the login response object.
  • webhooks_key — The Webhooks key can be found in the API Credentials tab in your Portal Page.

Paths & Operations 4

Across 1 path, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Spend Controls 4

Manage spend rules and authorisation forwarding to approve or reject card payments in real time.

GET
/managed_cards/{id}/spend_rules
Get all spend rules for a managed card
managedCardSpendRulesGet 1 param → 200400401403404429500503
POST
/managed_cards/{id}/spend_rules
Create spend rules for a managed card
managedCardSpendRulesCreate 2 params body → 204400401403404409429500
PATCH
/managed_cards/{id}/spend_rules
Update spend rules for a managed card
managedCardSpendRulesUpdate 2 params body → 204400401403404409429500
DELETE
/managed_cards/{id}/spend_rules
Delete all spend rules for a managed card
managedCardSpendRulesDelete 1 param → 204400401403404429500503

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are AllLevelSpendRules (17 properties), CardAuthorisationEvent (16 properties), MerchantData (14 properties), CommonLevelSpendRules (12 properties). Each schema is shown below with its type and property counts.

IdentityLevelSpendRules
CardAuthorisationEvent
object
16 properties 9 required
CardHolderPresent
string
BaseCardLevelSpendRules
ProfileLevelSpendRules
SpendLimitUpdateMethod
string
The spend limit update method to apply. Currently supported: - OVERWRITE: (default option if nothing selected). Overwrites the previous values for the spendLim…
Currency
string
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
CardLevelSpendRules
SyntaxError
object
Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided.
1 property
AllLevelSpendRules
object
17 properties
CardAuthorisationDetailsAuthorisationType
string
UpdateCardLevelSpendRules
CurrencyAmount
object
The object representing a monetary amount in a particular currency.
2 properties 2 required
SpendLimitInterval
string
The time period for which the spendLimit is valid. - DAILY: starting from 00:00:00 UTC of current day to 23:59:59 UTC of current day - WEEKLY: 00:00:00 UTC Mon…
SpendLimit
object
3 properties 2 required
CommonLevelSpendRules
object
12 properties
RolloverPolicy
object
The rollover policy will dictate how Weavr handles any eventual overspending. This is possible if a merchant clears more funds than authorised, or when a merch…
1 property 1 required
CardAuthorisationDetailsTransactionType
string
IdentityId
object
2 properties 2 required
MerchantData
object
14 properties 3 required
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weavr-spend-controls-api-openapi.yml Raw ↑

Other APIs Weavr publishes across the network.

Weavr Access Token API
Weavr Access Tokens API
Weavr Accounts API
Weavr Additional Factors API
Weavr Authentication Factors API
Weavr Authorised Signatories API
Weavr Authorised Users API
Weavr Buyer Authorised Users API
Weavr Buyers API
Weavr Card Payments API
Weavr Cards API
Weavr Confirmation Challenges API
Where this information came from

This is an independent, third-party profile of Weavr Spend Controls 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.