> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/api/rest-api/tables/get.md).

# get

Retrieve detailed information about a table and its export restrictions

## HTTP Request

```http
GET /tables/:tableReference
GET /workflows/:workflowReference/tables/:tableReference
```

## Path parameters

| Parameter         |                                                                                                                                                                                                                                                                                                                                               |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| tableReference    | A qualified reference to the table. See [referencing resources](/api/referencing-resources.md) for more information.                                                                                                                                                                                                                          |
| workflowReference | A qualified reference to a workflow. When provided, `tableReference` may be the table's name (and optional reference id) alone, and can refer to any table in the workflow, including tables from the workflow's datasources. See [referencing tables within a workflow](/api/referencing-resources.md#referencing-tables-within-a-workflow). |

{% hint style="info" %}
This endpoint extends the [general API structure](/api/rest-api/general-structure.md).
{% endhint %}

## Authorization

Overview access to the table is required. If a table's overview is not public, your access token must have one of the following scopes:

* data.overview
* data.metadata
* data.data
* data.edit

When using the workflow form, you must also have read access to the workflow.

[Learn more about authorization.](/api/rest-api/authorization.md)

## Request body

The request body must be empty.

## Response body

Returns a JSON representation of a [table resource](/api/resource-definitions/table.md).

{% hint style="info" %}
The table's `uri` and `qualifiedReference` always reflect where the table actually lives. For a table from one of the workflow's datasources, this is the dataset (or workflow) that the table belongs to.
{% endhint %}

## Examples

{% tabs %}
{% tab title="curl" %}

```bash
# Get the table "Ozone (O3)" from the EPA Air Quality dataset 
# from the StanfordPHS organization
curl -H "Authorization: Bearer $REDIVIS_ACCESS_TOKEN" \
"https://redivis.com/api/v1/tables/stanfordphs.epa_air_quality.ozone_O3"
```

{% endtab %}

{% tab title="curl (within a workflow)" %}

```bash
# Get the "daily_observations" table, which comes from a dataset
# that has been added as a datasource to the workflow
curl -H "Authorization: Bearer $REDIVIS_ACCESS_TOKEN" \
"https://redivis.com/api/v1/workflows/imathews.example_workflow_climate_analysis/tables/daily_observations"
```

{% endtab %}
{% endtabs %}


---

# 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.redivis.com/api/rest-api/tables/get.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.