Google Looker · Rate Limits

Google Looker Rate Limits

Google Looker (Google Cloud core) enforces request limits as monthly API-call quotas tied to the platform edition rather than per-second throttling. Standard, Enterprise, and Embed editions provide different monthly allowances for query-based and admin API calls. Per-instance request limits are also governed by the size and concurrency settings of the Looker instance itself.

Google Looker Rate Limits is the machine-readable rate-limit profile for Google Looker on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 7 rate-limit definitions, measuring requests_per_month and varies.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Rate Limiting, Business Intelligence, Analytics, and Google Cloud.

7 Limits Throttle: 429 Quota: 429
Rate LimitingBusiness IntelligenceAnalyticsGoogle Cloud

Limits

Query-based API calls (Standard edition) instance
requests_per_month · month
1000
Aggregated across all query-based endpoints. Overage requires upgrade to higher edition.
Admin API calls (Standard edition) instance
requests_per_month · month
1000
Query-based API calls (Enterprise edition) instance
requests_per_month · month
100000
Admin API calls (Enterprise edition) instance
requests_per_month · month
10000
Query-based API calls (Embed edition) instance
requests_per_month · month
500000
Admin API calls (Embed edition) instance
requests_per_month · month
100000
Per-instance concurrency instance
varies
see service-specific quotas page
Concurrent query and request capacity is determined by Looker instance sizing; contact support for higher concurrency.

Policies

Backoff Strategy
Implement exponential backoff with jitter when receiving 429 or 503; respect Retry-After where present.
Quota tied to edition
Monthly API quotas reset on a calendar basis and are determined by the Looker platform edition; upgrades raise the cap.
Long-running queries
Use async query endpoints for queries that may exceed default request timeouts; poll for completion rather than blocking the request thread.

Sources