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

# Upload Executable for SHA-256 Extraction

> Stream and analyze a compiled binary to auto-compute and update product integrity SHA-256 hash.



## OpenAPI

````yaml /api-reference/openapi/qpapel.json post /remote-settings/upload-sha256
openapi: 3.0.3
info:
  title: qPapel Protection Web API
  version: 1.0.0
  description: >
    qPapel Protection API provides developer-grade license validation, remote
    software configuration, staff URL delegation, client anti-cheat heuristics,
    and Discord community integration for desktop applications and loaders.
  contact:
    name: PapelShip Developer Support
    url: https://papelship.com
servers:
  - url: https://app.papelship.com/api/qpapel/v1
    description: Production Server
security:
  - BearerAuth: []
  - ApiKeyHeader: []
  - ApiKeyHeaderLegacy: []
tags:
  - name: License Keys
    description: >-
      Programmatic management of customer license keys, hardware ID bindings,
      activations, and bans.
  - name: Reseller Keys
    description: >-
      Multi-seat reseller key creation, extension, duration freeze, and license
      allocation.
  - name: Remote Settings
    description: >-
      Secure remote runtime configuration mapping, build SHA-256 verification,
      and dynamic values.
  - name: Staff Management
    description: Temporary and scope-limited web portal URLs for support moderators.
  - name: Discord Integrations
    description: >-
      Guild linkage, anti-cheat event channel streaming, and role-based bot
      permissions.
  - name: Client Security & Anti-Cheat
    description: >-
      Device fingerprint monitoring, process blacklists, window title filters,
      and server-side protected strings/files.
paths:
  /remote-settings/upload-sha256:
    post:
      tags:
        - Remote Settings
      summary: Upload Executable for SHA-256 Extraction
      description: >-
        Stream and analyze a compiled binary to auto-compute and update product
        integrity SHA-256 hash.
      operationId: uploadSha256Binary
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              type: object
              required:
                - product_id
                - file
              properties:
                product_id:
                  type: string
                  description: Product cheat_value identifier.
                  example: cs2_cheat
                file:
                  type: string
                  format: binary
                  description: Executable binary or DLL payload.
      responses:
        '200':
          description: Binary analyzed and hash recorded.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  message:
                    type: string
                    example: SHA-256 hash updated successfully
                  sha256:
                    type: string
                    example: >-
                      e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
        '400':
          $ref: '#/components/responses/BadRequestError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
components:
  responses:
    BadRequestError:
      description: Invalid request body or query parameter structure.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/StandardErrorResponse'
          example:
            success: false
            error: Missing required field or invalid value
    UnauthorizedError:
      description: Authentication failed. Missing or invalid developer API key.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/StandardErrorResponse'
          example:
            success: false
            error: Unauthorized access. Valid API key required.
  schemas:
    StandardErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: string
          example: Invalid parameters provided
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API_KEY
      description: >-
        Standard HTTP Bearer token authentication header (e.g. `Authorization:
        Bearer pk_live_...`).
    ApiKeyHeader:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Custom header API key authentication parameter (`x-api-key:
        pk_live_...`).
    ApiKeyHeaderLegacy:
      type: apiKey
      in: header
      name: api-key
      description: >-
        Legacy custom header API key fallback parameter (`api-key:
        pk_live_...`).

````