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

Lead Bank Wire API

The Wire API from Lead Bank — 4 operation(s) for wire.

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

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

This API exposes 6 operations across 4 paths, and defines 35 schemas. It is described by OpenAPI 3.0.1, at version v1.0.

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

6 operations 4 paths 35 schemas 2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1.0
Base URL
gated-partner-access
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Lead Bank Wire API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 6

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

Wire 6
GET
/v1/wires/{wire_id}
Retrieve a wire V1
retrieve-a-wire-v1 1 param → 200403404
PATCH
/v1/wires/{wire_id}
Update a wire V1
update-a-wire-v1 2 params body → 200400404422
GET
/v1/wires
List all wires V1
list-all-wires-v1 8 params → 200403422
POST
/v1/wires
Create a wire V1
create-a-wire-v1 1 param body → 200400403422
POST
/v1/wires/{wire_id}/return
Return a wire V1
return-a-wire-v1 2 params body → 200400403404422
POST
/v1/wires/{wire_id}/cancel
Cancel a wire V1
cancel-a-wire-v1 1 param → 200400404

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are WireV1 (26 properties), WirePostalAddress (17 properties), APIError (6 properties), WireOtherAgents (6 properties). Each schema is shown below with its type and property counts.

WireReturnReasonEnum
string
Reason to return a wire payment.
WireInstructAgent
object
Wire instruct agent information.
3 properties
AccountNumberID
string
The ID of the Lead Bank Account Number object.
Metadata
object
A set of key-value pairs that can be used to store additional information related to this object.
WireAmount
integer
The amount of the wire transaction in cents.
WireAgent
object
Wire agent information.
5 properties
WireRejectionReasonV1
object
3 properties
APIError
object
6 properties
WireChargeBearer
string
Specifies which party bears the charges associated with the wire transfer.
WireRejectionReasonEnum
string
Reason to return a wire payment.
WireReturnV1
object
3 properties
WireTransferPurposeV1
object
The purpose or reason for which the wire is being sent.
2 properties 1 required
WireCreditorRequest
object
The person or entity to which the wire is being sent.
3 properties 3 required
LocalRoutingIdentifierRequest
object
Routing or transit code used by the creditor agent's local clearing system for international wire transfers, such as a sort code, IFSC, or BSB. This field may…
1 property
WirePaymentIdentifiers
object
Wire payment identifiers.
5 properties
WireStatus
string
The current status of the wire object.
WireOtherAgents
object
Details of any other agents involved in the wire transfer.
6 properties
WireAgentRequest
object
Wire agent information.
3 properties
CurrencyCode
string
A three-letter currency code as defined in ISO 4217.
WireRemittanceDetails
object
Wire remittance details.
5 properties
WirePartyAccountIdentifier
object
Object representing the account that the party holds at its financial institution
2 properties
WireDirection
string
Who is initiating the transaction. outgoing: You are sending a wire transaction to a counterparty. incoming: You are receiving an wire transaction from a count…
WireParty
object
Wire party information.
3 properties
WireReturnCode
string
List of eligible return reason codes for wire transfers. AC06 - accountblocked AM09 - wrongamount BE01 - creditornamemismatch FOCR - honorreturnrequest FR01 -…
WireAmounts
object
5 properties
AccountID
string
The ID of the Account object.
WirePostalAddressRequest
object
3 properties 1 required
LocalRoutingIdentifier
object
Routing or transit code used by the financial institution's local clearing system for international wire transfers, such as a sort code, IFSC, or BSB.
2 properties
RelatedWiresV1
object
Related wire objects.
2 properties
WireCharges
object
Information about charges associated with the wire transfer.
2 properties
InvalidParameterDetail
object
2 properties
WirePostalAddress
object
17 properties
WireChargeInfo
object
Details of a single charge assessed during wire transfer processing.
3 properties 2 required
IMAD
string
Input Message Accountability Data (IMAD), a unique identifier available to originating and receiving banks of a wire message.
WireV1
object
26 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lead-bank-wire-api-openapi.yml Raw ↑

Other APIs Lead Bank publishes across the network.

Lead Bank Lend API
Lead Bank Move API
Lead Bank Issue API
Lead Bank Store API
Lead Bank File Integrations (SFTP)
Lead Bank Webhooks
Lead Bank Account Number API
Lead Bank ACH API
Lead Bank Blockchain Payment API
Lead Bank Compliance API
Lead Bank Entity API
Lead Bank Events API
Where this information came from

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