> ## Documentation Index > Fetch the complete documentation index at: https://closedloop.sh/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get an integration ## OpenAPI ````yaml /api-reference/openapi.yaml get /integrations/{id} openapi: 3.0.3 info: title: ClosedLoop AI Public API version: 1.0.0 x-logo: url: https://app.closedloop.sh/favicon.svg altText: ClosedLoop AI description: > # ClosedLoop AI Public API Programmatic access to your team's **product insights**, the structured intelligence ClosedLoop AI extracts from customer conversations (Gong, Fireflies, Slack, …) and structured feedback (surveys, webhooks). Pull insights, themes, features, customer context and analytics into your own tools. ## Two ways to integrate | | **This REST API** | **MCP** (live today) | |---|---|---| | Best for | server-to-server, dashboards, ETL, scripts | AI assistants (Claude, Cursor, …), agents | | Shape | resource endpoints, JSON | tool calls over the Model Context Protocol | | Auth | `X-API-Key` header | OAuth | Most agentic use cases are already covered by MCP. Reach for this REST API when you want plain HTTP resources. ## Base URLs (region-scoped) Your API key belongs to a **team**, and each team lives in exactly one region. Use the base URL for **your** region. A key issued in the EU only works against the EU host. | Region | Base URL | |---|---| | United States | `https://api.closedloop.sh/v1` | | European Union | `https://eu.api.closedloop.sh/v1` | ## Authentication Create a key in **Settings → API Keys** in the app, then send it on every request: ``` X-API-Key: clai_live_xxxxxxxxxxxxxxxxxxxx ``` Keys are **team-scoped**: every response is automatically limited to your team's data. Never expose a key in client-side code. ## Conventions - **Read-only**: every v1 endpoint is a `GET`; nothing is mutated. Feedback is ingested through your connected integrations, not this API. - **Pagination**: list endpoints accept `limit` (default 50, max 200) and `offset`. Responses include a `pagination` object with the full-set `total`. - **Errors**: non-2xx responses return a JSON `{ error, code, hint? }` body. User-safe messages only; never raw internals. - **Rate limits** (per API key): Free 100/hr · Pay-as-you-go 500/hr · Enterprise 2,000/hr. `429` on exceed, with `X-RateLimit-*` headers. - **Linking insights and context**: both carry the same resolved `customer_id`, so you can line up an insight with the context (churn, competitor, satisfaction) for the same customer. Filter either list by `customer_id`. - **Time anchors**: timestamps are ISO 8601 (UTC). contact: name: ClosedLoop AI Support email: support@closedloop.sh url: https://closedloop.sh license: name: Proprietary (ClosedLoop Labs LLC) url: https://closedloop.sh/terms servers: - url: https://api.closedloop.sh/v1 description: United States (production) - url: https://eu.api.closedloop.sh/v1 description: European Union (production) security: - ApiKeyAuth: [] tags: - name: Insights description: | Individual **product insights**: structured, AI-processed feedback items (pain point, severity, workaround, competitor gap, evidence). - name: Themes description: > **Themes**: top-level problem clusters of related insights, RIC-scored. The "what should we build?" surface. Each theme rolls up one or more buildable features. - name: Features description: > **Features**: the buildable, shippable children of a theme. Filter by `theme_id`. Same theme → features hierarchy you see on the roadmap. - name: Customers description: The people and accounts who gave feedback, with CRM context. - name: Context description: > **Customer context**, the strategic intelligence behind your customers: churn reasons, competitive mentions, satisfaction, pricing perception and more, surfaced from conversations. This is the `/context` surface in the app. Each record resolves to a customer (`customer_id`), so it lines up with insights for the same customer. - name: Competitors description: > Competitive pressure derived from your customers' own words. Competitors with a **mention trend over time** (not a static total), and a searchable feed of the exact mentions, each showing the company behind it. - name: Analytics description: Trends, cohorts and facet counts over the full dataset. - name: Integrations description: Connected data sources for your team. - name: Usage description: Credit consumption and usage records for billing transparency. - name: Meta description: Service metadata. paths: /integrations/{id}: get: tags: - Integrations summary: Get an integration parameters: - $ref: '#/components/parameters/PathId' responses: '200': description: Integration detail content: application/json: schema: $ref: '#/components/schemas/Integration' '404': $ref: '#/components/responses/NotFound' components: parameters: PathId: name: id in: path required: true schema: type: string format: uuid description: Resource UUID. schemas: Integration: type: object required: - id - type - name - status properties: id: type: string format: uuid example: in7e6600-0000-4000-8000-000000000001 type: type: string example: gong name: type: string example: Gong Production status: type: string enum: - active - inactive - error - pending example: active last_sync_at: type: string format: date-time example: '2026-06-10T10:00:00Z' created_at: type: string format: date-time example: '2026-01-01T00:00:00Z' Error: type: object required: - error - code properties: error: type: string description: User-safe message. code: type: string example: INVALID_API_KEY hint: type: string description: Optional next step. responses: NotFound: description: Resource not found (or not in your team) content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Not found. code: NOT_FOUND securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: | Team-scoped API key created in the app (Settings → API Keys). Sent as `X-API-Key: ` on every request. ````