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

Nacha Accounts API

The Accounts API from Nacha — 4 operation(s) for accounts.

Nacha Accounts API is one of 19 APIs that Nacha publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Account. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

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

Requests are made against 3 base URLs: /accounts/v1, https://api.asig.org/afinis/accounts/aavplus/v1, https://api.afinis.org/v1.

4 operations 4 paths 35 schemas 4 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.asig.org/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Nacha Accounts API declares 1 security scheme for authenticating requests. An API key is passed in the query as apikey (APIKeyQueryParam).

Paths & Operations 4

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

Accounts 4
POST
/validatewithnameandret
validateAccountWithNameAndRET 2 params body → 200400401403404405406415
POST
/validate
Account eligibility for debit ACH transactions
validateAccount 2 params body → 200400401403404405406415
POST
/accounts/validate/achPaymentDebitAcceptance
Account eligibility for debit ACH transactions
validateDebtorAccount 1 param body → 200400401404500503
POST
/accounts/validate/achPaymentCreditAcceptance
Account eligibility for credit ACH transactions
validateCreditorAccount 1 param body → 200400401404500503

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are response-200_2 (6 properties), owner (5 properties), response-200 (4 properties), ACHPaymentAcceptanceDebit (3 properties). Each schema is shown below with its type and property counts.

error-500
object
500 - Internal Server Error
1 property 1 required
errorDetails-401
object
2 properties 2 required
internalServerErrorDetails
object
2 properties 2 required
owner
object
Party that legally owns the account.
5 properties
returns
array
Contains RET fields for the response
errorDetails-400
object
2 properties
error-401
object
Authentication failed or user doesn’t have permissions for requested operation
1 property
response-200
object
200 - OK
4 properties
error-503
object
Service is temporarily unavailable
2 properties 2 required
error-406
object
Web server doesn't find any content that conforms to the criteria given by the user agent.
2 properties 2 required
error-405
object
The request method is known by the server but has been disabled and cannot be used.
2 properties 2 required
error-400
object
The request could not be understood or required parameters were missing
1 property
agent
object
Identification of a financial institution.
2 properties 2 required
error-415
object
The media format of the requested data is not supported by the server, so the server is rejecting the request.
2 properties 2 required
error-404
object
Resource was not found.
2 properties 2 required
account
object
1 property 1 required
error-403
object
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the c…
2 properties 2 required
debtorAccount
object
1 property 1 required
statusReasonInformation
object
2 properties
response-200_2
object
200 - OK
6 properties
debtorAgent
object
Identification of a financial institution.
2 properties 2 required
associatedName
object
Party that legally owns the account.
2 properties
ACHPaymentAcceptanceDebit
object
3 properties
error-500_2
object
1 property
CreditorAccount
object
1 property 1 required
errorDetails-401_2
object
2 properties 2 required
ACHPaymentAcceptanceCredit
object
3 properties
CreditorAgent
object
2 properties
errorDetails-400_2
object
2 properties 2 required
error-401_2
object
1 property
errorDetails-500
object
2 properties 2 required
DebtorAgent
object
2 properties
error-400_2
object
1 property
DebtorAccount
object
1 property 1 required
AccountStatus
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nacha-accounts-api-openapi.yml Raw ↑

Other APIs Nacha publishes across the network.

Nacha Account Validation API
Nacha ACH Payments API
Nacha ACH Transaction Status API
Nacha Authorize to Pay API
Nacha Banks API
Nacha Expand Bank Contact V2 API
Nacha Get Corporate Account Balances API
Nacha Get Corporate Transaction History API
Nacha Get Participants Profile API
Nacha Initiate Payment API
Nacha Instant Payment API
Nacha Instant Payment Transfer API
Where this information came from

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