Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Upcoming rate limiting changes to Statuspage REST API

Statuspage will soon be making changes to how rate limiting is implemented in our authenticated REST API. If you have an existing integration with our REST API, you may need to make updates to accommodate these changes, so please read on to understand the details.

What is changing

  1. Rate limit policy changes. Effective Sep 15, 2020, unpaginated GET requests to the page-access-users and components endpoints will be limited to 1 request per minute. Paginated requests to those endpoints will continue to be rate limited at the existing rate of 60 requests per minute.
  2. Rate limit response code change from 420 to 429. Effective Feb 15, 2021 when you exceed the Statuspage API rate limit, we’ll respond with HTTP status code 429 (Too Many Requests) instead of the current behavior of responding with a 420.
  3. Inclusion of Retry-After header in rate limit responses. Effective immediately, we’ll include a Retry-After HTTP header in 420 / 429 responses, e.g. Retry-After: 60 for unpaginated requests that exceed the rate limit.

What you need to do

You may need to update your integration to prepare for these changes:

  • We strongly recommend that you implement pagination for GET requests where possible, since the unpaginated rate limit will be much more restrictive.
  • If you've implemented rate-limiting handling that expects a 420 status code, you should update it to also accommodate a 429 response.
  • You should look for the Retry-After header and limit your requests accordingly.

If you have questions about these changes, please feel free to post a comment here, or contact our support team.

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Statuspage

New feature: Slack notifications for Statuspage

We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...

1,400 views 2 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you