uses RFC3339 which is fine but different from Retry-After, nice thing uses another header name
non clock-skew safe
Can be implemented with this spec? Yes, eg:
RateLimit-Limit: 5000
RateLimit-Policy: 5000; w=86400 # expliciting daily window in the optional comment part
RateLimit-Remaining: 4999
RateLimit-Reset: 36000 # 10 hours before reset time
Amazon
Amazon uses custom headers with x-mws-quota-resetsOn using the IMF-fixdate syntax.
The time-window is hourly.
Compliant implementations: Zalando, IBM, 3scale, Kong, Dutch government, pipedrive, Envoy
Explicit support via
RateLimit-*
orX-RateLimit-*
from:WIP in
Support via configuration from:
Uses 429 and the triple like the following
Can be implemented? Yes
Google
Returns 429 or 403 depending on the API.
Yelp
Returns 429
Considerations:
Yelp-
see https://tools.ietf.org/html/rfc6648Can be implemented with this spec? Yes, eg:
Amazon
Amazon uses custom headers with
x-mws-quota-resetsOn
using theIMF-fixdate
syntax. Thetime-window
is hourly.Can be implemented with this spec? Yes, switching to
delta-seconds
eg:Github
Uses 429 and the triple like the following
considerations:
Can be implemented with this spec? Yes, but should change the x-ratelimit-reset semantic
twitter, axway, oracle
Uses 429 and the triple like the following (same as github, but with different names)
mulesoft
https://docs.mulesoft.com/api-manager/2.x/rate-limiting-and-throttling-sla-based-policies
Uses delta-seconds with milliseconds
Other implementers