-
I have a few questions about the API that I'm hoping someone could answer.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Thanks for asking. A few replies:
Probably the easiest thing to do with that is convert it to an API request by changing the URL a bit. This has the same GET params but returns JSON instead of HTML: You could also tweak this to get back one result per case by changing it to
I'm sorry, I don't think that's really possible now. We don't make the FJC data searchable or filterable as far as I'm aware.
Well....if you have a list of cases, there's no surefire way to get their initial complaints, but they're usually document 1. So if you assume that, what I'd do is an API request for each of those documents. So if you have docket number That gets you:
In the response from this, you'll see:
Tack that onto storage.courtlistener.com, and you've got the download URL: https://storage.courtlistener.com/recap/gov.uscourts.dcd.178502/gov.uscourts.dcd.178502.1.0_48.pdf Great! But if you don't get back the filepath_local value, you'll want to buy the document. We don't provide a link to PACER for that, but we do have an API that you can use to buy it instead of doing it by hand. Search here for "Fetch" and you should see some good examples of using our Fetch API (it's documented too). Does that help |
Beta Was this translation helpful? Give feedback.
Thanks for asking. A few replies:
Probably the easiest thing to do with that is convert it to an API request by changing the URL a bit. This has the same GET params but returns JSON instead of HTML:
https://www.courtlistener.com/api/rest/v3/search/?q=&type=r&order_by=dateFiled%20desc&nature_of_suit=Prisoner%3APrison%20conditions&court=azd
You could also tweak this to get back one result per case by changing it to
type=d
(that only works on API results, I believe).