---
title: "Inspect integration connection"
description: "Callers: an account bearer (API key or access token). The web app may also use its browser session."
canonical: "https://www.cool.computer/docs/api-reference/integrations/inspect-integration-connection"
---
# Inspect integration connection

> Callers: an account bearer (API key or access token). The web app may also use its browser session.

```http
GET https://api.cool.computer/api/integrations/connect/{id}
```

Callers: an account bearer (API key or access token). The web app may also use its browser session.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Parameters

- `id` (path, string, required)

## Responses

- `200`: Success
  - `application/json` (object)
    - `id` (string, required)
    - `provider` ("claude" or "codex" or "grok" or "github", required)
    - `state` ("starting" or "waiting" or "connected" or "failed" or "canceled", required)
    - `url` (string, uri)
    - `user_code` (string)
    - `message` (string)
    - `needs_code` (boolean, required)
- `400`: Bad request
- `401`: Unauthorized.
- `403`: Forbidden
- `404`: Not found
- `409`: Conflict
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `503`: Service unavailable

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl "https://api.cool.computer/api/integrations/connect/$PARAM_ID" \
  -H "authorization: Bearer $TOKEN"
```
