API request throttler for Power Query

Problem Context

Power BI users rely on Power Query to pull data from APIs into dashboards. Many APIs enforce strict concurrency limits (e.g., 2 simultaneous requests). Power Query’s default behavior sends multiple parallel requests, triggering 'concurrency limit reached' errors and blocking data access. Users must manually reduce data size or avoid previews, slowing down workflows and breaking automation.

Pain Points

Power Query sends parallel API requests by default, hitting concurrency limits even for small datasets. Users can’t preview data in Power Query, forcing them to guess-and-check changes. Manual workarounds (like limiting data or using 'Close & Apply') are unreliable and time-consuming. The issue disrupts critical analytics workflows, especially for teams dependent on real-time API data.

Impact

Failed API requests waste hours per week as users debug concurrency errors. Broken data pipelines delay reporting, dashboards, and decision-making. Teams may miss revenue opportunities or operational insights due to stalled analytics. Frustration grows when native tools (Power Query) lack built-in throttling controls, forcing users to abandon features or switch tools.

Urgency

This problem blocks daily work for API-dependent teams. Without a fix, users can’t iterate on dashboards or automate data refreshes. The risk of concurrency limits increases as API usage grows, making the issue worse over time. Ignoring it means accepting slower, less reliable analytics—something no data team can afford long-term.

Target Audience

Power BI/Power Query users who pull data from APIs (e.g., REST, GraphQL). This includes data analysts, BI engineers, and business intelligence teams in mid-sized companies. Freelancers and consultants also face this when building client dashboards. Any user relying on Power Query for API-based workflows will encounter this issue.

Solution Approach

A lightweight tool that sits between Power Query and APIs, automatically throttling requests to comply with concurrency limits. It queues API calls, enforces delays between requests, and retries failed attempts—all without requiring changes to Power Query or API endpoints. Users configure their API’s concurrency rules once, then forget about limits.

Key Features

1. Dynamic Throttling: Adjusts delays between requests based on API response times.
2. Retry Logic: Automatically retries failed requests with exponential backoff.
3. Preview Mode: Lets users test API connections in Power Query without hitting limits (bypasses the preview blocker).

User Experience

Users install the tool as a browser extension or local proxy. They enter their API’s concurrency limit (e.g., 2) in a simple settings panel. Power Query works as usual, but requests are now throttled in the background. Previews load without errors, and 'Close & Apply' succeeds on the first try. No code changes or admin access needed.

Differentiation

Unlike free tools (e.g., Postman), this focuses *exclusively- on Power Query’s API concurrency issue. It doesn’t require API keys or vendor approvals. Native Power Query has no built-in throttling, and manual workarounds (like reducing data size) are unreliable. This tool is the only solution designed for Power Query’s parallel request behavior.

Scalability

Starts with a single-API configuration, then expands to support multiple APIs per user. Can add team features (shared throttling rules) or monitoring (API usage analytics). Pricing scales with API connections or team size. Integrates with Power BI’s refresh schedules for automated workflows.

Expected Impact

Users regain control over API-based dashboards, saving hours per week. Data pipelines run reliably, eliminating errors and retries. Teams can automate refreshes without manual intervention. The tool pays for itself by restoring lost productivity and preventing revenue risks from stalled analytics.