Overview
Learn how Dash Social handles API rate limits and paginated responses. This helps you avoid throttling and reliably fetch large sets of data across multiple requests.
Rate Limits
To ensure consistent performance across all users, the Dash Social API enforces rate limits at two levels:
- App-level limit: Your application can make up to 1000 requests per minute total.
- Endpoint-level limits: Some endpoints may have stricter rate limits depending on system load or data sensitivity.
Every API response includes headers that show your current usage:
Use these headers to monitor and manage your request volume dynamically.
Best Practices
- Monitor your headers: Track
x-ratelimit-remaining to avoid hitting limits.
- Cache responses: Reduce repeated API calls when possible.
- Back off gracefully: If throttled, retry after the reset time.
- Batch your requests: Use pagination instead of pulling all data at once.
When Limits Are Exceeded
If your app exceeds the rate limit, requests will return an error and be temporarily throttled.
Wait until the x-ratelimit-reset time before sending new requests.
When fetching large collections - such as media, boards, or scheduled posts - the Dash Social API returns results in pages.
Each “list” endpoint includes a standard paging object in the response:
How it works
- The data array contains the current page of results.
- The next and previous fields provide full URLs for the next and previous pages.
- If next is null, you’ve reached the end of the results.
Parameters
You can control how many results are returned per request using limit and offset.
Example
Fetch the first 10 media items:
Then use the “next” URL from the response to get the next page:
