API throttles and limits - 60/minute and 250/request

[jafrank88]

If the citation-lookup API has these two limits,

The performance of this API is affected by the number of citations it has to look up. Therefore, it is throttled to 60 valid citations per minute. If you are below this throttle, you will be able to send a request to the API. If a request pushes you beyond this throttle, further requests will be denied. When your request is denied, the API will respond with a 429 HTTP code and a JSON object. The JSON object will contain a wait_util key that uses an ISO-8601 datetime to indicate when you will be able to make your next request.

The API will look up at most 250 citations in any single request. Any citations past that point will be parsed, but not matched to the CourtListener database. The status key of such citations will be 429, indicating “Too many citations requested.” See examples below for details. https://www.courtlistener.com/help/api/rest/citation-lookup/

When will the 250 limit be reached when the 60 won't be? If I have 300 citations to check what is the best way to structure my calls to take the least amount of time possible?

[mlissner]

When will the 250 limit be reached when the 60 won't be?

That's a good question. These two throttles are independent, so I think you're right that the 250 wouldn't be hit unless the 60 limit is elevated for you to a number higher than 250.

If I have 300 citations to check what is the best way to structure my calls to take the least amount of time possible?

You'll want to check them 60 at a time via one call per minute.

[jafrank88]

I don't have the full picture of server usage, but could the limit be raised to 250 citations per five-minute period and per request? That way the server would not be hit more, but the results could be returned faster. I understand a 300 citation document would have to be split, but it already has to be under the current approach.

[mlissner]

I just gave yours a bump. Give it 5-10 minutes to propogate.