Dwolla
Dwolla is a Des Moines-based fintech providing an account-to-account (A2A) payments platform that lets businesses programmatically move money across the U.S. banking system. Its v2 REST API — a JSON-HAL hypermedia API secured with OAuth 2.0 client-credentials — supports ACH (standard and Same-Day), instant/real-time payments over the RTP Network and FedNow Service, bank funding sources with micro-deposit and Open Banking (Plaid/MX) verification, verified Customers (personal and business with beneficial-owner/KYC flows), mass payments, labels and ledgers, virtual account numbers, and webhook event notifications. Dwolla ships official SDKs for Node, Python, Ruby, PHP, C#, and Kotlin, low-code Drop-in Components, and a read-only MCP server for AI agents.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Dwolla the way a machine reads it — 62 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Dwolla scores 60.2/100 (strong), with a separate agent-readiness read of 53/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Dwolla's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/dwolla/"
title="Dwolla on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/dwolla.svg"
alt="Dwolla Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/dwolla/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/dwolla/"
title="Dwolla on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/dwolla/card.svg"
alt="Dwolla Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Dwolla
Each block below is one kind of artifact we hold for Dwolla. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Dwolla Accounts API
Operations related to Accounts
Dwolla beneficial owners API
Operations related to Beneficial Owners
Dwolla client tokens API
Operations related to Client Tokens
Dwolla Customers API
Operations related to Customers
Dwolla Documents API
Operations related to Documents
Dwolla Events API
Operations related to Events
Dwolla exchange sessions API
Operations related to Exchange Sessions
Dwolla Exchanges API
Operations related to Exchanges
Dwolla funding sources API
Operations related to Funding Sources
Dwolla Kba API
Operations related to Knowledge-Based Authentication
Dwolla Labels API
Operations related to Labels
Dwolla mass payments API
Operations related to Mass Payments
Dwolla Root API
Root API operations
Dwolla sandbox simulations API
Sandbox-only operations for simulating processing of bank transfers
Dwolla Tokens API
Operations related to Application Access Tokens
Dwolla Transfers API
Operations related to Transfers
Dwolla webhook subscriptions API
Operations related to Webhook Subscriptions
Dwolla Webhooks API
Operations related to Webhooks
Scroll within the panel for all 18 ·
Postman Collections 18
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Dwolla API - Accounts
POSTMANDwolla API - Client Tokens
POSTMANDwolla API - Customers
POSTMANDwolla API - Documents
POSTMANDwolla API - Events
POSTMANDwolla API - Exchanges
POSTMANDwolla API - Funding Sources
POSTMANDwolla API - Kba
POSTMANDwolla API - Labels
POSTMANDwolla API - Mass Payments
POSTMANDwolla API - Root
POSTMANDwolla API - Tokens
POSTMANDwolla API - Transfers
POSTMANDwolla API - Webhooks
POSTMANScroll within the panel for all 18 ·
Open Collections 19
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Dwolla API - Accounts
OPEN COLLECTIONDwolla API - Beneficial Owners
OPEN COLLECTIONDwolla API - Client Tokens
OPEN COLLECTIONDwolla API - Customers
OPEN COLLECTIONDwolla API - Documents
OPEN COLLECTIONDwolla API - Events
OPEN COLLECTIONDwolla API - Exchange Sessions
OPEN COLLECTIONDwolla API - Exchanges
OPEN COLLECTIONDwolla API - Funding Sources
OPEN COLLECTIONDwolla API - Kba
OPEN COLLECTIONDwolla API - Labels
OPEN COLLECTIONDwolla API - Mass Payments
OPEN COLLECTIONDwolla API - Root
OPEN COLLECTIONDwolla API - Sandbox Simulations
OPEN COLLECTIONDwolla API - Tokens
OPEN COLLECTIONDwolla API - Transfers
OPEN COLLECTIONDwolla API - Webhook Subscriptions
OPEN COLLECTIONDwolla API - Webhooks
OPEN COLLECTIONDwolla API
OPEN COLLECTIONScroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Dwolla MCP Server
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Dwolla Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Dwolla Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Dwolla — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 7
Status, limits, changes, and where to get help
Scroll within the panel for all 7 ·
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/dwolla · machine-readable index on apis.io
This is an independent, third-party profile of Dwolla, 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.