specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Coda
providerId: coda
created: '2026-05-08'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-08, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-08'
reconciled: true
tags:
- Productivity
- Docs
- No-Code
- Collaboration
- Database
- Rate Limiting
- Quotas
- Throttling
description: Coda enforces per-API-token rate limits and returns 429 responses with a
  Retry-After header when the limit is exceeded. Limits scale with plan tier; mutation
  endpoints (row inserts, updates) are rate-limited more strictly than read endpoints.
notes: Coda recommends batching row writes (push multiple rows per request) and respecting
  the Retry-After header. Mutations are processed asynchronously and can be tracked via
  the mutation status endpoint.
sources:
- https://coda.io/developers/apis/v1
responseCodes:
  throttled: 429
limits:
- name: Read Requests
  scope: api_token
  metric: request
  limit: published per-account
  timeFrame: per-minute
  notes: Read endpoints (list, get) have a higher per-token request rate than writes.
- name: Mutation Requests
  scope: api_token
  metric: request
  limit: published per-account
  timeFrame: per-minute
  notes: Row inserts/updates/deletes and other mutations are rate-limited more strictly.
- name: Mutation Status Polling
  scope: api_token
  metric: request
  limit: published per-account
  timeFrame: per-minute
  notes: Use the asynchronous mutation status endpoint instead of tight polling loops.
policies:
- name: Backoff Strategy
  description: Clients should implement exponential backoff with jitter and honor the
    Retry-After response header on 429.
- name: Batch Mutations
  description: Insert/update many rows in a single request rather than one row per request.
- name: Async Mutations
  description: Mutation endpoints return a request ID; poll the mutation status endpoint
    until completion instead of immediately re-reading.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com