> For the complete documentation index, see [llms.txt](https://developerdocs.instructure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developerdocs.instructure.com/services/dap/dap-cli-readme/dap-cli-reference/dap-cli-reference-list.md).

# dap list

List the namespaces and tables available for querying.

The `dap list` command group reports the namespaces the DAP API exposes, and the tables within a namespace. Use it to discover what to pass to `--namespace` and `--table` on the other commands.

```
dap list namespaces                      # all namespaces available for querying
dap list tables --namespace <namespace>   # all tables in one namespace
```

Both subcommands list everything the DAP API exposes. The output is not filtered by [table access](https://developerdocs.instructure.com/services/dap/dap-cli-readme/dap-cli-security.md#table-access): a name appearing here does not mean your key may read that table's data.

### Usage

```
dap [arguments] list COMMAND [flags]
```

## dap list namespaces

Lists the name of all namespaces available for querying.

### Options

**`-h, --help`**\
Displays help information for the command.

### Output

Namespace names are printed to `stdout`, one per line. There is no JSON output mode for this command.

```
canvas
canvas_logs
catalog
new_quizzes
```

### Examples

List every namespace:\
`$ dap list namespaces`

## dap list tables

Lists the name of all tables available for querying in the specified namespace.

### Options

**`--namespace <string>`**\
Specifies the data source (namespace). Use [`dap list namespaces`](#dap-list-namespaces) to see the available values.

**`-h, --help`**\
Displays help information for the command.

### Output

Table names are printed to `stdout`, one per line. There is no JSON output mode for this command.

```
access_tokens
accessibility_issues
account_users
accounts
...
```

### Examples

List tables from the `canvas` namespace:\
`$ dap list tables --namespace canvas`

List tables from the `catalog` namespace:\
`$ dap list tables --namespace catalog`

## Global options

**`--base-url <string>`**\
Base URL of the DAP API. Skip, if the `DAP_API_URL` environment variable is set.

**`--client-id <string>`**\
Client ID obtained from the Identity Service. Skip, if `DAP_CLIENT_ID` environment variable is set.

**`--client-secret <string>`**\
Client Secret obtained from the Identity Service. Skip, if `DAP_CLIENT_SECRET` environment variable is set.

## Scripting

For scripting, use `--non-interactive --loglevel warning` to suppress log lines from `stderr`:

```sh
dap --non-interactive --loglevel warning list tables --namespace canvas
```

## Error handling

| Scenario                               | Exit code | Error output                                                                                                    |
| -------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------- |
| Invalid namespace                      | 5         | `ERROR - The namespace '<name>' specified in the request is not valid.`                                         |
| Missing `--namespace` on `list tables` | 2         | `Error: Missing option '--namespace'.`                                                                          |
| Missing base URL                       | 5         | `ERROR - Missing DAP API base URL. Please provide the base URL of your regional API Gateway before proceeding.` |

### Related Resources

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Key Concepts</strong></td><td>Get familiar with the key concepts in DAP.</td><td><a href="https://developerdocs.instructure.com/services/dap/key-concepts.md">Key Concepts</a></td></tr><tr><td><strong>Rate Limits &#x26; Policies</strong></td><td>Learn more about the limits and our policies in DAP.</td><td><a href="https://developerdocs.instructure.com/services/dap/limits-policies.md">Rate Limits &amp; Policies</a></td></tr><tr><td><strong>Datasets</strong></td><td>Discover the available namespaces and tables.</td><td><a href="https://developerdocs.instructure.com/services/dap/dataset.md">Datasets</a></td></tr></tbody></table>


---

# 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://developerdocs.instructure.com/services/dap/dap-cli-readme/dap-cli-reference/dap-cli-reference-list.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.
