---
title: "List the connections an intern can use"
method: GET
path: "/vault/interns/{internId}/connections"
tags: ["Vault"]
---

# List the connections an intern can use

`GET /vault/interns/{internId}/connections`

## Request

- Base URL: `https://openrouter.ai/api/v1`
- URL: `https://openrouter.ai/api/v1/vault/interns/{internId}/connections`
- Auth: HTTP bearer

Lists the connections in scope for the intern, by the key of their card on the dashboard's Connections tab: `github`, `slack`, `google`, a catalog MCP server such as `linear` or `notion`, or `mcp:<host>` for a custom MCP server. A connection is listed when it is stored, enabled, and not turned off or hidden for this intern, as the Connections tab lists it; whether its last test passed is not part of the rule. `ori features add` checks a feature's `ori.requires.connections` against this list. Keys only, never credentials. Returns 404 for an intern the key cannot see. The scope is selected by the API key: workspace routes act on the key's active workspace and intern routes act on one intern inside that workspace. There is no default workspace and no fallback to another scope. Every vault route, including reads, requires access to the Intern API programme and returns 404 outside it. An intern's own API key is confined to that intern: it can always read the intern's secrets and effective secrets, writes to them follow the rules above, and every other intern and every workspace route answers 404. Requests on regional hostnames such as `eu.openrouter.ai` are refused. [API key](/docs/api-reference/authentication) required.

## Path parameters

- `internId` string, uuid, required: UUID of an intern in the workspace selected by the API key.

## Response `200`

The connections the intern can use.

- object
  - `data` object[], required
    - `key` string, required

## Other responses

- `400`: Bad Request - The secret name, path, query or JSON body failed validation. The vault returns 400 for a malformed request as well.
- `401`: Unauthorized - Missing or unknown API key. Provisioning keys cannot call vault routes.
- `403`: Forbidden - The key has no usable workspace scope, or the request arrived on a regional hostname.
- `404`: Not Found - The intern is not in the selected workspace or is not visible to the key (a member key without an admin role sees only interns its member created or interns in workspaces they administer), the secret does not exist in the selected scope, or the caller is outside the intern programme.
- `408`: Request Timeout - The route deadline passed before the request completed, or the request body stopped arriving.
- `429`: Too Many Requests - The vault rate limit was reached.
- `500`: Internal Server Error - Scope lookup failed.
- `502`: Bad Gateway - The vault could not be reached or returned an unexpected response.
- `503`: Service Unavailable - Vault writes are disabled for the caller, or the vault is not configured.
- `504`: Gateway Timeout - The vault did not answer in time.

## Changes

- **2026-10-18** `06d574d7fe7d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/openrouterteam/apis/openrouter-api/changes/vault/interns/:internId/connections/get.md)

---

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