Weavr Operations API
The Operations API from Weavr — 9 operation(s) for operations.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/weavr-operations-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
OpenAPI Specification
openapi: 3.2.0
info:
title: Weavr Operations API
version: v3
contact:
name: Weavr
url: https://weavr.io
x-logo:
url: https://storage.googleapis.com/weavr-cdn/weavr_logo-new.png
backgroundColor: '#FFFFFF'
altText: Weavr
description: 'Operations tagged Operations across 2 of this provider''s published API definitions: weavr-multi-backoffice-openapi-original.yml, weavr-multi-openapi-original.yml. Each path carries the servers of the definition it was published in.'
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi/backoffice
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
tags:
- name: Operations
paths:
/bulks/managed_cards/_id_/spend_rules:
patch:
tags:
- Operations
summary: Update spend rules for a managed card
operationId: bulksManagedCardSpendRulesUpdate
description: 'Submit the details to update the spend rules of Managed Cards.
The bulkId returned in the response can subsequently be used to launch the updating of Managed Card spend rules process through <Execute bulk process>. A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any other Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through <Cancel bulk process>.
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.
Each spend rules update operation in this bulk process is processed via <Managed Cards > Update a Managed Card.
'
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api_key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties:
_id_:
type: string
pattern: ^[0-9]+$
requestBody:
$ref: '#/components/schemas/UpdateCardLevelSpendRules'
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi/backoffice
/bulks/transfers:
post:
tags:
- Operations
description: 'Submit the details for the creation of a batch of Transfers.
The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.
Each individual operation in this bulk will be processed via [Create a Transfer Transaction](#tag/Transfers/operation/transferCreate).
'
summary: Create transfer transactions in bulk
operationId: bulksTransferCreate
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api_key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties: {}
requestBody:
required:
- profileId
- source
- destination
- destinationAmount
type: object
properties:
profileId:
$ref: '#/components/schemas/ProfileId'
tag:
$ref: '#/components/schemas/Tag'
source:
description: The managed account or managed card from where the funds will be transferred.
$ref: '#/components/schemas/InstrumentId'
description:
type: string
maxLength: 255
pattern: ^[a-zA-Z0-9\/\-?:().$_,'+\s#=!"%&*<>;\{@\r\n]*$
description: The description details that are included in the transaction as reference.
destination:
description: The managed account or managed card to where the funds will be transferred.
$ref: '#/components/schemas/InstrumentId'
destinationAmount:
description: The amount, in same currency as the source and destination instruments, to be transferred to the destination (exclusive of any fee amount that may be specified in the profile).
$ref: '#/components/schemas/CurrencyAmount'
scheduledTimestamp:
$ref: '#/components/schemas/ScheduledTimestamp'
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi/backoffice
/bulks/users:
post:
x-permissions:
- i:users:create
tags:
- Operations
description: "Submit the details for the creation of a batch of Authorised Users \n\nThe bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.\n\nThe status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.\n\nThe submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).\n\nThe system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations\n\nEach individual operation in this bulk will be processed via [Create a User](#tag/Setup/operation/userCreate).\n"
summary: Create users in bulk
operationId: bulksUserCreate
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api-key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties: {}
requestBody:
required:
- email
- name
- surname
type: object
properties:
name:
minLength: 1
maxLength: 50
type: string
description: The first name of the user.
surname:
minLength: 1
maxLength: 50
type: string
description: The last name of the user.
email:
$ref: '#/components/schemas/Email'
mobile:
$ref: '#/components/schemas/Mobile'
dateOfBirth:
description: Date of birth of the authorised user.
$ref: '#/components/schemas/Date'
tag:
$ref: '#/components/schemas/Tag'
countryOfResidence:
type: string
maxLength: 2
minLength: 2
pattern: ^[A-Z]+$
locale:
$ref: '#/components/schemas/UserLocale'
brand:
$ref: '#/components/schemas/Brand'
roles:
type: array
items:
$ref: '#/components/schemas/UserPredefinedRole'
description: Optional roles to assign to the user. For a full description of the permissions associated with each role, see our product documentation.
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
/bulks/users/_user_id_/invite:
post:
x-permissions:
- i:users:send_invite
tags:
- Operations
summary: Send user invites in bulk
operationId: bulksUserInviteSend
description: 'Submit the details for the creation of a batch of Authorised User invites
The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations
Each individual operation in this bulk will be processed via [Send a User Invite](#tag/Authorised-Users/operation/userInviteSend).
'
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api-key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties:
_user_id_:
$ref: '#/components/schemas/UserId'
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
/bulks/managed_cards/_id_/block:
post:
tags:
- Operations
description: 'Submit the details to block Managed Cards.
The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.
Each individual operation in this bulk will be processed via [Block a Managed Card](#tag/Managed-Cards/operation/managedCardBlock).
'
summary: Block cards in bulk
operationId: bulksManagedCardBlock
x-permissions:
- i:managed_cards:block
- i:managed_cards:block:own
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api-key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties:
_id_:
type: string
pattern: ^[0-9]+$
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
/bulks/managed_cards/_id_/unblock:
post:
tags:
- Operations
description: 'Submit the details to unblock Managed Cards.
The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.
Each individual operation in this bulk will be processed via [Unblock a Managed Card](#tag/Managed-Cards/operation/managedCardUnblock).
'
summary: Unblock cards in bulk
operationId: bulksManagedCardUnblock
x-permissions:
- i:managed_cards:unblock
- i:managed_cards:unblock:own
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api-key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties:
_id_:
type: string
pattern: ^[0-9]+$
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
/bulks/managed_cards/_id_/remove:
post:
tags:
- Operations
description: 'Submit the details to remove Managed Cards.
The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.
Each individual operation in this bulk will be processed via [Remove a Managed Card](#tag/Managed-Cards/operation/managedCardRemove).
'
summary: Remove cards in bulk
operationId: bulksManagedCardRemove
x-permissions:
- i:managed_cards:remove
parameters: []
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api-key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties:
_id_:
type: string
pattern: ^[0-9]+$
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
/bulks/sends:
post:
tags:
- Operations
description: 'Submit the details for the creation of a batch of Sends.
The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.
Each individual operation in this bulk will be processed via [Create a Send Transaction](#tag/Sends/operation/sendCreate).
'
summary: Create send transactions in bulk
operationId: bulksSendCreate
x-permissions:
- i:sends:create
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api-key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties: {}
requestBody:
$ref: '#/components/schemas/SendCreateRequest'
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
/bulks/outgoing_wire_transfers:
post:
tags:
- Operations
summary: Create an outgoing wire transfer in bulk
operationId: bulksOutgoingWireTransferCreate
x-permissions:
- i:owt:create
description: 'Submit the details for the creation of a batch of Outgoing Wire Transfers.
The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through [Execute Bulk Process](#tag/Manage/operation/bulkIdExecute). A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.
The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.
The submission of data for a bulk process does not expire but it can be cancelled through [Cancel Bulk Process](#tag/Manage/operation/bulkIdCancel).
The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.
Each individual operation in this bulk will be processed via [Create an Outgoing Wire Transaction](#tag/Outgoing-Wire-Transfers/operation/outgoingWireTransferCreate).
'
parameters:
- $ref: '#/components/parameters/idempotency-ref'
responses:
'201':
description: Success - returning bulk process
content:
application/json:
schema:
type: object
properties:
bulkId:
type: string
operationCount:
type: integer
path:
type: string
security:
- auth_token: []
api-key: []
requestBody:
content:
application/json:
schema:
type: array
items:
type: object
properties:
pathParams:
type: object
properties: {}
requestBody:
$ref: '#/components/schemas/OutgoingWireTransferCreateRequest'
maxItems: 10000
minItems: 1
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi
components:
schemas:
CurrencyAmount:
required:
- currency
- amount
type: object
properties:
currency:
$ref: '#/components/schemas/Currency'
amount:
type: integer
format: int64
description: 'The monetary amount, scaled to the lowest denomination of the currency.
Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.
'
description: The object representing a monetary amount in a particular currency.
Currency:
type: string
description: 'The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.'
maxLength: 3
minLength: 3
pattern: ^[A-Z]*$
CommonLevelSpendRules:
type: object
properties:
allowedMerchantCategories:
type: array
maxItems: 200
items:
type: string
description: 'Whitelist MCC: A list of allowed merchant category codes (MCCs). If the MCC does not match, then the transaction will be declined. If an MCC is also in the blocked list, the blocked list will take precedence.'
blockedMerchantCategories:
type: array
maxItems: 200
items:
type: string
description: 'Blacklist MCC: A list of disallowed merchant category codes (MCCs). If the MCC matches, then the transaction will be declined. If an MCC is also in the allowed list, the blocked list will take precedence.'
allowedMerchantIds:
type: array
maxItems: 200
items:
type: string
description: 'Whitelist Merchant Id: A list of allowed merchant IDs. If the Merchant Id does not match, then the transaction will be declined. If a Merchant Id is also provided in the blocked list, the blocked list will take precedence.'
blockedMerchantIds:
type: array
maxItems: 200
items:
type: string
description: 'Blacklist Merchant Id: A list of disallowed merchant IDs. If the Merchant Id matches, then the transaction will be declined. If a Merchant Id is also in the allowed list, the blocked list will take precedence.'
allowedMerchantCountries:
type: array
maxItems: 50
items:
maxLength: 2
minLength: 2
pattern: ^[A-Z]{2}$
type: string
description: 'Whitelist Merchant Country: A list of allowed merchant countries, in ISO 3166-1 alpha-2 format. If the Merchant country does not match, then the transaction will be declined. If a Merchant Country is also provided in the blocked list, the blocked list will take precedence.'
blockedMerchantCountries:
type: array
maxItems: 50
items:
maxLength: 2
minLength: 2
pattern: ^[A-Z]{2}$
type: string
description: 'Blacklist Merchant Country: A list of disallowed merchant countries, in ISO 3166-1 alpha-2 format. If the Merchant country matches, then the transaction will be declined. If a Merchant Country is also in the allowed list, the blocked list will take precedence.'
allowContactless:
type: boolean
description: Indicates if a contactless transaction is allowed on the card.
allowAtm:
type: boolean
description: Indicates if an ATM Withdrawal transaction is allowed on the card.
allowECommerce:
type: boolean
description: Indicates if an online transaction is allowed on the card.
allowCashback:
type: boolean
description: Indicates if a cashback transaction at a physical terminal is allowed on the card.
allowCreditAuthorisations:
type: boolean
description: Indicates if a the card can receive a credit transaction.
rolloverPolicy:
$ref: '#/components/schemas/RolloverPolicy'
SpendLimit:
type: object
required:
- value
- interval
properties:
startTimestamp:
description: The start timestamp of the spend limit, expressed in Epoch timestamp using millisecond precision.
type: integer
format: int64
value:
description: The spend limit, as amount and currency, (for the given interval).
$ref: '#/components/schemas/CurrencyAmount'
interval:
$ref: '#/components/schemas/SpendLimitInterval'
UpdateCardLevelSpendRules:
allOf:
- $ref: '#/components/schemas/CardLevelSpendRules'
- type: object
properties:
updateSpendLimitMethod:
$ref: '#/components/schemas/SpendLimitUpdateMethod'
CardLevelSpendRules:
allOf:
- $ref: '#/components/schemas/BaseCardLevelSpendRules'
- type: object
properties:
minTransactionAmount:
type: integer
minimum: 0
format: int64
description: The minimum transaction amount, in card currency, that is allowed. If the transaction amount is less than this value, then the transaction will be declined.
maxTransactionAmount:
type: integer
minimum: 0
format: int64
description: The maximum transaction amount, in card currency, that is allowed. If the transaction amount is greater than this value, then the transaction will be declined.
RolloverPolicy:
type: object
description: 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 merchant clears funds without authorising, resulting in the `availableToSpend` value to go into negative. Rollover is relative to a `spendLimit.interval`
required:
- rolloverNegative
properties:
rolloverNegative:
type: boolean
description: If set to true any overspend will keep rolling over and get deducted in the upcoming intervals until the `availableToSpend` is back to a positive value. Any overspend will be deducted from the `availableToSpend` at the beginning of the next interval.
SpendLimitInterval:
description: "The time period for which the `spendLimit` is valid.\n - DAILY: starting from 00:00:00 UTC of current day to 23:59:59 UTC of current day\n - WEEKLY: 00:00:00 UTC Monday of current week to following Sunday 23:59:59 UTC\n - MONTHLY: 1st of current calendar month to end of current calendar month\n - QUARTERLY: starting from beginning of current quarter where quarters are defined as follows:\n - 1 January 00:00:00 UTC to 31 March 23:59:59 UTC\n - 1 April 00:00:00 UTC to 30 Jun 23:59:59 UTC\n - 1 July 00:00:00 UTC to 30 September 23:59:59 UTC\n - 1 October 00:00:00 UTC to 31 December 23:59:59 UTC\n\n- YEARLY: 1 January 00:00:00 UTC of current calendar year to 31 December 23:59:59 UTC of current calendar year.\n- ALWAYS: This indicates that the `spendLimit` is the total amount that can be spent through the card throughout the whole lifetime of the card.\n"
type: string
enum:
- DAILY
- WEEKLY
- MONTHLY
- QUARTERLY
- YEARLY
- ALWAYS
Tag:
type: string
description: The tag field is a custom field that can be used to search and filter.
maxLength: 50
pattern: ^[a-zA-Z0-9_-]+$
InstrumentType:
type: string
enum:
- managed_cards
- managed_accounts
SpendLimitUpdateMethod:
type: string
description: "The spend limit update method to apply. Currently supported:\n - OVERWRITE: (default option if nothing selected). Overwrites the previous values for the spendLimit object i.e. sets new limits\n - INCREMENT : This will increase the existing value of the spend limit by the amount input the value field. If used in conj
# --- truncated at 32 KB (52 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/weavr/refs/heads/main/openapi/weavr-operations-api-openapi.yml