Pipedream rate limits
The following rate limits apply to the Connect API:
To get the connected accounts for one user, use List user accounts (
GET /users/{external_user_id}/accounts). It is the fastest way to retrieve account details and credentials.
Access tokens from POST /v1/oauth/token are valid for multiple requests. Reuse a token until it expires. Do not request a new token for each API call.
Pipedream also applies per-IP rate limits to all traffic to protect the platform.
Need higher limits? Contact our support team to discuss your requirements.
Rate limit responses
When you exceed a limit, the API returns HTTP429 Too Many Requests. Responses from the per-project and per-client limits above include these headers:
Wait until the window resets before you retry. Use exponential backoff for retries.
Custom rate limits
You can set custom rate limits for your users to control their usage of the Connect API and prevent runaway requests or abuse.Create rate limit
Create a rate limit by specifying a time window and maximum requests allowed within that window. The API returns arate_limit_token that you include in subsequent Connect API requests.
Parameters
Example request
Response
Using rate limit tokens
Include therate_limit_token in the x-pd-rate-limit header for all Connect API requests:
rate_limit_token share one limit. To give each of your users a separate limit, create a token for each user.
When a request exceeds a custom rate limit, the API returns HTTP 429 Too Many Requests with an x-pd-rate-limit-reset-in header. The header gives the number of seconds until the window resets.
