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
{{ message }}
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.
Is your feature request related to a problem? Please describe.
The API offers X-RATE-Limit and X-RATE-Remaining, but no X-Rate-resetAt.
Describe the solution you'd like
The headers should include a X-Rate-ResetAt.
Describe alternatives you've considered
The value could be a unix timestamp or a zoned date time.
Additional context X-Rate-resetAt is very valuable in case someone is reaching the limit, but it also fully specifies the rate limit per period. Currently, the information on the rate limit is 1,000 / unknown time period.
The text was updated successfully, but these errors were encountered:
@Nosferican I think that's not a Code.gov thing. The rate limit is handled by https://api.data.gov/ as well as the api key. The response headers are added by them.
Thanks for the information. I found NREL/api-umbrella#377 (created on 2017-07-30) which had that request. On this end, maybe we should document that it uses the api.data.gov and a link to their docs.
Is your feature request related to a problem? Please describe.
The API offers
X-RATE-Limit
andX-RATE-Remaining
, but noX-Rate-resetAt
.Describe the solution you'd like
The headers should include a
X-Rate-ResetAt
.Describe alternatives you've considered
The value could be a unix timestamp or a zoned date time.
Additional context
X-Rate-resetAt
is very valuable in case someone is reaching the limit, but it also fully specifies the rate limit per period. Currently, the information on the rate limit is 1,000 / unknown time period.The text was updated successfully, but these errors were encountered: