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

# List File Placements

> Lists every place a file appears — one placement per owner the file has
been added to, with the owning entity's display name resolved. The
single-file metadata read summarizes only the file's primary (oldest)
placement; this endpoint is the full enumeration.

**Required permission:** `company.file:read`




## OpenAPI

````yaml /openapi/generated-external-api.yaml get /api/v1/companies/{companyId}/files/{fileId}/placements
openapi: 3.0.3
info:
  title: AI Insurance External API
  description: External API for AI Insurance platform
  version: 1.0.0
  contact:
    email: support@aiinsurance.io
servers:
  - url: https://go.aiinsurance.io
    description: Production
security:
  - ApiKeyAuth: []
paths:
  /api/v1/companies/{companyId}/files/{fileId}/placements:
    get:
      tags:
        - Company Files
      summary: List File Placements
      description: |
        Lists every place a file appears — one placement per owner the file has
        been added to, with the owning entity's display name resolved. The
        single-file metadata read summarizes only the file's primary (oldest)
        placement; this endpoint is the full enumeration.

        **Required permission:** `company.file:read`
      operationId: listCompanyFilePlacements
      parameters:
        - $ref: '#/components/parameters/companyId'
        - $ref: '#/components/parameters/fileId'
      responses:
        '200':
          description: The file's placements, oldest first
          content:
            application/json:
              schema:
                type: object
                properties:
                  placements:
                    type: array
                    items:
                      $ref: '#/components/schemas/CompanyFilePlacement'
              examples:
                shared:
                  summary: A file shared from an Event to a Submission
                  value:
                    placements:
                      - placementId: 550e8400-e29b-41d4-a716-446655440031
                        entityType: event
                        entityId: 550e8400-e29b-41d4-a716-446655440010
                        entityDisplayName: Warehouse Fire
                        folderId: null
                        category: Evidence
                        createdAt: '2026-06-11T09:14:30.000Z'
                      - placementId: 550e8400-e29b-41d4-a716-446655440032
                        entityType: submission
                        entityId: 550e8400-e29b-41d4-a716-446655440011
                        entityDisplayName: SUB-001
                        folderId: 550e8400-e29b-41d4-a716-446655440001
                        category: Loss Runs
                        createdAt: '2026-06-11T10:02:00.000Z'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          description: File not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                notFound:
                  summary: File does not exist
                  value:
                    error:
                      code: NotFound
                      message: 'File not found: 550e8400-e29b-41d4-a716-446655440020'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    companyId:
      name: companyId
      in: path
      required: true
      schema:
        type: string
        format: uuid
      description: Company identifier
    fileId:
      name: fileId
      in: path
      required: true
      schema:
        type: string
        format: uuid
      description: File identifier
  schemas:
    CompanyFilePlacement:
      type: object
      description: |
        One appearance ("placement") of a file under an owner. A file can be
        placed on more than one entity at a time — sharing adds a placement, it
        never copies the stored bytes; every placement sees the same current
        version and history. Folder location and category are per placement, the
        display name lives on the file itself.
      properties:
        placementId:
          type: string
          format: uuid
          description: Placement identifier
        entityType:
          type: string
          enum:
            - event
            - exposure
            - quote
            - submission
            - person
            - organization
            - policy
            - company
          description: The placement owner's entity type
        entityId:
          type: string
          format: uuid
          nullable: true
          description: The owner entity's id (null for the company-level placement)
        entityDisplayName:
          type: string
          nullable: true
          description: >
            The owner entity's display name (null for company-level placements
            and

            for owners that have since been deleted)
        folderId:
          type: string
          format: uuid
          nullable: true
          description: The folder this placement sits in (null = the owner's top level)
        category:
          type: string
          nullable: true
          description: This placement's category label (per placement)
        createdAt:
          type: string
          format: date-time
          description: When the placement was created (ISO 8601)
    ErrorResponse:
      type: object
      description: Standard error response for all external API endpoints
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              description: Machine-readable error code
              example: VALIDATION_ERROR
            message:
              type: string
              description: Human-readable error message
              example: 'submissionId: Required field is missing'
            userMessages:
              type: array
              description: >-
                Clean, verbatim-displayable messages — one entry per failure,
                free of error-code tags, field paths, and internal noise.
                Suitable for showing to end users as-is.
              items:
                type: string
              example:
                - Exposures of type 'company' require an address
            details:
              type: array
              description: Additional details for validation errors (field-level errors)
              items:
                type: object
                properties:
                  field:
                    type: string
                    description: The field that caused the error
                    example: submissionId
                  message:
                    type: string
                    description: Description of the field error
                    example: Required field is missing
  responses:
    Unauthorized:
      description: Unauthorized - Invalid or missing API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          examples:
            missingApiKey:
              summary: Missing API key
              value:
                error:
                  code: AuthenticationError
                  message: API key authentication required
                  userMessages:
                    - API key authentication required
            invalidApiKey:
              summary: >-
                Invalid API key (e.g. unknown key, or a Bearer token used
                instead of an API key)
              value:
                error:
                  code: AuthenticationError
                  message: Invalid API key
                  userMessages:
                    - Invalid API key
    Forbidden:
      description: Forbidden - Insufficient permissions
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          examples:
            insufficientPermissions:
              summary: Insufficient permissions
              value:
                error:
                  code: AuthorizationError
                  message: User is not authorized to perform the requested action
                  userMessages:
                    - User is not authorized to perform the requested action
            companyMismatch:
              summary: A valid API key naming another company in the URL
              value:
                error:
                  code: AuthorizationError
                  message: API key is not scoped to the requested company
                  userMessages:
                    - API key is not scoped to the requested company
    InternalServerError:
      description: Internal Server Error - Unexpected error occurred
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          examples:
            internalError:
              summary: Unexpected server error
              value:
                error:
                  code: UncaughtActionError
                  message: Uncaught error occurred in <actionName>
                  userMessages:
                    - An unexpected error occurred. Please try again later.
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        API key authentication. Send your raw API key as the `Authorization`
        header value with NO scheme prefix — `Authorization: YOUR-API-KEY`. Do
        NOT prefix it with `Bearer ` or `ApiKey `, and do not use an `X-API-Key`
        header; those are not accepted.

````