> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/courtlistener.md).

# CourtListener

Search United States case law and judges, inspect dockets and oral arguments, and resolve legal citations with CourtListener.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector     | Authentication |
| ------------- | -------------- |
| CourtListener | API Token      |

#### CourtListener

Connect to CourtListener to search case law and judges, inspect dockets and oral arguments, and resolve legal citations.

**Set up in CourtListener**

1. Prepare the CourtListener account or service that the workflow will access. Grant access to the required resources and operations.
2. **API Token:** Your CourtListener API token. Create or copy it from your CourtListener profile, then paste it here.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **CourtListener**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                         |
| ------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API Token     | Yes      | Your CourtListener API token. Create or copy it from your CourtListener profile, then paste it here. [Provider instructions](https://www.courtlistener.com/profile/). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **CourtListener** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Search Case Law Opinions

Search United States case-law opinions in CourtListener.

**Inputs**

| Field                        | Type     | Required | Description                                                                  |
| ---------------------------- | -------- | -------- | ---------------------------------------------------------------------------- |
| Search query                 | textarea | Yes      | Words, phrases, or legal concepts to search in case law.                     |
| Semantic search              | boolean  | No       | Match legal meaning rather than only exact keywords. Default: false.         |
| Include unpublished opinions | boolean  | No       | Include unpublished opinions in addition to published cases. Default: false. |
| Page cursor                  | string   | No       | Cursor returned by a previous case-law search.                               |

**Outputs**

| Field       | Type          | Description                                   |
| ----------- | ------------- | --------------------------------------------- |
| Opinions    | object\_array | Matching case-law opinion clusters.           |
| Next cursor | string        | Pass this cursor back to fetch the next page. |

#### Get Docket Details

Get detailed metadata for a CourtListener docket.

**Inputs**

| Field     | Type    | Required | Description                        |
| --------- | ------- | -------- | ---------------------------------- |
| Docket ID | integer | Yes      | CourtListener's numeric docket ID. |

**Outputs**

| Field  | Type   | Description                        |
| ------ | ------ | ---------------------------------- |
| Docket | object | The matching CourtListener docket. |

#### List Oral Arguments

List CourtListener oral-argument recordings.

**Inputs**

| Field               | Type    | Required | Description                                                             |
| ------------------- | ------- | -------- | ----------------------------------------------------------------------- |
| Docket ID           | integer | No       | Only return recordings linked to this CourtListener docket.             |
| Processing complete | boolean | No       | Return completed or incomplete audio-processing records. Default: true. |
| Page cursor         | string  | No       | Cursor returned by a previous oral-argument list call.                  |

**Outputs**

| Field          | Type          | Description                                      |
| -------------- | ------------- | ------------------------------------------------ |
| Oral arguments | object\_array | Matching CourtListener oral-argument recordings. |
| Next cursor    | string        | Pass this cursor back to fetch the next page.    |

#### Search Judges

Search CourtListener judge records by name or keywords.

**Inputs**

| Field        | Type     | Required | Description                                                    |
| ------------ | -------- | -------- | -------------------------------------------------------------- |
| Search query | textarea | Yes      | Name or keywords to search across CourtListener judge records. |
| Page cursor  | string   | No       | Cursor returned by a previous judge search.                    |

**Outputs**

| Field       | Type          | Description                                   |
| ----------- | ------------- | --------------------------------------------- |
| Judges      | object\_array | Matching CourtListener judge records.         |
| Next cursor | string        | Pass this cursor back to fetch the next page. |

#### Look Up Citations

Find and resolve case-law citations in a block of text.

**Inputs**

| Field               | Type     | Required | Description                                     |
| ------------------- | -------- | -------- | ----------------------------------------------- |
| Text with citations | textarea | Yes      | Text containing one or more case-law citations. |

**Outputs**

| Field          | Type          | Description                                           |
| -------------- | ------------- | ----------------------------------------------------- |
| Citations      | object\_array | Every citation found, its status, and matching cases. |
| Citation count | integer       | Number of citation occurrences found in the input.    |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/courtlistener.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
