We are considering using Coda as a key part of our workflow, but we’re concerned about the API rate limits. As our project scales, we anticipate needing higher API limits to ensure smooth integration and automation.
Is there any plan to introduce higher rate limits for paid users in the future? (We are not there yet but might be in a future so we would like to be prepared).
We really like Coda’s flexibility, but we want to be sure the API limits won’t become a bottleneck as we grow. Looking forward to your insights!
Hi @Gal_Mrvar - Unfortunately we don’t offer different tiers of rate limits currently, although I think it’s worth considering. Can you talk more about your workflow, and what rate limits you think you may run into?
At the moment, everything is working well for us, and we can manage the API limits by adding a cooldown if needed. However, just to provide more context:
We are building an API endpoint where registered users on our platform can add, edit, and read data from a Coda table. Our plan is to use a single API key to interact with a central Coda table, while managing views and other manipulations within the Coda doc itself.
Currently, we are in a testing phase, so this was just an informative question. However, we want to be prepared for a potential increase in users. Speed is slightly important in our case, and if API cooldowns become necessary, it could be frustrating for our users.
We appreciate your response and we will take this into account as we continue developing our API.
Thanks for the additional context @Gal_Mrvar. Generally speaking Coda isn’t designed to be an application backend, and the rate limits reflect that. While it may suffice for a POC or small internal app, I wouldn’t recommend launching a customer-facing application that relies on a Coda doc as a backend. I wrote an article about using Google Sheets as a database and I think almost all the points apply to Coda as well: