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

# List connections

> Returns all active platform connections for the authenticated customer.
Use this to verify which platforms are connected after calling `/connect`.


Returns all active platform connections for the authenticated customer. Use this to confirm
which platforms are connected after calling [`POST /connect`](/api-reference/connect).

The response is an array of connection objects. Each includes the platform name, connection
status, when it was established, and how many entity mappings exist for that platform.

If no platforms are connected, the `connections` array is empty.

<Note>
  Only connections with status `active` are returned. If a connect call failed mid-flight, the
  connection may be in `seeding` or `error` state and will not appear in this response. Retry the
  [`POST /connect`](/api-reference/connect) call to re-seed.
</Note>


## OpenAPI

````yaml GET /connections
openapi: 3.1.0
info:
  title: Structural API
  version: '1.0'
  description: |
    Bidirectional data translation between construction management platforms.
    One integration gives you normalized access to every connected platform.
  contact:
    email: support@structural.app
    url: https://structural.app
servers:
  - url: https://api.structural.app/api/v1
    description: Production
security: []
paths:
  /connections:
    get:
      tags:
        - Connections
      summary: List connections
      description: >
        Returns all active platform connections for the authenticated customer.

        Use this to verify which platforms are connected after calling
        `/connect`.
      operationId: getConnections
      responses:
        '200':
          description: Connections retrieved
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      connections:
                        type: array
                        items:
                          $ref: '#/components/schemas/ConnectionInfo'
        '401':
          $ref: '#/components/responses/AuthenticationError'
      security:
        - bearerAuth: []
components:
  schemas:
    ConnectionInfo:
      type: object
      properties:
        platform:
          type: string
          enum:
            - procore
            - dynamics
          example: procore
        status:
          type: string
          description: Connection status. Only active connections are returned.
          enum:
            - active
          example: active
        connected_at:
          type: string
          format: date-time
          description: When the connection was established
          example: '2026-04-11T12:00:00.000Z'
        entities_synced:
          type: integer
          description: Total entity mappings for this platform
          example: 38
    ErrorResponse:
      type: object
      properties:
        error:
          type: object
          required:
            - type
            - message
            - request_id
          properties:
            type:
              type: string
              description: Machine-readable error code
              example: VALIDATION_ERROR
            message:
              type: string
              description: Human-readable error description
              example: platform and entity_type query params required
            request_id:
              type: string
              description: Unique request identifier — quote this in support requests
              example: req_a1b2c3d4e5f6
  responses:
    AuthenticationError:
      description: Missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            error:
              type: AUTHENTICATION_ERROR
              message: Invalid or missing API key
              request_id: req_a1b2c3d4e5f6
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >
        API key passed as a Bearer token. Keys are prefixed: `sk_demo_*`
        (sandbox),

        `sk_live_*` (production), `sk_test_*` (staging).

````