---
title: API Rate Limiting
slug: api-rate-limiting
docTags: 
createdAt: 2025-08-26T15:12:17.000Z
---

Turbine Cloud enforces rate limits to ensure platform stability and fair usage across all tenants.

## At a Glance

## Standard API Rate Limit

The global rate limit applies to **any HTTP request through the public load balancer** — including API calls, playbook actions, and UI requests.

**Scope — user hash:** The rate limit is calculated per unique combination of authentication method and source IP:

:::hint{type="info"}
If a playbook makes anonymous outbound HTTP calls, those requests are sourced from the region's shared egress IP and count toward the rate limit pool for that IP.
:::

## Webhook Rate Limit

Webhooks have a dedicated rate limit enforced separately from the standard API limit: **100 requests/minute per tenant**.

:::hint{type="info"}
For MSSP or multi-tenant architectures where a central tenant sends webhook requests to customer tenants, each tenant's webhook traffic is rate-limited independently.
:::

## Rate Limit Behavior

When a rate limit is exceeded, the API returns a 429 Too Many Requests response. Implement exponential backoff and retry logic in your integrations to handle rate limiting gracefully.