[FIG(quote)[
[FIGCAPTION[
[1] [CITE[Rate Limits]]
([TIME[2015-03-05 17:38:04 +09:00]] 版)
<https://developer.foursquare.com/overview/ratelimits>
]FIGCAPTION]

> Generally rate limits follow the rules above; however, some endpoints may have different limits due to security or other considerations. For the most current and accurate rate limit usage information for a particular request type, inspect the X-RateLimit-Remaining and  X-RateLimit-Limit HTTP headers of API responses.

]FIG]


[FIG(quote)[
[FIGCAPTION[
[2] [CITE[Mattermost API Reference]]
([TIME[2016-12-07 08:34:06 +09:00]])
<https://api.mattermost.com/#tag/rate-limiting>
]FIGCAPTION]

> X-Ratelimit-Limit	The maximum number of requests you can make per second.
> X-Ratelimit-Remaining	The number of requests remaining in the current window.
> X-Ratelimit-Reset	The remaining UTC epoch seconds before the rate limit resets.

]FIG]


[FIG(quote)[
[FIGCAPTION[
[8] [CITE@en[Uber API Reference Guide]]
([TIME[2015-09-25 03:53:01 +09:00]] 版)
<https://developer.uber.com/v1/api-reference/>
]FIGCAPTION]

> Furthermore, we will supply X-Rate-Limit-* headers for all requests containing the current state of the secret token’s rate limit.
> Header	Description
> X-Rate-Limit-Limit	Total number of requests possible.
> X-Rate-Limit-Remaining	Number of requests left in the rate limit window.
> X-Rate-Limit-Reset	Timestamp when the rate limit will reset.

]FIG]



[FIG(quote)[
[FIGCAPTION[
[20] [CITE@en[GitHub API v3 | GitHub Developer Guide]]
([TIME[2017-06-10 05:53:45 +09:00]])
<https://developer.github.com/v3/#rate-limiting>
]FIGCAPTION]

> X-RateLimit-Limit	The maximum number of requests you're permitted to make per hour.
> X-RateLimit-Remaining	The number of requests remaining in the current rate limit window.
> X-RateLimit-Reset	The time at which the current rate limit window resets in UTC epoch seconds.

]FIG]


[FIG(quote)[
[FIGCAPTION[
[24] [CITE[Rate Limits]]
([TIME[2015-03-05 17:37:30 +09:00]] 版)
<https://developer.foursquare.com/overview/ratelimits>
]FIGCAPTION]

> Generally rate limits follow the rules above; however, some endpoints may have different limits due to security or other considerations. For the most current and accurate rate limit usage information for a particular request type, inspect the X-RateLimit-Remaining and  X-RateLimit-Limit HTTP headers of API responses.

]FIG]


[26] [CITE[W3C API Overview]], [TIME[2022-09-21T14:37:51.000Z]], [TIME[2023-04-17T04:58:34.639Z]] <https://w3c.github.io/w3c-api/>

>
[PRE(HTTP code)[
X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4524
X-RateLimit-Reset: 1439472737
]PRE]




[3] 関連: [CODE[429]]

[4] [CITE[Discord Developer Portal — Documentation — Rate Limits]], [TIME[2023-05-31T22:18:22.000Z]], [TIME[2023-06-01T05:13:54.492Z]] <https://discord.com/developers/docs/topics/rate-limits>

>
[PRE(HTTP code)[
X-RateLimit-Limit: 5
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1470173023
X-RateLimit-Reset-After: 1
X-RateLimit-Bucket: abcd1234
]PRE]

- [CODE[X-RateLimit-Global:]]
- [CODE[X-RateLimit-Scope:]]

[FIG(quote)[
[FIGCAPTION[
[5] [CITE[W3C API Overview]]
([TIME[2015-11-23 22:46:59 +09:00]] 版)
<https://w3c.github.io/w3c-api/>
]FIGCAPTION]

> You can check the status of a key in response headers after any request:
> X-RateLimit-Limit: 5000
> X-RateLimit-Remaining: 4524
> X-RateLimit-Reset: 1439472737

]FIG]