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 ACH API

The ACH API from Lead Bank — 5 operation(s) for ach.

Lead Bank ACH 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 ACH. The published artifact set on APIs.io includes an OpenAPI specification.

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

7 operations 5 paths 33 schemas 2 GET1 PATCH4 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 ACH API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 7

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

ACH 7
POST
/v1/ach
Create an ACH
create-an-ach 1 param body → 200400422
GET
/v1/ach
List all ACHes
list-all-ach 11 params → 200400404
GET
/v1/ach/{ach_id}
Retrieve an ACH
retrieve-an-ach 1 param → 200404
PATCH
/v1/ach/{ach_id}
Update an ACH
update-an-ach 2 params body → 200400404
POST
/v1/ach/{ach_id}/cancel
Cancel an ACH
cancel-an-ach 2 params body → 200400
POST
/v1/ach/{ach_id}/return
Return an ACH
return-an-ach 2 params body → 200400404
POST
/v1/ach/{ach_id}/reverse
Reverse an ACH
reverse-an-ach 2 params body → 200400404

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Ach (21 properties), IatDetails (11 properties), APIError (6 properties), Return (6 properties). Each schema is shown below with its type and property counts.

DeliveryType
string
How fast you want the counterparty to receive the ACH. samebusinessday: if the ACH request is submitted before the cutoff window with the same business day opt…
IatParty
object
Name and address of a party to an IAT transaction, in NACHA format.
4 properties
RejectionReason
object
2 properties
AccountNumberID
string
The ID of the Lead Bank Account Number object.
AchStatus
string
The current status of the ACH object.
IatReceiver
object
Name, reference number, and address of the receiver of an IAT transaction.
5 properties
Metadata
object
A set of key-value pairs that can be used to store additional information related to this object.
ReceiverName
string
The name of the receiver of funds. Note: This field is set by the counterparty and may or not be accurate.
Amount
integer
The amount of the transaction in cents.
APIError
object
6 properties
AchCorrection
object
The corrected counterparty details.
3 properties
SecCode
string
Standard Entry Class (SEC) code to use for this ACH object. Lead currently only supports CCD, PPD, WEB, and TEL for outgoing ACHes.
TransactionType
string
ACH transaction type.
AccountType
string
The account type for the bank account. This should be one of checking or savings.
Ach
object
21 properties
IatFinancialInstitution
object
Financial institution details for an IAT transaction.
4 properties
IatTransactionTypeCode
string
Identifies the purpose of the IAT transaction.
IatDetails
object
IAT (International ACH Transaction) specific details. Present only when seccode is IAT.
11 properties
Direction
string
Who is initiating the transaction. outgoing: You are sending a transaction to a counterparty. incoming: You are receiving a transaction from a counterparty.
CurrencyCode
string
A three-letter currency code as defined in ISO 4217.
AccountID
string
The ID of the Account object.
ReturnCode
string
NACHA Return codes.
Counterparty
object
The details of the counterparty you are sending/receiving money from.
4 properties 4 required
AdditionalInformation
string
Additional information for the ACH recipient. Not all banks will share this message with their end customer.
StatementDescriptor
string
The description you would like to appear on your customers’ statement. Maximum number of characters is 10.
ReversalReason
string
Reason you want to initiate a reversal.
DescriptiveDate
string
The date you would like displayed to the counterparty. Receiving financial institutions may utilize this field to display on the statement.
InvalidParameterDetail
object
2 properties
IndividualId
string
The name of the individual you are sending funds to. Required for P2P payments.
Return
object
6 properties
OutgoingSecCode
string
The Standard Entry Class, SEC, to code the outgoing ACH. Lead currently supports: CCD: Corporate payment PPD: Written authorization to initiate payment TEL: Te…
OutgoingReturnCode
string
The NACHA Return code you want to initiate this return under.
TransactionCode
string
Identifies the type of debit or credit Entry and the account type

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lead-bank-ach-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 Blockchain Payment API
Lead Bank Compliance API
Lead Bank Entity API
Lead Bank Events API
Lead Bank Funding API
Where this information came from

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