Teable · Rate Limits

Teable Rate Limits

Teable's REST API is governed primarily by plan-based resource quotas (rows, automation runs, attachment storage, AI credits) rather than published per-endpoint request-rate ceilings. Record list requests cap page size at take=1000 and use skip-based pagination. Self-hosted Community Edition deployments are bounded by the operator's own Postgres and infrastructure capacity. Specific per-account request-rate values are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring records, rows, runs, storage, and credits.

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

Tagged areas include No-Code, Database, Airtable Alternative, Postgres, and Open Source.

5 Limits Throttle: 429
No-CodeDatabaseAirtable AlternativePostgresOpen SourceRate LimitingQuotasThrottling

Limits

Record Page Size (take) request
records
1000
Maximum records returned per list call; paginate with skip.
Rows Quota account
rows
plan-based (1,000 Free / 250,000 Pro / 1,000,000 Business)
Total rows allowed across the account by cloud tier; unbounded by license for self-host.
Automation Runs account
runs
plan-based (100 Free / 25,000 Pro / 100,000 Business)
Monthly automation executions by cloud tier.
Attachment Storage account
storage
plan-based (1 GB Free / 10 GB Pro / 100 GB Business)
Total attachment storage by cloud tier.
AI Credits account
credits
plan-based (500 Free / 1,000 Pro / 2,000 Business per seat)
Credits consumed by AI chat, AI field, and related features.

Policies

Quota-Based Limits
API throughput is governed by plan quotas (rows, runs, storage, credits) rather than fixed RPM ceilings.
Self-Host Capacity
Self-hosted Community Edition has no license-imposed limits; capacity is set by your Postgres and host resources.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any 429 / Retry-After responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/teable-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.