SOFTWARERADAR — AIRTABLE API PLANNING EXAMPLE

Guide: https://softwareradar.co.uk/guides/airtable-api-limits-pricing/
Reviewed 16 October 2026. All workload numbers are fictional. No Airtable account, base, token, API request, integration, record update or purchase was operated. These are editorial planning files, not API payloads or native exports.

One complete list operation returns a stable set of 230 records in pages of 100, 100 and 30: three read requests. Twelve distinct existing records are then updated in batches of 10 and 2: two update requests. Five requests per run, twelve runs per active day and 22 active days give 264 runs and 1,320 workflow calls. Another 100 calls across the same workspace give 1,420 planned calls. The other-call row has no known record count, so that field is blank. An empty attempted list operation still uses one request. Actual pagination follows the returned offset.

With individual updates, three reads plus twelve updates make 15 calls per run: 3,960 workflow calls plus 100 other calls = 4,060. With batches of ten and eight runs per day over 22 active days, the forecast is 980 including 100 other calls, leaving 20 within the Free allowance. Zero runs or zero active days leaves only the other workspace calls. These alternatives are calculated plans, not observed savings or a recommendation to lower required freshness. The ledger records only the default batched example.

Free includes 1,000 calls per workspace per month; Team includes 100,000. Business and Enterprise Scale have no monthly call cap in the reviewed documents. Free's one-time grace and subsequent blocking differ from Team's slower processing at two requests per second after its allowance. The calculator has no live counter, grace state or current throttle information. A positive monthly balance does not establish that bursts comply with five requests per second per base or the 50 requests per second token-owner traffic limit.

The calculator assumes one complete list operation per run with pages of up to 100 and optional existing-record updates, in batches of up to ten or individual requests. It excludes retries and unlisted requests. Add a full-month estimate of other workspace calls, rather than mixing the forecast with an allowance remaining today. Record/storage capacity, permissions, automation limits, subscriptions, connector fees and request scheduling are separate checks. Calculations run locally; no token is requested or sent.

integration-review.csv supplies six proposed checks. Actual workspace/plan, actual usage, observed result, evidence, reviewer and decision are blank. Map the assumptions to the actual authorised environment and retained plan.