Variable response times

The API depends on the Airtable API, which can exhibit significant latency with large variation. We believe this is likely caused by cold starts on Airtable’s side, though this has not been fully confirmed.

• Mutation requests typically complete within 500–1000 ms, but in rare cases may take up to 20 seconds.

• Schema requests involve database introspection and usually take 3–8 seconds on the first request.

For read-only fetch requests, the API applies a caching layer. After the initial request, subsequent calls are significantly faster.

Recommended timeouts
We strongly recommend configuring client-side timeouts of at least 15 seconds, and preferably higher, to prevent premature request failures caused by upstream latency.

Improving response time consistency is a core focus for the next major API release.

Need help?

If you encounter issues or unexpected behavior, feel free to get in touch. We are happy to help troubleshoot and assist with your integration.