> ## Documentation Index > Fetch the complete documentation index at: https://docs.file.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get file ocr > Get file ocr (Optical Character Recognition). The `fileId` field is used to specify the file ocr that should be retrieved. ## OpenAPI ````yaml get /prod/v1/files/{fileId}/ocr openapi: 3.0.0 info: title: Public API description: >- ### Welcome to fileAI’s Public API Documentation. This API allows users to check the health of the system, upload and manage files, and manage AI Schemas. Should you have any questions, please reach out to fileAI via the “Contact a Developer” link below. [Contact a Developer](mailto:support@file.ai) ### Prerequisites Before using our API, please ensure you complete the following prerequisites - You must have a fileAI account. Sign up or login [here](https://orion.file.ai/en/sign-up) - You must have an API Key. After creating your fileAI account, you can generate your API Key. Refer to the Authentication section below for more details. ### Authentication All API requests require an API key for authentication. - To obtain your API key, please log in to your fileAI account and navigate to Project Settings in your dashboard - Keep your API key secure and do not share it publicly. ![Authentication](https://static.orion.file.ai/authentication.png) ### How to Use Your API Key Once you have your API key: - Click the Authorize button on the top-right of this page - Enter your API Key under Value - Click Authorize to start making authenticated requests directly from the documentation ![How to Use Your API Key](https://static.orion.file.ai/how-to-use-api-keys.png) version: '1.0' contact: {} servers: - url: https://api.orion.file.ai description: Default. Use this unless your workspace is on an instance. - url: https://api.orion.{instance}.file.ai description: Instance-specific host. variables: instance: default: au enum: - au - sg - jp description: >- Instance hosting your workspace: au (Australia), sg (Singapore), jp (Japan). security: [] tags: - name: Public API V1 paths: /prod/v1/files/{fileId}/ocr: get: tags: - Public API V1 summary: Get file ocr description: >- Get file ocr (Optical Character Recognition). The `fileId` field is used to specify the file ocr that should be retrieved. operationId: PublicAPIController_getFileOCR parameters: - name: fileId required: true in: path schema: type: string responses: '200': description: The file ocr is found content: application/json: example: ocr: - page_number: 1 text: OCR Result page 1 example - page_number: 2 text: OCR Result page 2 example schema: type: object properties: ocr: type: array items: type: object properties: page_number: type: number text: type: string '401': description: Missing or invalid API key. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetailsDto' '403': description: Read-only or inactive API key. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetailsDto' '404': description: Resource not found. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetailsDto' '422': description: Invalid fileId. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetailsDto' example: type: https://errors.file.ai/validation-failed title: Validation failed status: 422 detail: Invalid fileId. instance: /v1/{route} code: VALIDATION_FAILED requestId: 0f1c8e03-978e-40d5-bc93-6894a57f9324 errors: [] message: Invalid fileId. error: Unprocessable Entity statusCode: 422 '429': description: Rate limit exceeded. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetailsDto' '500': description: Unexpected internal error. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetailsDto' security: - x-api-key: [] components: schemas: ProblemDetailsDto: type: object properties: type: type: string description: A URI identifying the problem type. example: https://errors.file.ai/validation-failed title: type: string description: Stable, human-readable summary of the problem type. example: Validation failed status: type: number description: HTTP status code. example: 422 detail: type: string description: Human-readable explanation specific to this occurrence. example: One or more fields are invalid. instance: type: string description: URI reference for this occurrence (the request path). example: /v1/files/upload code: type: string description: Stable machine-readable error code. example: VALIDATION_FAILED requestId: type: string description: Correlation id for this request. example: 0f1c8e03-978e-40d5-bc93-6894a57f9324 errors: description: Field-level violations (validation only). type: array items: $ref: '#/components/schemas/ProblemErrorItemDto' retryAfter: type: number description: Seconds until the client may retry (present on 429 only). example: 42 message: type: string description: Legacy key (deprecated — use `detail`/`title`). example: Validation failed error: type: string description: Legacy key (deprecated — use `title`). example: Unprocessable Entity statusCode: type: number description: Legacy key (deprecated — use `status`). example: 422 required: - type - title - status - detail - instance - code - requestId - errors - message - error - statusCode ProblemErrorItemDto: type: object properties: code: type: string example: REQUIRED detail: type: string example: must not be empty pointer: type: string description: JSON Pointer to the offending body field. example: '#/fileName' parameter: type: string description: Name of the offending query/header parameter. example: limit required: - code - detail securitySchemes: x-api-key: type: apiKey in: header name: x-api-key description: API key for authentication ````