---
title: "Dataset Options"
method: GET
path: "/api/v1/integrations/{provider}/dataset-options"
tags: ["integrations"]
---

# Dataset Options

`GET /api/v1/integrations/{provider}/dataset-options`

## Request

- Base URL: `https://api.aws.cognee.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.aws.cognee.ai/api/v1/integrations/{provider}/dataset-options`
- Auth: API key in header `X-Api-Key`

Datasets this connection could be pointed at instead of its default (CLO-1014).

Owner-only (finding #3) — the same bar ``POST .../connection/dataset``
already gates on, not merely member-visible: this list is exactly
what that write accepts, and a member who could list it but not
choose from it learns nothing a stricter gate wouldn't also have to
justify separately.

The pod is asked directly (a new internal route, same trust model as
connector-sync itself) rather than through a user-held API key — this
service already reaches the pod in-cluster for every dispatch, and a
list call needs no new secret to do the same.

## Path parameters

- `provider` string, required

## Query parameters

- `tenant_id` string, uuid, required
- `account_id` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/cognee/apis/cognee-api.md) - [All operations](https://skmtc.dev/cognee/apis/cognee-api/llms.txt) - [OpenAPI document](https://skmtc.dev/cognee/apis/cognee-api/revisions/a7b6c6cb8212?raw)