> ## 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.

# List Scorecards

> Retrieves scorecards visible to the caller. User-scoped API keys see scorecards for their allowed teams; org-scoped API keys see every scorecard in the organization. Pagination is optional: when both page and size are omitted, the full result set is returned to preserve backward compatibility.



## OpenAPI

````yaml /api-reference/openapi.json get /scorecards
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:
  /scorecards:
    get:
      tags:
        - Scorecard
      summary: List Scorecards
      description: >-
        Retrieves scorecards visible to the caller. User-scoped API keys see
        scorecards for their allowed teams; org-scoped API keys see every
        scorecard in the organization. Pagination is optional: when both page
        and size are omitted, the full result set is returned to preserve
        backward compatibility.
      operationId: listScorecards
      parameters:
        - name: page
          in: query
          description: >-
            Page number for pagination (1-indexed). If omitted, pagination is
            not applied and every visible scorecard is returned.
          schema:
            minimum: 1
            type: integer
        - name: size
          in: query
          description: >-
            Number of scorecards per page (min 1, max 200). Ignored when page is
            omitted.
          schema:
            maximum: 200
            minimum: 1
            type: integer
      responses:
        '200':
          description: Scorecards successfully retrieved
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
            application/vnd.api+json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: Bad request - invalid pagination parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                id: invalid_parameter
                status: '400'
                code: '400'
                title: Invalid Parameter
                detail: size must be between 1 and 200
            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'
              example:
                id: unauthorized
                status: '401'
                code: '401'
                title: Unauthorized
                detail: Authentication failed - valid API key required
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/Error'
        default:
          description: Unexpected error occurred while retrieving scorecards
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    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
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      name: Authorization
      in: header

````