> ## 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.

# Create Blacklisted Process Rule

> Add an executable process filename to client detection lists.



## OpenAPI

````yaml /api-reference/openapi/qpapel.json post /blacklisted-processes
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:
  /blacklisted-processes:
    post:
      tags:
        - Client Security & Anti-Cheat
      summary: Create Blacklisted Process Rule
      description: Add an executable process filename to client detection lists.
      operationId: createBlacklistedProcess
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - process_name
              properties:
                process_name:
                  type: string
                  description: Process filename (e.g. CheatEngine.exe, fiddler.exe).
                  example: x64dbg.exe
                is_active:
                  type: boolean
                  default: true
                severity:
                  type: string
                  enum:
                    - suspicious
                    - ban
                  default: suspicious
                  example: ban
                description:
                  type: string
                  description: Context note on why this process is flagged.
                  example: Disassembler and debugger process
      responses:
        '200':
          description: Blacklist rule added.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  data:
                    $ref: '#/components/schemas/BlacklistedProcess'
        '400':
          $ref: '#/components/responses/BadRequestError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
components:
  schemas:
    BlacklistedProcess:
      type: object
      properties:
        id:
          type: integer
          example: 3
        user_id:
          type: integer
          example: 1
        process_name:
          type: string
          example: CheatEngine.exe
        is_active:
          type: boolean
          example: true
        severity:
          type: string
          enum:
            - suspicious
            - ban
          example: ban
        description:
          type: string
          example: Flashed Cheat Engine process detection
        created_at:
          type: string
          format: date-time
          example: '2026-06-12T04:00:00.000Z'
    StandardErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: string
          example: Invalid parameters provided
  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.
  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_...`).

````