API rate limits (like GA4 or Stripe) affect how fast Airbyte can read from the API and whether retries are needed, but Airbyte has built‑in mechanisms to handle them. ### 1. Default retry & backoff (CDK and Builder) For HTTP-based connectors using the Python CDK, Airbyte: - Automatically retries on HTTP 429 and 5XX responses - Uses an exponential backoff and fails after 5 tries by default [[HTTP CDK rate limiting 1.6](https://docs.airbyte.com/platform/1.6/connector-development/cdk-python/http-streams#rate-limiting); [HTTP CDK rate limiting 1.8](https://docs.airbyte.com/platform/1.8/connector-development/cdk-python/http-streams#rate-limiting)]. - You can override

should_retry

and

backoff_time

in custom CDK connectors if the API has special rules [[HTTP CDK 1.8](https://docs.airbyte.com/platform/1.8/connector-development/cdk-python/http-streams#rate-limiting)]. In the Connector Builder UI, default behavior (when you don’t configure an error handler) is also to: - Retry on 429 and 5XX, - Up to 5 retries, - With a 5‑second exponential backoff [[Error handling – default](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/error-handling)]. You can explicitly configure backoff strategies per API: - Constant, Exponential, or Wait time from header / until time from header based on API docs and headers like

Retry-After

[[Backoff strategies 1.8](https://docs.airbyte.com/platform/1.8/connector-development/connector-builder-ui/error-handling#backoff-strategies)]. ### 2. Global rate limiting (HTTP API Budget) For APIs with strict limits (like GA4 or Stripe), you can cap request throughput via API Budget / HTTP API Budget in config-based connectors and in the Connector Builder Global Configuration: - Define call limits per time window (Fixed window, Moving window, or Unlimited) [[Rate limiting API Budget](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/rate-limit-api-budget); [Global configuration HTTP API Budget](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/global-configuration#http-api-budget)]. - Optionally read limit info from headers like

X-RateLimit-Remaining

and

X-RateLimit-Reset

, and specify which status codes (usually 429) indicate a rate‑limit hit [[Rate limiting API Budget](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/rate-limit-api-budget); [Global configuration HTTP API Budget](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/global-configuration#http-api-budget)]. - When a rate limit status code is hit, Airbyte pauses and retries according to these policies [[Global configuration HTTP API Budget](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/global-configuration#http-api-budget)]. ### 3. Stripe-specific behavior For Stripe, the docs state: - Under normal usage, the connector should not hit Stripe rate limits, and rate‑limited calls are automatically retried. - You’re asked to open an issue if you see rate limit problems that aren’t retried successfully [[Stripe rate limiting](https://docs.airbyte.com/integrations/sources/stripe#rate-limiting)]. ### 4. Practical impact - If GA4/Stripe limits are hit, Airbyte will slow down syncs (due to backoff or API Budget waits) but should still complete as long as limits allow enough throughput. - If limits are very strict vs. data volume, syncs can become longer or fail after repeated retries. If you share the exact GA4 or Stripe rate limit you’re concerned about (e.g., X requests per hour), I can suggest a concrete API Budget / backoff configuration pattern using the mechanisms above.

For the free tiers of GA4 and Stripe, here’s what the Airbyte docs say about how limits affect connectors: ### GA4 (Google Analytics 4 – Google Analytics Data API) - The GA4 connector is explicitly subject to Google Analytics Data API quotas. [[GA4 performance](https://docs.airbyte.com/integrations/sources/google-analytics-data-api#performance-considerations)] - Airbyte does not restate the exact free‑tier numbers; you must rely on Google’s own quota page for the precise limits. [[GA4 performance](https://docs.airbyte.com/integrations/sources/google-analytics-data-api#performance-considerations)] - Forum posts show that users can hit errors like “Exhausted property tokens for a project per hour” even when daily quota remains, meaning hourly / per‑property token limits are often the bottleneck. [[GA4 quota error](https://discuss.airbyte.io/t/3413); [GA4 exhausted tokens discussion](https://discuss.airbyte.io/t/2547)] - The knowledge sources do not provide specific recommended rate settings for free GA4; you’d need to size sync frequency and scope so you stay under those Google quotas. ### Stripe - Stripe has its own rate limits; the connector docs say that under normal usage it “should not run into Stripe API limitations,” and that rate‑limited calls are automatically retried. [[Stripe rate limiting](https://docs.airbyte.com/integrations/sources/stripe#rate-limiting)] - No specific free‑plan numbers (requests per second, etc.) are restated in the Airbyte docs; they point you to Stripe’s own Rate limits documentation for details. [[Stripe rate limiting](https://docs.airbyte.com/integrations/sources/stripe#rate-limiting)] ### Summary - For both free GA4 and free Stripe: - Airbyte depends on the provider’s quotas and does not override or extend them. - When limits are hit (e.g., GA4 429 quota errors), Airbyte backs off / retries, but if the external quota is too low for the amount of data requested, syncs may slow down or fail. [[GA4 performance](https://docs.airbyte.com/integrations/sources/google-analytics-data-api#performance-considerations); [Stripe rate limiting](https://docs.airbyte.com/integrations/sources/stripe#rate-limiting)] - The exact free‑tier quotas (numbers) must be taken from Google’s and Stripe’s own documentation; they are not enumerated in the Airbyte knowledge sources.