> ## 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. # List product and feature areas > Current product-area and feature-area vocabulary. Each area includes its all-time insight total and earliest feedback date, so an empty filtered result can be distinguished from a scope with little or no coverage. Active areas are returned by default. ## OpenAPI ````yaml /api-reference/openapi.yaml get /areas openapi: 3.0.3 info: title: ClosedLoop AI Public API version: 1.2.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`. `/insights` also supports fixed-watermark cursor export with `updated_since`. - **Errors**: non-2xx responses return a JSON `{ error, code, hint? }` body. User-safe messages only; never raw internals. - **Rate limits**: the public API currently has no fixed published per-key quota. - **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: Products description: >- The current product, product-area, and feature-area vocabulary for the team. - 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 customer 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: /areas: get: tags: - Products summary: List product and feature areas description: > Current product-area and feature-area vocabulary. Each area includes its all-time insight total and earliest feedback date, so an empty filtered result can be distinguished from a scope with little or no coverage. Active areas are returned by default. operationId: listAreas parameters: - name: include_archived in: query schema: type: boolean default: false description: Include archived product areas and feature areas. responses: '200': description: Nested area vocabulary with all-time coverage totals content: application/json: schema: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/ProductArea' example: data: - id: 223e4567-e89b-42d3-a456-426614174000 name: Operations description: Operational workflows status: active sort_order: 0 insight_count: 84 feedback_since: '2026-01-12T09:00:00Z' feature_areas: - id: 323e4567-e89b-42d3-a456-426614174000 name: Exports description: Data export workflows status: active sort_order: 0 insight_count: 84 feedback_since: '2026-01-12T09:00:00Z' '401': $ref: '#/components/responses/Unauthorized' components: schemas: ProductArea: type: object required: - id - name - status - sort_order - insight_count - feature_areas properties: id: type: string format: uuid description: Immutable product-area UUID. name: type: string example: Operations description: type: string nullable: true status: type: string example: active sort_order: type: integer example: 0 insight_count: type: integer example: 84 description: Sum of all-time insight counts across returned child feature areas. feedback_since: type: string format: date-time nullable: true description: Earliest feedback across returned child feature areas. feature_areas: type: array items: $ref: '#/components/schemas/FeatureArea' FeatureArea: type: object required: - id - name - status - sort_order - insight_count properties: id: type: string format: uuid description: Immutable feature-area UUID. name: type: string example: Exports description: type: string nullable: true status: type: string example: active sort_order: type: integer example: 0 insight_count: type: integer example: 84 description: All-time insights assigned directly to this feature area. feedback_since: type: string format: date-time nullable: true description: Earliest feedback assigned to this feature area. 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: Unauthorized: description: | Missing or invalid API key. `code` is `NO_API_KEY` when the `X-API-Key` header is absent, or `INVALID_API_KEY` when a key is present but invalid or inactive. content: application/json: schema: $ref: '#/components/schemas/Error' examples: missing: summary: No key provided value: error: API key required. code: NO_API_KEY hint: Send your key in the X-API-Key header. invalid: summary: Key invalid or inactive value: error: Invalid or inactive API key. code: INVALID_API_KEY hint: Create a key in Settings → API Keys. 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. The header name `apikey` is also accepted as an alias. ````