Ensembl · Rate Limits

Ensembl Rate Limits

The Ensembl REST API applies per-IP rate limiting of 55,000 requests per hour (approximately 15 requests per second). No authentication is required and no API key is needed. Rate limit state is communicated via X-RateLimit-* response headers. When the quota is exhausted the API returns HTTP 429 with a Retry-After header indicating the fractional number of seconds the client must wait before resuming. For high-volume use cases Ensembl recommends mirroring the database locally or using FTP bulk downloads.

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

It captures 2 rate-limit definitions, measuring requests.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, unauthorized, and serverError.

Tagged areas include Genomics, Bioinformatics, Genome Annotation, Life Sciences, and Rate Limiting.

2 Limits Throttle: 429
GenomicsBioinformaticsGenome AnnotationLife SciencesRate Limiting

Limits

Requests Per Hour ip_address
requests · hour
55000
55,000 requests per rolling hour per source IP address. Applies to all REST API endpoints equally. Shared IP addresses (e.g. corporate NAT or cloud egress) share this quota across all users behind that IP.
Recommended Request Rate ip_address
requests · second
15
Ensembl recommends clients self-throttle to 15 requests per second to avoid exhausting the hourly quota and to be a good citizen on the shared public infrastructure.

Policies

Self-Throttle to 15 req/s
All example clients in the official Ensembl documentation self-throttle to 15 requests per second and honour the Retry-After header when encountered.
Backoff on 429
When a 429 response is received clients must stop querying and sleep for at least the number of seconds specified in the Retry-After header before resuming.
Shared IP Awareness
Users behind a shared NAT or corporate proxy share the 55,000 req/hr quota with all other users at that IP. Consider running a local Ensembl database mirror for high-throughput institutional use.
Bulk Data via FTP
For large-scale data retrieval (full genome sequences, complete gene sets, VCF files) use the Ensembl FTP service rather than the REST API to avoid rate limit constraints.

Sources