Thank you very much for the clarification! It would be great if the documentation could be updated soon then, as we’ve been using this for reference the entire time during development. (Also, I see this page also states the asynchronous endpoint uses the write rate limit: https://dev.twitter.com/ads/analytics#RateLimiting (which should be 300 requests / 1 minute) ).
So this rate limit of 250 requests / 15 minutes is both for the synchronous and asynchronous endpoints?
We’re currently in development phase and making sure to use the asynchronous endpoint as much as possible. During this we continuously use and test the API like one of our users would (and would be able to), but we’re noticing we’re running into the rate limit during development already. So, we will need to contact our API program contact about this, because I definitely expect this would become an issue when our users start using it. Perhaps you know, if we contact our API program contact, what would be a rate limit increase we could expect? That way we can take this into account with further development while we await response.