> ## Documentation Index
> Fetch the complete documentation index at: https://developers.dwolla.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate Limits

> Ensure smooth integration by understanding Dwolla's API rate limits. Grasp concurrency and volume-based limits, and learn effective strategies to handle 429 Too Many Requests errors.

## Overview

Dwolla imposes a rate limit for any applications that make requests to our API. Currently, we have the following rate limit defined:

* Concurrency-based: Quick successive transfers sourced from the same [Dwolla Wallet](/docs/balance-funding-source) associated with a Dwolla [Account](/docs/api-reference/accounts) or [Customer](/docs/api-reference/customers) may receive an HTTP 429 Too Many Requests status code.
* Volume-based: If the rate limit is reached for an endpoint, subsequent requests will result in an HTTP 429 Too Many Requests status code, which will persist for 5 minutes. At this time, these thresholds are defined as outside the range of what we consider normal API usage.

Dwolla recommends building a mechanism into your application to handle 429 Too Many Requests responses, which would retry the request following an exponential backoff schedule to reduce request volume, and utilizes [idempotency keys](/docs/api-reference/api-fundamentals/idempotency-key), where applicable. This ensures actions only perform once and prevents creation of duplicate records.

If you believe that your application will require a high rate of API calls, please contact [support@dwolla.com](mailto:support@dwolla.com) for further assistance.