File tree Expand file tree Collapse file tree 1 file changed +4
-2
lines changed Expand file tree Collapse file tree 1 file changed +4
-2
lines changed Original file line number Diff line number Diff line change @@ -84,7 +84,7 @@ first second and then get one call back every second. With
84
84
``api_calls_per_interval = 60`` and ``api_interval_in_sec = 3600`` (1
85
85
hour) they can use all 60 calls in the first second and they get one
86
86
additional call every 10 seconds. ``api_calls_per_interval`` is the
87
- burst rate that you are willing to allow within `api_interval_in_sec``
87
+ burst rate that you are willing to allow within `` api_interval_in_sec``
88
88
seconds. The average rate of use is the ratio of
89
89
``api_calls_per_interval/api_interval_in_sec``. So you can have many
90
90
values that permit one call per second on average: 1/1, 60/60,
@@ -134,7 +134,9 @@ Also if the user has exceeded the rate limit, this header is added:
134
134
135
135
If the client has requested a deprecated API endpoint, the header:
136
136
137
- **Sunset**: an http date after which the end point will not be available.
137
+ **Sunset**: an http date after which the end point will not be
138
+ available. This is not returned by current code, but can be used
139
+ when `Programming the REST API`_.
138
140
139
141
will be returned. It should be used as a hint that the REST endpoint
140
142
will be going away. See https://tools.ietf.org/html/rfc8594 for
You can’t perform that action at this time.
0 commit comments