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

Moov Transfers API

Initiate and manage money movement between Moov accounts. Supports ACH, RTP, and card rails with full lifecycle tracking.

Moov Transfers API is one of 19 APIs that Moov publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Transfers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, a JSON-LD context, and 2 JSON Schemas.

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

Requests are made against a single base URL, https://api.moov.io.

10 operations 6 paths 17 schemas 4 GET1 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Server
https://api.moov.io
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — OAuth2 bearer token obtained from the /oauth2/token endpoint. Include in the Authorization header as "Bearer {token}".

Paths & Operations 10

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

Transfers 10

Initiate and manage money movement between Moov accounts. Supports ACH, RTP, and card rails with full lifecycle tracking.

POST
/accounts/{accountID}/transfers
Create a transfer
createTransfer 2 params body → 200400401
GET
/accounts/{accountID}/transfers
List transfers
listTransfers 5 params → 200401
GET
/accounts/{accountID}/transfers/{transferID}
Retrieve a transfer
getTransfer 4 params → 200401404
PATCH
/accounts/{accountID}/transfers/{transferID}
Update transfer metadata
updateTransferMetadata 4 params body → 200400401404
POST
/accounts/{accountID}/transfer-options
Retrieve transfer options
getTransferOptions 2 params body → 200400401
POST
/accounts/{accountID}/transfers/{transferID}/cancellations
Cancel a transfer
cancelTransfer 4 params → 200400401404
POST
/accounts/{accountID}/transfer-config
Create transfer configuration.
createTransferConfig 1 param → 200
GET
/accounts/{accountID}/transfer-config
Get transfer configuration.
getTransferConfig 1 param → 200
PUT
/accounts/{accountID}/transfer-config
Update transfer configuration.
updateTransferConfig 1 param → 200
GET
/accounts/{accountID}/transfers/{transferID}/cancellations/{cancellationID}
Get cancellation details.
getCancellation 3 params → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are Card (14 properties), Transfer (13 properties), BankAccount (9 properties), CreateTransferRequest (6 properties). Each schema is shown below with its type and property counts.

PaymentMethodOption
object
A payment method option with its compatible payment rails.
3 properties
CreateTransferRequest
object
Request body for initiating a new transfer between Moov accounts.
6 properties 3 required
TransferAccountRef
object
Reference to the Moov account involved in a transfer.
3 properties
CardExpiration
object
Card expiration date.
2 properties
Error
object
Standard error response returned by the Moov API.
2 properties
TransferParticipant
object
Source or destination participant in a Moov transfer.
6 properties
Address
object
Physical or mailing address.
6 properties
Wallet
object
A Moov digital wallet that holds funds on the platform for an account. Wallets serve as intermediate stores of value for money movement.
4 properties
Amount
object
A monetary amount with currency denomination.
2 properties
BankAccount
object
A bank account linked to a Moov account as a funding source for ACH and RTP transfers.
9 properties
TransferOptions
object
Available payment rails and options for a proposed transfer.
2 properties
Transfer
object
A money movement operation between two Moov accounts. Transfers have a source (origin) and destination, and are processed over ACH, RTP, or card rails.
13 properties
TransferCancellation
object
A cancellation request for a pending transfer.
3 properties
TransferOptionsRequest
object
Request body for retrieving available transfer options.
3 properties 3 required
Card
object
A credit or debit card linked to a Moov account as a payment source.
14 properties
CardVerification
object
Results of card verification checks.
3 properties
UpdateTransferRequest
object
Request body for updating transfer metadata.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

moov-transfers-api-openapi.yml Raw ↑

Other APIs Moov publishes across the network.

Moov Drops
Moov Backend SDKs
Moov Accounts API
Moov Authentication API
Moov Bank Accounts API
Moov Capabilities API
Moov Cards API
Moov Disputes API
Moov Payment Links API
Moov Payment Methods API
Moov Refunds API
Where this information came from

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