The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are postalAddress (16 properties), contactDetails (13 properties), taxRecord (13 properties), taxRemittance (11 properties). Each schema is shown below with its type and property counts.
paymentIdentification
object
4 properties
error-500
object
500 - Internal Server Error
1 property1 required
errorDetails-401
object
2 properties2 required
internalServerErrorDetails
object
2 properties2 required
error-422
object
422 - Unprocessable request
1 property1 required
statusReasonInformation
object
2 properties
errorDetails-400
object
2 properties
error-401
object
Authentication failed or user doesn’t have permissions for requested operation
1 property
response-200
object
3 properties1 required
error-503
object
Service is temporarily unavailable
2 properties2 required
error-406
object
Web server doesn't find any content that conforms to the criteria given by the user agent.
2 properties2 required
error-405
object
The request method is known by the server but has been disabled and cannot be used.
2 properties2 required
unprocessableRequestErrorDetails
object
2 properties2 required
error-400
object
The request could not be understood or required parameters were missing
1 property
party
object
Identification of a person or an organisation
3 properties
error-415
object
The media format of the requested data is not supported by the server, so the server is rejecting the request.
2 properties2 required
error-404
object
Resource was not found.
2 properties2 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 properties2 required
amountAndType
array
taxPeriod
object
Party to which the tax applies.
5 properties
organisationIdentification
object
Identification of an organisation
5 properties
amountAndReason
array
paymentIdentification_2
object
3 properties2 required
postalAddress
object
Information that locates and identifies a specific address, as defined by postal services.
16 properties
taxRemittance
object
Provides remittance information about a payment made for tax-related purposes.
11 properties
lineIdentification
array
remittanceAmount
object
Provides details on the amounts.
6 properties
remittanceInformation
object
Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' rec…
2 properties
creditorDebtorParty
object
Identification of a person or an organisation
5 properties
privateIdentification
object
Unique and unambiguous identification of a person, for example a passport.
7 properties
garnishmentRemittance
object
Provides remittance information about a payment for garnishment-related purposes.
10 properties
remittanceParty
object
Identification of a person or an organisation
6 properties
contactDetails
object
Set of elements used to indicate how to contact the party.
13 properties
amount
object
2 properties2 required
taxParty
object
Party to which the tax applies.
5 properties
lineDetails
array
paymentTypeInformation
object
Set of elements used to further specify the type of transaction.
2 properties1 required
structuredRemittanceInformation
array
Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an…
referredDocumentInformation
array
response-200_2
object
4 properties2 required
taxRecord
object
Record of tax details
13 properties
agent
object
Identification of a financial institution.
2 properties2 required
creditorReferenceInformation
object
Reference information provided by the creditor to allow the identification of the underlying documents.
3 properties
account
object
Details to identify an account
1 property1 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Nacha Wire Transfer 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.
