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

# Get Connection Report

> Simple report showing which users have connected their calendar and email. No parameters needed - shows all users in the organization.



## OpenAPI

````yaml /api-reference/openapi.json get /connectionReport
openapi: 3.0.1
info:
  title: Attention Service V2
  description: Attention Service API V2
  termsOfService: https://www.attention.com/terms-of-use
  contact:
    name: Attention Team
    url: https://docs.attention.com/welcome
    email: support@attention.com
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0.html
  version: 1.8.0
servers:
  - url: https://api.attention.tech/v2
security:
  - APIKeyHeader: []
paths:
  /connectionReport:
    get:
      tags:
        - Tool
      summary: Get Connection Report
      description: >-
        Simple report showing which users have connected their calendar and
        email. No parameters needed - shows all users in the organization.
      operationId: getConnectionReport
      responses:
        '200':
          description: Connection report successfully generated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConnectionReportResponse'
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/ConnectionReportResponse'
        '400':
          description: Bad request - invalid parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Authentication failed - valid API key required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/Error'
        default:
          description: Unexpected error occurred while generating the connection report
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    ConnectionReportResponse:
      type: object
      properties:
        summary:
          $ref: '#/components/schemas/ConnectionSummary'
        users:
          type: array
          description: List of all users with their connection status
          items:
            $ref: '#/components/schemas/UserConnectionStatus'
      example:
        summary:
          totalUsers: 4
          fullyConnected: 1
          missingCalendar: 1
          missingEmail: 1
          missingBoth: 1
        users:
          - uuid: user1-uuid
            email: user1@company.com
            firstName: John
            lastName: Doe
            calendarConnected: true
            emailConnected: true
          - uuid: user2-uuid
            email: user2@company.com
            firstName: Jane
            lastName: Smith
            calendarConnected: false
            emailConnected: true
          - uuid: user3-uuid
            email: user3@company.com
            firstName: Bob
            lastName: Johnson
            calendarConnected: true
            emailConnected: false
          - uuid: user4-uuid
            email: user4@company.com
            firstName: Alice
            lastName: Brown
            calendarConnected: false
            emailConnected: false
    Error:
      type: object
      properties:
        id:
          type: string
          description: A unique identifier for the error.
        status:
          type: string
          description: >-
            The HTTP status code applicable to this problem, expressed as a
            string value.
        code:
          type: string
          description: An application-specific error code, expressed as a string value.
        title:
          type: string
          description: A short, human-readable summary of the problem.
        detail:
          type: string
          description: >-
            A human-readable explanation specific to this occurrence of the
            problem.
        source:
          type: object
          properties:
            pointer:
              type: string
            parameter:
              type: string
        meta:
          type: object
          properties: {}
      example:
        id: not_found_error
        status: '404'
        code: '404'
        title: Not Found Error
        detail: The requested resource was not found
        source:
          pointer: /data/attributes/id
    ConnectionSummary:
      required:
        - fullyConnected
        - missingBoth
        - missingCalendar
        - missingEmail
        - totalUsers
      type: object
      properties:
        totalUsers:
          type: integer
          description: Total number of users in the organization
        fullyConnected:
          type: integer
          description: Users connected to both calendar and email
        missingCalendar:
          type: integer
          description: Users missing calendar connection
        missingEmail:
          type: integer
          description: Users missing email connection
        missingBoth:
          type: integer
          description: Users missing both calendar and email connections
      example:
        totalUsers: 50
        fullyConnected: 35
        missingCalendar: 8
        missingEmail: 4
        missingBoth: 3
    UserConnectionStatus:
      required:
        - calendarConnected
        - email
        - emailConnected
        - firstName
        - lastName
        - uuid
      type: object
      properties:
        uuid:
          type: string
          description: User unique identifier
        email:
          type: string
          description: User email address
        firstName:
          type: string
          description: User first name
        lastName:
          type: string
          description: User last name
        calendarConnected:
          type: boolean
          description: Whether the user has connected their calendar
        emailConnected:
          type: boolean
          description: Whether the user has connected their email
      example:
        uuid: user-uuid-123
        email: jane@example.com
        firstName: Jane
        lastName: Smith
        calendarConnected: true
        emailConnected: true
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      name: Authorization
      in: header

````