You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fern/docs/pages/rate-limits.mdx
+16Lines changed: 16 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,22 @@ Retry-After: 30
11
11
12
12
The `Retry-After` response header can be used to determine the number of seconds left before the user’s rate limit window expires.
13
13
14
+
The user’s current rate limit quota and usage can be inspected in a request’s response headers:
15
+
16
+
| Header | Description |
17
+
| :--- | :--- |
18
+
| X-Ratelimit-Limit | The user’s total rate limit units for the current window. |
19
+
| X-Ratelimit-Remaining | The user’s remaining rate limit units for the current window. |
20
+
| X-Ratelimit-Reset | The time at which the rate limit window resets, in seconds from the Unix epoch. |
21
+
22
+
The following provides an example of response header values:
23
+
24
+
```
25
+
X-Ratelimit-Limit: 1000
26
+
X-Ratelimit-Remaining: 900
27
+
X-Ratelimit-Reset: 1720636800
28
+
```
29
+
14
30
<Calloutintent="info">
15
31
All APIs have the same weight when applying rate limiting, and there is no preference given to any individual API. However, this is subject to change in the future.
0 commit comments