Transfer

As explained in The Design of Web APIs, Second Edition

A money transfer is a financial transaction that moves a specified amount from a source account or party to a destination account or party.

A money transfer moves a specified amount from a source account to a destination account. A transfer may happen immediately, on a future date, or repeatedly. section 9.4.4

A user-friendly transfer operation requires source, destination, and amount. Currency can default to the source account currency; a date implies a delayed transfer, while frequency implies a recurring transfer. section 9.4.4 section 9.4.1

A practical transfer flow validates both the participants and the transaction:

• List the user’s accounts and exclude blocked source accounts. section 10.3.1
• List preregistered beneficiaries and user-owned destination accounts. section 10.3.1
• Submit the selected source, destination, and amount through the Transfer operation. section 10.3.1
• Handle ownership, account status, authorization, balance, account limits, and rolling user limits before completing the transfer. section 10.3.1

Minimal transfer request

POST /transfers with a request body containing source, destination, and amount represents an immediate transfer. Adding a date schedules it; adding frequency makes it recurring. Omitting currency uses the source account currency by default. section 9.4.4 section 9.4.1

Figure 9.7 We minimize money transfer inputs by determining data based on other data and using default data.

Use the input diagram to compare explicitly supplied transfer data with values inferred or defaulted by the implementation. section 9.4.4

How The Design of Web APIs, Second Edition covers it

How deep it goes

Defines transfer variants, input defaults, validation failures, and API boundaries without descending into implementation internals.

Examples

Uses POST /transfers, account and beneficiary listings, immediate or scheduled transfers, recurring frequency, and transfer validation.

What it assumes

Assumes familiarity with accounts and HTTP operations while teaching transfer inputs, beneficiaries, defaults, and failure conditions.

What you can do after

Operate/configure transfer flows by minimizing inputs, choosing HTTP-compliant locations, and validating account and amount constraints.

How it connects

Connects transfers with accounts, beneficiaries, authorization, HTTP request bodies, API decomposition, and security-sensitive operations.

liveBookmanning.com

Read The Design of Web APIs, Second Edition on liveBook Get the book at manning.com

Related concepts

• use casekind of · A use case is a description of a situation or interaction in which a system, method, or capability is applied to achieve or support a goal or outcome.
• subdomainkind of · A subdomain is a bounded subdivision or subordinate namespace within a broader domain, such as a business area or a domain-name hierarchy.
• unique identifieruses · A unique identifier is a value or name that distinguishes an entity or record from others within a defined scope or namespace.
• account balanceuses · An account balance is the recorded amount of money or funds associated with a financial account.

This explainer was generated by Manning's knowledge graph from the text of The Design of Web APIs, Second Edition. The section links point to the parts of the book it draws on.