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 Incoming Wire Transfers API

Incoming wire transfers received from external bank accounts to managed accounts with IBANs.

Weavr Incoming Wire Transfers API is one of 55 APIs that Weavr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incoming Wire Transfers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 49 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.

2 operations 2 paths 49 schemas 2 GET

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 Incoming Wire Transfers 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 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Incoming Wire Transfers 2

Incoming wire transfers received from external bank accounts to managed accounts with IBANs.

GET
/incoming_wire_transfers
Get all incoming wire transfers
incomingWireTransfersGet 8 params → 200400401403429500503default
GET
/incoming_wire_transfers/{id}
Get an incoming wire transfer
incomingWireTransferGet 1 param → 200400401403404429500503

Schemas 49

The contract defines 49 schemas that model the data the API accepts and returns. The most detailed are ConsumerRootUser (16 properties), IncomingWireTransfer (14 properties), Corporate (14 properties), CorporateRootUser (13 properties). Each schema is shown below with its type and property counts.

CorporateRootUser
object
13 properties 9 required
StringWrappedTypeId
object
2 properties 2 required
Brand
string
Brand identifier used to determine the set of email and SMS user notification templates. Must be alphanumeric, up to 25 characters, and contain no spaces.
Industry
string
The industry of the identity.
AccountLowBalanceThreshold
integer
Sends a low balance notification webhook when the available balance drops below this amount. Currency is inherited from the managed account.
IncomingWireTransfer
object
An incoming wire transfer received from an external bank account.
14 properties 5 required
AddressWithNoRequiredFields
object
The address, with none of the separate fields being set as required.
6 properties
Id
string
Mobile
object
2 properties 2 required
IncomingWireTransferList
object
A paginated list of incoming wire transfers.
3 properties
ScaledAmount
object
A floating point number, represented as a value and its scale. Its actual value can be obtained using the equation: value pow(10, -scale).
2 properties
CurrencyAmount
object
The object representing a monetary amount in a particular currency.
2 properties 2 required
UserLocale
string
BCP47 locale code (e.g. en, en-US). The locale determines which email and SMS user notification templates are used.
BlockedReason
string
The reason why the instrument has been blocked: - USER: The root, or an authorised user, of the identity owning the instrument has temporarily blocked the inst…
CompanyType
string
Supported company types - if company type is not listed, please contact our support team to check if the company type can be supported.
CorporateSourceOfFunds
string
The corporate's source of funds.
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
Consumer
object
11 properties 5 required
Iban
object
Bank details
2 properties 1 required
Error
object
2 properties
ManagedInstrumentBalance
object
Instruments with funds have 2 balances, the availableBalance indicating the funds that are available for transactions such as purchases, and the actualBalance…
2 properties
LinkedAccount
object
12 properties 5 required
AccountDescriptor
object
Identifier or account number which does not follow either the IBAN or Faster Payment (sort code and account number) format, such as a US bank account identifie…
1 property 1 required
Corporate
object
14 properties 7 required
Date
object
3 properties 3 required
ManagedAccount
object
9 properties 7 required
DestroyedReason
string
The reason why the instrument has been destroyed: - SYSTEM: The platform or an administrator of the platform has destroyed the instrument. - USER: The root, or…
Tag
string
The tag field is a custom field that can be used to search and filter.
Address
object
6 properties 4 required
AccountNumberAndSortCode
object
Bank details
3 properties 2 required
InstrumentState
string
The state of the instrument indicating what it can and cannot do as follows: - ACTIVE: The instrument is in an active state and can be used in transactions. -…
LegalAddress
object
The legal address of the company. This information is captured via the Due Diligence (KYB) process.
6 properties 3 required
IdentityId
object
2 properties 2 required
UnknownSenderAccount
object
2 properties
InstrumentType
string
ProfileId
string
The profile Id which a specific identity, instrument or transaction type is linked to. Profiles contain configuration and determine behavioral aspects of the n…
Email
string
E-mail Address of the user
Occupation
string
The industry of the identity.
TransactionForex
object
Foreign exchange details when the transaction involved currency conversion.
4 properties
Currency
string
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
ConsumerSourceOfFunds
string
The consumer's source of funds.
IncomingWireTransferMultiState
string
The state of an incoming wire transfer: - PENDING: The transfer has been received and is being processed. Funds have not yet been credited to the destination a…
LinkedAccountState
string
The state of the linked account: - PENDINGVERIFICATION: The Linked Account is pending the completion of the required verification steps. - ACTIVE: The Linked A…
Nationality
string
Nationality of the user - using ISO 3166 alpha-2.
ManagedInstrumentState
object
3 properties 1 required
CompanyPosition
string
The company position of the Corporate Root User.
InstrumentId
object
2 properties 2 required
AccountType
string
An account can be of two types, Personal or Business: - PERSONAL means that the account held at the external bank or PSP is registered under the ownership of a…
ConsumerRootUser
object
16 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weavr-incoming-wire-transfers-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 Incoming Wire Transfers 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.