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

The Outgoing Wire Transfer transaction is used to transfer funds from managed accounts to an external bank account.

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

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

This API exposes 10 operations across 8 paths, and defines 51 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://sandbox.weavr.io/multi, "".

10 operations 8 paths 51 schemas 3 GET1 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 3

Weavr Outgoing 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 10

Across 8 paths, the API surfaces 10 operations — 3 GET, 1 PATCH, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Outgoing Wire Transfers 10

The Outgoing Wire Transfer transaction is used to transfer funds from managed accounts to an external bank account.

POST
/outgoing_wire_transfers
Create an outgoing wire transfer
outgoingWireTransferCreate 1 param body → 200400401403409429500503
GET
/outgoing_wire_transfers
Get all outgoing wire transfer transactions
outgoingWireTransfersGet 12 params → 200400401403429500503
GET
/outgoing_wire_transfers/{id}
Get an outgoing wire transfer transaction
outgoingWireTransferGet 1 param → 200400401403404429500503
PATCH
/outgoing_wire_transfers/{id}
Update the beneficiary name of an outgoing wire transfer
outgoingWireTransferUpdateBeneficiaryName 1 param body → 200409
GET
/outgoing_wire_transfers/{id}/payment_confirmation
Get an outgoing wire transfer payment confirmation
outgoingWireTransferPaymentConfirmation 1 param → 200400401403404409429500
POST
/outgoing_wire_transfers/{id}/cancel
Cancel an outgoing wire transfer transaction
outgoingWireTransferSingleCancel 1 param body → 200400401403404409429500
POST
/outgoing_wire_transfers/{id}/confirm
Confirm an outgoing wire transfer transaction
outgoingWireTransferConfirm 1 param → 200400401403404409429500
POST
/outgoing_wire_transfers/{id}/challenges/otp/{channel}deprecated
Issue a one-time password that can be used to verify an outgoing wire transfer
outgoingWireTransferSCAChallenge 2 params → 204400401403405409429500
POST
/outgoing_wire_transfers/{id}/challenges/otp/{channel}/verifydeprecated
Verify an outgoing wire transfer using a one-time password
outgoingWireTransferSCAVerify 2 params body → 204400401403409429500503
POST
/outgoing_wire_transfers/{id}/challenges/push/{channel}deprecated
Issue a push notification that can be used to verify an outgoing wire transfer
outgoingWireTransferSCAChallengePush 2 params → 204400401403405409429500

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are LegacyOutgoingWireTransfer (20 properties), OutgoingWireTransfer (18 properties), Destination (11 properties), FasterPaymentsBeneficiary (11 properties). Each schema is shown below with its type and property counts.

OutgoingWireTransferCreateRequest
object
8 properties 4 required
Nationality
string
Nationality of the user - using ISO 3166 alpha-2.
OutgoingWireTransferUpdateBeneficiaryNameConflictSchemaErrorCode
string
Tag
string
The tag field is a custom field that can be used to search and filter.
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
OutgoingWireTransfer
object
18 properties 6 required
OutgoingWireTransferRejectedInfo
string
Additional info when the outgoing wire transfer has been rejected, as follows: - SYSTEM: The wire transfer was rejected by the system. - USER: The wire transfe…
OutgoingWireTransferState
string
The state of the Outgoing wire transfer transaction, as follows: - INVALID: The wire transfer has failed initial validation checks. - PENDINGCHALLENGE: The wir…
ExecutionTimestamp
string
The epoch timestamp at which the transaction was executed, transitioning to a final state such as COMPLETED, REJECTED, or FAILED.
IBANDetails
object
Bank details used in case the wire transfer is executed over SEPA or RIX
2 properties 1 required
SCAOtpChannel
string
- "SMS": The one-time-password is sent as a text message
Nonce
string
A randomly generated one-time use code.
SEPAVerificationOfPayeeResult
object
2 properties 1 required
TransactionSingleCancelRequest
object
1 property
Error
object
2 properties
OutgoingWireTransferUpdateBeneficiaryNameRequest
object
2 properties
FasterPaymentsBeneficiary
object
Beneficiary details for Faster Payments wire transfers.
11 properties 4 required
OutgoingWireTransferValidationOutcome
object
2 properties 2 required
TransactionCancellationReason
string
The reason the scheduled transaction was cancelled.
SEPABeneficiary
object
Beneficiary details for SEPA/IBAN wire transfers.
9 properties 2 required
OutgoingWireTransferPaymentConfirmationConflict
object
1 property 1 required
BeneficiaryId
object
1 property 1 required
OutgoingWireTransferBeneficiary
object
Details of the beneficiary of the outgoing wire transfer. Deprecated: Use SEPABeneficiary for SEPA/IBAN transfers or FasterPaymentsBeneficiary for Faster Payme…
9 properties 2 required
Id
string
OutgoingWireTransferUpdateBeneficiaryNameConflict
object
1 property
ChallengeExemptionReason
string
The Reason the transaction was exempted from SCA verification
UKConfirmationOfPayeeResult
object
3 properties 1 required
Currency
string
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
DateOfBirth
string
The date of birth in ISO 8601 format (YYYY-MM-DD).
OutgoingWireTransferPaymentConfirmationConflictErrorCode
string
ExternalAccountId
object
The id of an external account, such as a Linked Account, registered with the Weavr Platform.
2 properties 2 required
OutgoingWireTransferType
string
The wire transfer rails used, from SEPA, Faster Payments, SWIFT or RIX.
ScheduledTimestamp
string
The epoch timestamp at which the transaction is scheduled to be executed.
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…
FasterPaymentsBankDetailsOrBACSBankDetails
object
Bank details used in case the wire transfer is executed over Faster Payments.
3 properties 2 required
SCAPushChannel
string
- "AUTHY": The push notification is sent on the user's device using [Twilio Authy](https://www.twilio.com/authy) - "BIOMETRIC": The push notification is sent t…
SWIFTBeneficiary
object
Beneficiary details for SWIFT wire transfers.
9 properties 4 required
ExternalAccountType
string
SourceInstrumentType
string
CurrencyAmount
object
The object representing a monetary amount in a particular currency.
2 properties 2 required
RIXBeneficiary
object
Beneficiary details for RIX wire transfers.
9 properties 2 required
ChallengeExemptionReason_2
string
The Reason the transaction was exempted from SCA verification
InstrumentId
object
2 properties 2 required
StringWrappedTypeId
object
2 properties 2 required
LegacyOutgoingWireTransfer
object
20 properties 8 required
Destination
object
11 properties 1 required
InstrumentType
string
OWTConflictErrorCode
string
OutgoingWireTransferEvent
object
4 properties 4 required
OutgoingWireTransferEventType
string
LegacyCurrencyAmount
object
The object representing a monetary amount in a particular currency.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weavr-outgoing-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 Outgoing 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.