This rate limit is in addition to our published API rate limits (200 RPM - this limit is not changing), which currently only rate limits REST API requests from third party clients. We expect to complete the rollout by end of day.
This rate limit effectively introduces a rate limit for apps as a protection against situations of heavy API usage to ensure quality of service for all customers . As such, accounts should only encounter this API rate limit in abnormal circumstances.
Expected behavior when an account reaches this rate limit:
When an account reaches the account-wide rate limit, the API will return an HTTP 429 response with a Retry-After header. Requests via the app framework will now transparently honor this Retry-After header on behalf of affected apps. Furthermore, the framework will emit a .delayed event that developers can use to customize a message for app users if the app encounters a rate limit. There is currently no limit to number of retries via the app framework.
As is the case today, third party API clients are expected to honor the Retry-After header .
We apologize for the late notice, we're here to help ease this transition so if you have any questions email firstname.lastname@example.org and we would be glad to help.