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

# delete_job

> Hide a job from listings, keeping it for billing. Cost class: fast.

A **soft** delete. The row survives, so ``units`` keep answering and
``GET /v1/usage`` still counts the work; what stops is ``GET /v1/jobs``
returning it. Reading it by id still works, with ``deleted_at`` set — the
same reasoning as an expired payload, where a 404 would conflate "gone" with
"never existed".

A job still queued or running is **cancelled first**, so hitting delete
stops the compute rather than paying for a run nobody will ever see. A job
that finished under us is simply hidden: there was nothing left to stop, and
refusing the delete over a race the caller cannot see would be noise.

``Temporal`` is not declared as a dependency here because asking for the
client connects: most deletes are of finished runs and need it for nothing,
so an outage must not fail work that is entirely in Postgres.

There is no project-level route to pair with ``?project_id=``: a run's
fan-out is one job per file, and the console deletes the group the same way
it renames it — per job, over the ids it already holds.



## OpenAPI

````yaml /openapi.json delete /v1/jobs/{job_id}
openapi: 3.1.0
info:
  description: >-
    Document intelligence: parse, split, classify, extract, and ground files, or
    build a searchable workspace. Authenticate with ``X-API-Key``.
  title: NDI Platform API
  version: 0.1.0
servers:
  - url: https://ndi-api.nace.ai
security: []
tags: []
paths:
  /v1/jobs/{job_id}:
    delete:
      tags:
        - operations
      summary: delete_job
      description: >-
        Hide a job from listings, keeping it for billing. Cost class: fast.


        A **soft** delete. The row survives, so ``units`` keep answering and

        ``GET /v1/usage`` still counts the work; what stops is ``GET /v1/jobs``

        returning it. Reading it by id still works, with ``deleted_at`` set —
        the

        same reasoning as an expired payload, where a 404 would conflate "gone"
        with

        "never existed".


        A job still queued or running is **cancelled first**, so hitting delete

        stops the compute rather than paying for a run nobody will ever see. A
        job

        that finished under us is simply hidden: there was nothing left to stop,
        and

        refusing the delete over a race the caller cannot see would be noise.


        ``Temporal`` is not declared as a dependency here because asking for the

        client connects: most deletes are of finished runs and need it for
        nothing,

        so an outage must not fail work that is entirely in Postgres.


        There is no project-level route to pair with ``?project_id=``: a run's

        fan-out is one job per file, and the console deletes the group the same
        way

        it renames it — per job, over the ids it already holds.
      operationId: delete_job_v1_jobs__job_id__delete
      parameters:
        - description: Job identifier.
          in: path
          name: job_id
          required: true
          schema:
            description: Job identifier.
            format: uuid
            title: Job Id
            type: string
      responses:
        '204':
          description: Successful Response
        '504':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorEnvelope'
          description: Gateway Timeout
        default:
          content:
            application/json:
              example:
                error:
                  code: invalid_request
                  detail: null
                  message: >-
                    Request body has extra fields that this operation does not
                    accept.
                  request_id: req-01j9k2n3p4q5r6s7t8v9
                  retryable: false
              schema:
                $ref: '#/components/schemas/ErrorEnvelope'
          description: >-
            Typed error envelope used by every 4xx and 5xx. ``error.code``
            distinguishes the failure; HTTP status is a consequence of the code.
      security:
        - APIKeyHeader: []
components:
  schemas:
    ErrorEnvelope:
      description: Every non-2xx body on ``/v1``.
      example:
        error:
          code: invalid_request
          detail: null
          message: Request body has extra fields that this operation does not accept.
          request_id: req-01j9k2n3p4q5r6s7t8v9
          retryable: false
      properties:
        error:
          $ref: '#/components/schemas/Error'
      required:
        - error
      title: ErrorEnvelope
      type: object
    Error:
      description: The error object, per spec 12 §1.8.
      properties:
        code:
          $ref: '#/components/schemas/ErrorCode'
        detail:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          description: Structured payload, when the code carries one.
          title: Detail
        message:
          description: Human- and model-readable; says what to do differently.
          title: Message
          type: string
        request_id:
          description: Per-request correlation id; matches the ``X-Request-Id`` header.
          title: Request Id
          type: string
        retryable:
          description: Whether retrying the identical request could succeed.
          title: Retryable
          type: boolean
      required:
        - code
        - message
        - retryable
        - request_id
      title: Error
      type: object
    ErrorCode:
      description: |-
        Every error the ``/v1`` surface can return.

        Clients must treat this as an **open** enum: a new member is an additive
        change (spec 12 §9), and a client that crashes on an unknown code makes
        every future error a breaking change.
      enum:
        - invalid_request
        - unsupported_file_type
        - file_too_large
        - invalid_schema
        - invalid_sql
        - invalid_path_prefix
        - command_not_permitted
        - batch_too_large
        - domain_validation_failed
        - default_label_required
        - wait_required_for_zero_retention
        - workspace_not_found
        - file_not_found
        - job_not_found
        - upload_not_found
        - node_not_found
        - schema_not_found
        - domain_not_found
        - session_not_found
        - access_label_not_found
        - path_conflict
        - schema_version_conflict
        - access_label_name_taken
        - workspace_name_taken
        - access_label_in_use
        - upload_expired
        - file_not_ingested
        - workspace_deleting
        - workspace_not_deletable
        - ingestion_in_progress
        - job_not_cancellable
        - confirmation_required
        - domain_not_published
        - domain_in_use
        - reserved_domain_slug
        - kg_not_built
        - kg_build_in_progress
        - session_busy
        - range_not_satisfiable
        - result_expired
        - access_denied
        - access_backstop_violation
        - access_mode_not_implemented
        - rate_limited
        - concurrency_limit_reached
        - quota_exceeded
        - corrupt_file
        - zero_byte_file
        - encrypted_file
        - parse_failed
        - ocr_failed
        - conversion_failed
        - sheetless_workbook
        - unplayable_media
        - unclassified_pages
        - job_cancelled
        - job_timeout
        - upstream_unavailable
        - internal_error
        - unauthorized
        - not_implemented
      title: ErrorCode
      type: string
  securitySchemes:
    APIKeyHeader:
      in: header
      name: X-API-Key
      type: apiKey

````