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

Memo Bank Wire Transfers API

Wire transfers are transfers going through Swift. They allow you to send funds outside the SEPA network and to transfer money in foreign currencies.Initiating a wire transfer may require you to upload a supporting document. In such case the transfer will have a `pending_attachment_required` status and you'll receive an event `wire_transfer_attachment_required` on your webhook. If no document is required but you still want to attach one to your transaction, use the [attachments](#endpoint-attachments) endpoints.

Memo Bank Wire Transfers API is one of 15 APIs that Memo Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Wire Transfers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 4 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: https://api.memo.bank, https://api.sandbox.memo.bank.

4 operations 4 paths 9 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.memo.bank
Resource Areas
1

Paths & Operations 4

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

Wire Transfers 4

Wire transfers are transfers going through Swift. They allow you to send funds outside the SEPA network and to transfer money in foreign currencies. Initiating a wire transfer may…

POST
/v2/wire_transfers
Initiate a wire transfer
createWireTransfer body → 200
POST
/v2/wire_transfers/{id}/attachments
Create an attachment to a wire transfer
createWireTransferAttachment 1 param body → 201
GET
/v2/wire_transfers/{id}/proof
Generate a proof of wire transfer
getProofOfWireTransfer 1 param → 200
GET
/v2/wire_transfers/{id}
Get a wire transfer
getWireTransfer 1 param → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are WireTransfer (14 properties), CreateWireTransfer (9 properties), TransferBeneficiary (6 properties), TransferBeneficiaryAddress (4 properties). Each schema is shown below with its type and property counts.

WireTransfer
object
14 properties 8 required
TransferBeneficiary
object
Information regarding the beneficiary of this wire transfer.
6 properties 5 required
AccountIdentifierDiscriminator
object
1 property 1 required
CreateWireTransfer
object
9 properties 6 required
IbanAndBic
object
3 required
TransferBeneficiaryAddress
object
Address of the beneficiary. Will be used to create the beneficiary if one doesn't already exist with the same accountidentifier, will be ignored otherwise.
4 properties 4 required
AccountNumberAndBic
object
3 required
AccountIdentifier
object
Account identifier of the beneficiary.
AccountNumberAndRoutingCode
object
3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

memo-bank-wire-transfers-api-openapi.yml Raw ↑

Other APIs Memo Bank publishes across the network.

Memo Bank Account assessments API
Memo Bank Accounts API
Memo Bank AIS API
Memo Bank Attachments API
Memo Bank Collections API
Memo Bank IBA Ns API
Memo Bank Mandate signature requests API
Memo Bank O Auth2 API
Memo Bank PIS API
Memo Bank Sandbox API
Memo Bank Transactions API
Memo Bank Transfers API
Where this information came from

This is an independent, third-party profile of Memo Bank 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.