Weavr Payment runs API
A Payment run contains a list of supplier payments. A Payment run can be - created by a user with a `CREATOR` role - confirmed by a user with a `CONTROLLER` role- funded by a user with a `CONTROLLER` roleNote that the Controller user must have their mobile device enrolled to SCA. Before a payment run can be executed, it must be funded. Users with the `CONTROLLER` role must link their company's bank account(s) that are represented as Linked Accounts, which than can be used as the funding source for a payment run.Depending on the bank's constraints it may not be possible to deposit the total amount of funds required for a payment run, in which case the payment run will be automatically split into funding groups. All funding groups must be funded and executed for the payment run to be marked as completed. Note that even if the payment is created successfully, you still need to check its status in order to determine if it is `completed` or`failed`.
Weavr Payment runs API is one of 55 APIs that Weavr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payment Runs. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 10 operations across 8 paths. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against a single base URL, https://sandbox.weavr.io/payment-run.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Weavr Payment runs API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as api-key (apiKey).
It accepts HTTP bearer tokens (JWT) (authToken).
By default, every request must be authenticated.
apiKey— The API Key representing your Weavr account. You can find your API Key in your Weavr Portal in the API Credentials page.authToken— The authentication token representing the user. This will be included in the login response object.
Paths & Operations 10
Across 8 paths, the API surfaces 10 operations — 3 GET, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
A Payment run contains a list of supplier payments. A Payment run can be - created by a user with a CREATOR role - confirmed by a user with a CONTROLLER role - funded by a user wi…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Weavr 12
Other APIs Weavr publishes across the network.
This is an independent, third-party profile of Weavr Payment runs 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.