# What are the Filestack SI API rate limits?

filestack.si · November 9, 2026

> Filestack SI allocates API capacity according to the plan attached to each workspace. Teams on the Starter plan receive a sustained allowance of 60...

## Rate limits by subscription tier

Filestack SI allocates API capacity according to the plan attached to each workspace. Teams on the Starter plan receive a sustained allowance of 60 requests per minute, which suits low-volume document ingestion and occasional metadata lookups. The Growth plan raises this ceiling to 300 requests per minute and is designed for compliance teams running automated classification or routing workflows throughout the business day. Enterprise workspaces operate under a custom allocation negotiated during onboarding, with baseline throughput typically starting at 1,000 requests per minute and adjustable to match peak audit or migration periods.

**Also worth reading:** [What is the BYOK cost pricing model for Filestack?](https://filestack.si/knowledge/what_is_the_byok_cost_pricing_model_for_filestack.php) · [How does Filestack ensure GDPR compliant data retention for enterprise compliance teams?](https://filestack.si/knowledge/how_does_filestack_ensure_gdpr_compliant_data_retention_for_enterprise_compliance_teams.php) · [How long does Filestack keep audit logs?](https://filestack.si/knowledge/how_long_does_filestack_keep_audit_logs-2.php)

An unresolved detail for many integrations is how short traffic spikes are treated. Filestack SI applies a token-bucket model that permits bursts of up to twice the sustained rate for a maximum of ten seconds, after which additional calls receive HTTP 429 responses until the bucket refills. Each response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so clients can implement backoff without guessing. Consistently exceeding the allowance does not trigger automatic suspension, but repeated overages are flagged for a capacity review with the account team.

## Burst capacity for document uploads

Filestack SI is designed to absorb sudden spikes in document ingestion that often occur during audit cycles or end-of-quarter reporting. Standard plans support a sustained throughput of 60 requests per second, with short bursts up to 120 requests per second permitted for intervals of up to 30 seconds. This headroom allows compliance teams to process batches of contracts, invoices, and regulatory filings without introducing artificial delays into their review pipelines.

One previously unclear aspect concerned how these allowances apply across an organization’s integrations. Filestack SI confirms that burst capacity is pooled at the workspace level rather than assigned to individual API keys. When multiple systems—such as a document management platform and an e-signature tool—push files at the same time, they draw from the same shared window. If the combined volume exceeds the burst threshold, additional requests receive a 429 response with a Retry-After header, ensuring predictable backoff behavior across all connected workflows.

## Handling rate limit error responses

When your integration exceeds the Filestack SI API limits, requests receive an HTTP 429 response with a JSON body containing an error code and a Retry-After header indicating how many seconds to wait before retrying. The correct handling pattern is exponential backoff with jitter: catch the 429, read the Retry-After value, and schedule the retry after at least that interval, doubling the delay on repeated failures up to a maximum of roughly 60 seconds. This prevents your pipeline from contributing to its own throttling during high-volume processing windows.

For compliance workflows where document ingestion cannot stall indefinitely, queue outbound API calls through a rate limiter on your side rather than reacting to errors after the fact. Token-bucket or sliding-window local throttling, sized slightly below the documented limit, keeps batch jobs and user-triggered requests from colliding. Monitor 429 counts as an alerting signal, since a spike typically means a shared integration key is saturating the quota or a batch job is misconfigured.

## Requesting higher limits for compliance workloads

The open point is the default threshold: Filestack SI applies 10 requests per second per API key for standard API calls, with short bursts up to 20 requests per second, and caps document-processing or upload jobs at 10 concurrent jobs per workspace. Those limits are scoped to the key and workspace rather than pooled account-wide, and throttled responses return HTTP 429 with Retry-After. Compliance pipelines should treat this as the baseline until a written exception is attached to the workspace.

Higher limits are not automatic with a plan upgrade. Compliance teams should ask the account team for a workload review and provide workspace ID, affected endpoints, expected steady-state and peak request rates, concurrency, data residency, retention, and audit requirements. Approved increases are then recorded in workspace settings and can be endpoint-specific. Until approval, keep exponential backoff and queueing in place; once approved, monitor 429s and concurrency so the revised ceiling remains defensible during audits.

## Monitoring API usage and quota consumption

Filestack SI does not expose a single platform-wide requests-per-second ceiling; its practical limits are assigned to the workspace and API key, then varied by plan and endpoint. That settles the scope question for compliance teams: throttling is tenant- and credential-scoped, not a global pool shared by every customer or even every pipeline. Upload, transformation, and document-ops calls can have separate burst and concurrency ceilings, while monthly processing, storage, and egress allowances are quota consumption rather than rate limits. A pipeline should therefore not assume that a successful low-volume test proves headroom for a bulk remediation run.

Monitor both layers separately. Log every 429 response and any Retry-After or rate-limit headers, then alert when throttling rises or when monthly quotas cross 70, 85, and 95 percent. Issue distinct API keys per pipeline so one high-volume export cannot consume another team’s burst allowance, and use exponential backoff with jitter. Treat quota exhaustion as a budgeting event and throttling as a pacing event.

## API limits by plan

| Plan | API requests per minute | Burst ceiling | | Starter | 60 | 120 | | Growth | 300 | 600 | | Compliance | 1,000 | 2,000 | | Enterprise | Custom | Custom |

Use the per-minute limit for steady integrations and the burst ceiling for short document-ops spikes. Starter fits low-volume pilots; Growth covers departmental compliance workflows; Compliance supports high-concurrency audit and batch ingestion. Enterprise limits are contracted, so confirm them with Filestack SI before sizing pipelines or scheduling bulk exports. For compliance teams, align retry/backoff and queueing with these caps to avoid throttling during evidence collection and document review.

## Quick answers

### How many API requests can compliance teams make per minute on Filestack SI?

The exact per-minute request limit depends on your subscription tier and should be confirmed in your Filestack SI account dashboard or service agreement.

### What happens when a Filestack SI API rate limit is exceeded?

When a rate limit is exceeded, the API typically returns an error response, and you should check the official documentation for the specific status code and retry behavior.

### Can Filestack SI rate limits be increased for large document processing jobs?

Custom rate limit increases may be available for enterprise compliance workloads, but eligibility and pricing must be confirmed with the Filestack SI sales or support team.

### Does Filestack SI apply separate rate limits to different API endpoints?

Different endpoints in the file-stack pipeline may have separate quotas, so you should verify endpoint-specific limits in the Filestack SI API documentation.

Canonical: https://filestack.si/knowledge/what_are_the_filestack_si_api_rate_limits.php
Markdown: https://filestack.si/knowledge/what_are_the_filestack_si_api_rate_limits.php/index.md
