Question about API Rate Limit

[ta-aoki]

I have read this article, and I have two questions.
https://support.tulip.co/docs/rate-limiting

1. Your recommendation was this
   Best practices for high performance apps
   
   
   
   Are you changing the recommended “50 reads per second” limit to “50 seconds per read” ?
2. We are using API heavily, so we would like to know whether our current usage is exceeding this limit or not. Can you please provide us the the page where we can see API token/Table ID which is exceeding the limit?

[pete]

Hi @ta-aoki - Thanks for reaching out. To clarify:

1. This was a typo and the doc has been updated. It should be ‘per second’.
2. If you are approaching or exceeding the limits you will see a basic warning message for each table. There will also be a grace period of at least 30 days before rate limiting is strictly enforced to allow for adjustments if necessary. In the meantime we can also provide your specific usage; please send me (peter@tulip.co) the Tulip instance(s) that you are using and we can provide more info.

[ta-aoki]

@pete

If you are approaching or exceeding the limits you will see a basic warning message for each table.

Where and how is it actually shown?

Can you give me a sample screenshot?

[ta-aoki]

@pete

This was a typo and the doc has been updated. It should be ‘per second’.

Thank you for the fix!

I still see small difference between the two articles for the record read.

Rate limiting

https://support.tulip.co/docs/best-practices-for-high-performance-apps-1#highfrequency-usage-of-tulip-table-apis

Which is correct?

[pete]

@ta-aoki it should read ‘per table’, we will update that article as well.