---
title: "List connection variables"
method: GET
path: "/connection/{id}/variables"
tags: ["Connections"]
---

# List connection variables

`GET /connection/{id}/variables`

## Request

- Base URL: `https://api.elaichi.ai`
- URL: `https://api.elaichi.ai/connection/{id}/variables`
- Auth: HTTP bearer

Lists the connection's context variables: the setup values the customer supplied when they connected the account (subdomain, region, instance URL), one row per top-level key, plus one valueless row for every value Elaichi stores as a secret. Requires `can_manage`, not just read access: a `view` or `use` grantee runs tools through the connection, but the answers its owner typed into the connect form are not part of that, so a caller without it gets `403`, deliberately not an empty `200`. An unbound connection answers an empty list. `can_manage` here means the owner or a holder of an `edit` grant.

## Path parameters

- `id` string, required

## Query parameters

- `limit` integer
- `cursor` string

## Headers

- `X-Organization-Id` string

## Response `200`

OK

- object
  - `result` object[], required
    - `name` string, required: Top-level context key; rows sort and page over it.
    - `value` unknown, required
    - `is_secret` boolean, required: Whether Elaichi stores this value as a secret; the value itself is returned as `null`.
    - `has_secrets` boolean, required: A leaf at or under this key was withheld — true for a secret key itself, and for a public object one of whose leaves was stripped.
  - `next_cursor` string, nullable, required
  - `prev_cursor` string, nullable, required

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not found
- `429`: Rate limited

---

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