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

Dwolla funding sources API

Operations related to Funding Sources

Dwolla funding sources API is one of 18 APIs that Dwolla publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 9 operations across 6 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: https://api.dwolla.com, https://api-sandbox.dwolla.com.

9 operations 6 paths 23 schemas 5 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.dwolla.com
Authentication
OAuth 2.0
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Dwolla funding sources API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (clientCredentials) using the clientCredentials flow. By default, every request must be authenticated.

Paths & Operations 9

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

funding sources 9

Operations related to Funding Sources

GET
/customers/{id}/funding-sources
List customer funding sources
listCustomerFundingSources 3 params → 200403404
POST
/customers/{id}/funding-sources
Create customer funding source
createCustomerFundingSource 2 params body → 201400403404
GET
/funding-sources/{id}
Retrieve a funding source
getFundingSource 2 params → 200404
POST
/funding-sources/{id}
Update or remove a funding source
updateOrRemoveFundingSource 2 params body → 200400403
GET
/funding-sources/{id}/micro-deposits
Retrieve micro-deposits details
getMicroDeposits 2 params → 200404
POST
/funding-sources/{id}/micro-deposits
Initiate or Verify micro-deposits
initiateOrVerifyMicroDeposits 2 params body → 200201403404
GET
/funding-sources/{id}/balance
Retrieve funding source balance
getFundingSourceBalance 2 params → 200404
GET
/funding-sources/{id}/ach-routing
Retrieve VAN account and routing numbers
getVanRouting 2 params → 200404
POST
/on-demand-authorizations
Create an on-demand transfer authorization
createOnDemandTransferAuthorization 1 param → 200403

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are FundingSource (13 properties), CreateCustomerBankFundingSourceWithAccountNumbers (7 properties), CreateCustomerBankFundingSourceWithPlaid (5 properties), UpdateUnverifiedBank (4 properties). Each schema is shown below with its type and property counts.

FundingSources
object
3 properties
OnDemandAuthorization
object
3 properties
MaximumCardsExceededError
object
Error returned when a customer has exceeded the maximum number of debit card funding sources
3 properties 3 required
InactiveExchangeError
object
2 properties 2 required
InvalidTokenError
object
Error returned when creating an Exchange with an invalid token, or when the card data is invalid
3 properties 3 required
UnsupportedCardCountryError
object
Error returned when attempting to create a debit card funding source from an unsupported country
3 properties 3 required
CreateCustomerExchangeFundingSource
object
Schema for creating a funding source using an exchange resource. This method is used when the bank account information is obtained via Instant Account Verifica…
3 properties 3 required
RemoveBank
object
Request body for removing a bank funding source
1 property 1 required
DuplicateFundingSourceError
object
2 properties 2 required
CreateCustomerBankFundingSourceWithAccountNumbers
object
Schema for creating a basic bank funding source using routing and account numbers. This is the traditional method of adding a bank account.
7 properties 4 required
InvalidExchangeTokenError
object
2 properties 2 required
FundingSource
object
13 properties
VerifyMicroDeposits
object
Request body for verifying micro-deposits
2 properties 2 required
CardMissingRequiredFieldsError
object
Error returned when required fields are missing when creating an Exchange or a debit card funding source
3 properties 3 required
NotFoundError
object
Error response schema for 404 NotFound
2 properties 2 required
CreateCustomerBankFundingSourceWithPlaid
object
Schema for creating a bank funding source using a Plaid processor token.
5 properties 3 required
CreateCustomerCardFundingSourceWithExchange
object
Schema for creating a debit card funding source using an Exchange. Used for Push to Card.
3 properties 3 required
UpdateVerifiedBank
object
Request body for updating information of a Verified bank funding source
1 property 1 required
HalLink
object
3 properties
CreateCustomerFundingSource
Parameters for creating customer funding sources using different methods: - Bank Account: Traditional method using routing/account numbers - Exchange: Using IA…
CreateCustomerVirtualAccountFundingSource
object
Schema for creating a Virtual Account Number (VAN) . VANs are unique account numbers for receiving external transactions into a Dwolla Balance.
3 properties 3 required
UpdateUnverifiedBank
object
Request body for updating information of an unverified bank funding source
4 properties 1 required
ForbiddenError
object
Error response schema for 403 Forbidden
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dwolla-funding-sources-api-openapi.yml Raw ↑

Other APIs Dwolla publishes across the network.

Dwolla Accounts API
Dwolla beneficial owners API
Dwolla client tokens API
Dwolla Customers API
Dwolla Documents API
Dwolla Events API
Dwolla exchange sessions API
Dwolla Exchanges API
Dwolla Kba API
Dwolla Labels API
Dwolla mass payments API
Dwolla Root API
Where this information came from

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