> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pnbr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Read a connection



## OpenAPI

````yaml /api-reference/openapi.json get /v1/connections/{id}
openapi: 3.1.0
info:
  title: Penumbra Platform API
  version: 1.0.0
  description: >-
    The Penumbra /v1 REST surface. Developer-intent nouns (memories, documents,
    submissions, connections, preflight, bridge) over a typed, governed
    knowledge graph. Every write stages through a reviewable delta; verdicts are
    dispositions and findings, never scores.
servers:
  - url: https://pnbr.io
security:
  - bearerAuth: []
tags:
  - name: Memories
    description: Store and recall agent memory as first-class REST.
  - name: Documents
    description: Add and search documents over the source/file substrate.
  - name: Submissions
    description: A generic capture door for app events, forms, and payloads.
  - name: Search
    description: Hybrid, graph, and retrieval search.
  - name: Ontology & Shapes
    description: Read the active ontology, types, and shapes.
  - name: Deltas
    description: 'The governed-write primitive: stage, plan, apply, revert.'
  - name: Graph
    description: >-
      Direct reads of the typed graph: nodes, edges, and counts. Scope:
      graph:read.
  - name: Extraction
    description: Coerce source material into typed entities through a shape.
  - name: Context & Slices
    description: >-
      Author reusable context scopes (slices) and compile them into context. A
      slice is a saved scope; the context verbs act on a scope or a saved slice.
  - name: Preflight
    description: >-
      Read-only decision-quality verdicts: is the graph fit to act on?
      Disposition plus findings, never a score.
  - name: Loops
    description: Bounded agentic extraction and hydration loops over your context.
  - name: Connections
    description: Headless integration connect for token-paste platforms.
  - name: Bridge
    description: Map an external API's type system onto your ontology.
paths:
  /v1/connections/{id}:
    get:
      tags:
        - Connections
      summary: Read a connection
      operationId: getConnection
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Connection status + next action.
          content:
            application/json:
              example:
                connection_id: adc2ff41-191d-4706-913b-dc37bf330aab
                platform: granola
                status: active
                target_project_id: e718d035-8693-4187-a6c3-b79bd62246b0
                sync: cron
                last_synced_at: '2026-05-28T17:54:42.218Z'
                next_action:
                  method: POST
                  path: /v1/connections/adc2ff41-191d-4706-913b-dc37bf330aab/sync
                request_id: 1d881419-5188-4419-b94d-824f7480151d
        '404':
          description: Not found
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        A `pnbr-` API key. Project-scoped keys make `project_id` implicit;
        org-scoped keys require it.

````