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

# Retrieves a specific document file for an operation

> Retrieves a document file by its unique identifier. The document ID is obtained from the operation's documents list. The client reference must be unique within your company and you can only access operations belonging to your authenticated company. Content type varies by document (PDF, JPEG, PNG etc.).



## OpenAPI

````yaml /specs/fuelboss/fuelboss-api.json get /v1/operations/{clientReference}/documents/{documentId}
openapi: 3.1.1
info:
  title: FuelBoss API
  description: >-
    REST API providing a powerful and easy way to manage your companies
    nominations and operations.
  termsOfService: https://www.ofiniti.com/legal/platform-service-terms
  contact:
    name: Support Team
    email: itops@ofiniti.com
  version: 1.15.1
servers:
  - url: https://api.demo.fuelboss.net
    description: Demo (sandbox for testing and integration development)
  - url: https://api.fuelboss.net
    description: Production
security:
  - bearerAuth: []
tags:
  - name: OAuth
  - name: Nominations
  - name: Entity management
  - name: Operations
  - name: Common
  - name: Webhooks
  - name: Webhook events
paths:
  /v1/operations/{clientReference}/documents/{documentId}:
    get:
      tags:
        - Operations
      summary: Retrieves a specific document file for an operation
      description: >-
        Retrieves a document file by its unique identifier. The document ID is
        obtained from the operation's documents list. The client reference must
        be unique within your company and you can only access operations
        belonging to your authenticated company. Content type varies by document
        (PDF, JPEG, PNG etc.).
      parameters:
        - name: clientReference
          in: path
          description: >-
            Your company's unique reference for the operation (the same client
            reference used on the corresponding nomination).
          required: true
          schema:
            type: string
        - name: documentId
          in: path
          description: >-
            Encoded document identifier, taken from the `documentId` field of
            the operation's `documents` list.
          required: true
          schema:
            type: string
      responses:
        '200':
          description: OK
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                type: object
                properties:
                  type:
                    type: string
                    format: uri
                  title:
                    type: string
                  status:
                    type: integer
                  detail:
                    type: string
                  instance:
                    type: string
                    format: uri
                  timestamp:
                    type: string
                    format: date-time
                  trace_id:
                    type: string
                description: >-
                  RFC 9457 Problem Details response - fully compliant with
                  latest standard

                  https://tools.ietf.org/html/rfc9457
        '401':
          description: Unauthorized
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                type: object
                properties:
                  type:
                    type: string
                    format: uri
                  title:
                    type: string
                  status:
                    type: integer
                  detail:
                    type: string
                  instance:
                    type: string
                    format: uri
                  timestamp:
                    type: string
                    format: date-time
                  trace_id:
                    type: string
                description: >-
                  RFC 9457 Problem Details response - fully compliant with
                  latest standard

                  https://tools.ietf.org/html/rfc9457
components:
  securitySchemes:
    bearerAuth:
      type: http
      description: >-
        Access token obtained from the /oauth/token endpoint using your client
        credentials.
      scheme: bearer
      bearerFormat: JWT

````