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

# Get File Context

> Retrieve full details for a single file context by its key.



## OpenAPI

````yaml GET /api/v1/contexts/{context_key}
openapi: 3.0.3
info:
  title: Uplint API
  version: 0.1.0
  description: >-
    Uplint is a file safety and integrity platform. Upload files through
    context-aware pipelines that automatically validate integrity, detect blank
    or placeholder content, and scan for viruses — all behind a single API.


    This specification covers the core Uplint REST API:


    - **API Keys** — Create and manage scoped API keys for programmatic access.

    - **File Contexts** — Define upload pipelines with per-context rules
    (allowed extensions, size limits, blank/corrupt rejection, virus scanning,
    rate limits, and storage quotas).

    - **Files** — Upload, list, download, inspect, and delete files. Every
    upload runs through the validation pipeline configured on its context.


    All endpoints are tenant-scoped. Authenticate with an API key or JWT token
    via the `Authorization` header.
  contact:
    name: Uplint Team
    url: https://uplint.dev
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
  - url: https://api.uplint.dev
    description: Production
  - url: http://localhost:8000
    description: Local development
security:
  - BearerAuth: []
tags:
  - name: API Keys
    description: >-
      Create, list, inspect, update, and revoke API keys. Each key carries
      scoped permissions (`upload`, `download`, `metadata`, `delete`, `admin`)
      and is bound to the authenticated tenant.
  - name: File Contexts
    description: >-
      File contexts define upload pipelines. Each context specifies allowed
      extensions, max file size, whether to reject blank or corrupt files, virus
      scanning, rate limits, and storage quotas. Files are always uploaded into
      a context.
  - name: Files
    description: >-
      Upload, list, download, inspect metadata, and delete files. Every upload
      is validated against its context rules before storage.
  - name: Storage Buckets
    description: >-
      Manage the S3 buckets a tenant stores files in. Each tenant can register
      multiple buckets (bring-your-own S3 credentials); one is the **default**
      (fallback) bucket, and file contexts can be routed to any active bucket.
      All storage endpoints require an `admin`-scoped API key.
paths:
  /api/v1/contexts/{context_key}:
    get:
      tags:
        - File Contexts
      summary: Get file context
      description: Retrieve full details for a single file context by its key.
      operationId: getFileContext
      parameters:
        - $ref: '#/components/parameters/ContextKey'
      responses:
        '200':
          description: File context details.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponse_Context'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  parameters:
    ContextKey:
      name: context_key
      in: path
      required: true
      schema:
        type: string
      description: The file context's unique key (e.g. `patient_reports`).
  schemas:
    SuccessResponse_Context:
      type: object
      properties:
        status:
          type: string
          enum:
            - SUCCESS
        message:
          type: string
        data:
          $ref: '#/components/schemas/ContextResponse'
        timestamp:
          type: string
          format: date-time
    ContextResponse:
      type: object
      properties:
        context_id:
          type: string
        context_key:
          type: string
        tenant_id:
          type: string
        display_name:
          type: string
        description:
          type: string
          nullable: true
        allowed_extensions:
          type: array
          items:
            type: string
        max_file_size_mb:
          type: integer
        storage_path_template:
          type: string
        reject_blank_files:
          type: boolean
        reject_corrupt_files:
          type: boolean
        scan_for_viruses:
          type: boolean
        upload_rate_limit:
          nullable: true
          allOf:
            - $ref: '#/components/schemas/UploadRateLimitConfig'
        storage_quota_mb:
          type: integer
          nullable: true
        storage_used_bytes:
          type: integer
          nullable: true
        status:
          $ref: '#/components/schemas/FileContextStatus'
        metadata:
          type: object
          additionalProperties: true
        storage_config_id:
          type: string
          nullable: true
          description: >-
            ID of the storage bucket (`config_id`) this context routes uploads
            to. `null` uses the tenant's default bucket.
    ErrorResponse:
      type: object
      properties:
        status:
          type: string
          enum:
            - ERROR
        message:
          type: string
        errors:
          type: array
          items:
            type: string
        timestamp:
          type: string
          format: date-time
    UploadRateLimitConfig:
      type: object
      required:
        - max_uploads
        - window_seconds
      properties:
        max_uploads:
          type: integer
          minimum: 1
          maximum: 10000
          description: Maximum number of uploads allowed within the time window.
        window_seconds:
          type: integer
          minimum: 1
          maximum: 3600
          description: Time window in seconds.
    FileContextStatus:
      type: string
      enum:
        - active
        - inactive
  responses:
    Unauthorized:
      description: Missing, invalid, or expired authentication credentials.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            status: ERROR
            message: Invalid or missing API key
            errors:
              - Authentication required
            timestamp: '2026-02-10T12:00:00Z'
    NotFound:
      description: The requested resource does not exist.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            status: ERROR
            message: Resource not found
            errors:
              - Not found
            timestamp: '2026-02-10T12:00:00Z'
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        Pass an API key or JWT token. API keys can be sent as `Authorization:
        Bearer <key>` or `Authorization: <key>`.

````