Stride API Rate Limiting in Place



Stride API Rate Limiting

Today we launched rate limiting for the Stride API. API calls are limited to 100 calls a minute per conversation for an app.

When your calls are being rate limited you will receive a 429 HTTP response code.


HTTP/1.1 429
Content-Type: application/json
Strict-Transport-Security: max-age=315360000; includeSubDomains; preload
Date: Fri, 08 Jun 2018 17:36:21 GMT
X-RateLimit-Limit: 100
X-RateLimit-Reset: 2018-06-08T17:36:32Z
X-Application-Context: Stargate:prod,prod-east:8080
X-XSS-Protection: 1; mode=block
transfer-encoding: chunked
X-Content-Type-Options: nosniff
Connection: keep-alive
X-Frame-Options: SameOrigin
X-RateLimit-Remaining: 0

{"code":429,"message":"request has been rate limited"}

A very important header to pay attention to is X-RateLimit-Reset. It can inform your app about when it can retry API calls again for that conversation. After that Date and Time, your app will then have another 100 API calls it can send to the API for that conversation.

This rate limiting ensures our ability to provide a reliable service for all your end users. This should not affect the vast majority of our current API usage we’re seeing today.

Stride API change log / known issues