Skip to main content
U.S. flag

An official website of the United States government

Legacy PACER Case Locator to Retire February 13, 2022

December 20, 2021

The legacy PCL will be retired on February 13, 2022. After that date, you will be redirected to the updated PACER Case Locator.

If you use automated scripts to scrape data from the legacy PCL, consider transitioning to the new PCL application programming interface (API), available on the Developer Resources page. The API simplifies the use of automated scripts to consume data from the PCL. For more information on the PCL API, check out the PCL API User Guide and the Q&A from the PCL API Town Hall.

Test Your Scripts

You can test the PCL API in the QA environment* at https://qa-pacer.uscourts.gov/. You may also test your scripts in QA as part of your development lifecycle process, or as needed. You must have a PACER account to use QA. To register for a PACER test account, visit https://qa-pacer.psc.uscourts.gov/pscof/registration.jsf. There is no charge for QA searches, so you may skip the credit card portion of the registration. Your QA account will be activated overnight.

*NOTE: QA is a testing site that may occasionally be unavailable due to maintenance. Also, there may be features in testing that are not currently available in the Production environment.

Reminders:

  • Please remember to limit large pulls to non-business hours (6 p.m.–6 a.m. Central Time). This will minimize slow system performance for all users.
  • PCL data is updated nightly.

How do I establish a federal government Interagency Agreement (IAA) for PACER Use?

Was this helpful?

Federal government agencies that wish to enter into an IAA for the use of PACER and payment of PACER fees incurred by its users should submit a 7600A Form and a 7600B Form to the PACER Service Center.  Agencies should contact the PACER Service Center to obtain forms prefilled with the required information.  

Update Automated Authentication Requests by 11/21/21

November 2, 2021

Automated script users who have written authentication requests to automatically log in to PACER and/or CM/ECF must update these requests to meet the new technical specifications and security requirements outlined in the PACER Authentication API User Guide by November 21, 2021. These requests will fail after that date.

On September 19, the PACER authentication application programming interface (API) was released. The API simplifies the use of automated scripts to access PACER and implement new security measures.

Test Your Scripts

To ensure your process works using the new PACER authentication API, test them in the QA environment* at https://qa-login.uscourts.gov/services/cso-auth. You must have a PACER account to use QA. To register for a PACER test account, visit https://qa-pacer.psc.uscourts.gov/pscof/registration.jsf. There is no charge for QA searches, so you may skip the credit card portion of the registration. Your QA account will be activated overnight.

*NOTE: QA is a testing site that may occasionally be unavailable due to maintenance. Also, there may be features in testing that are not currently available in the production environment.

Reminder: Limit large data pulls to non-peak hours

May 10, 2021

PACER users who run data scraping scripts are reminded to conduct large data pulls between 6 p.m. and 6 a.m. Central Time only. Adhering to this schedule will help minimize slow system performance for all users, a problem that has recently been reported in several courts. In order to facilitate continuous access for all PACER users, a court may suspend or reduce PACER access for a user causing operational disruption.

PACER Service Center Interruption

February 16, 2021

The PACER Service Center is operating with reduced staffing through Friday, Feb. 19 due to power outages and Internet connection issues relating to the winter storm in Texas. Hold times will be longer than normal. Use pacer.uscourts.gov to manage your account. You can make a payment, update address information, obtain billing and usage information, and many other actions pertaining to your account.

We apologize for any inconvenience this may cause.

Subscribe to