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

# Submit Custom Pipeline

> Submit a custom processor generation request.



## OpenAPI

````yaml https://www.datalab.to/openapi.json post /api/v1/custom_pipelines
openapi: 3.1.0
info:
  title: Datalab API
  version: 0.0.1
servers:
  - url: https://www.datalab.to
    description: Datalab API
security: []
paths:
  /api/v1/custom_pipelines:
    post:
      tags:
        - Custom Pipelines (Deprecated)
      summary: Submit Custom Pipeline
      description: Submit a custom processor generation request.
      operationId: submit_custom_pipeline_api_v1_custom_pipelines_post
      parameters:
        - name: wos-session
          in: cookie
          required: false
          schema:
            type: string
            title: Wos-Session
        - name: datalab_active_team
          in: cookie
          required: false
          schema:
            type: string
            title: Datalab Active Team
      requestBody:
        required: true
        content:
          multipart/form-data:
            schema:
              $ref: >-
                #/components/schemas/Body_submit_custom_pipeline_api_v1_custom_pipelines_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CustomProcessorInitialResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
components:
  schemas:
    Body_submit_custom_pipeline_api_v1_custom_pipelines_post:
      properties:
        request:
          type: string
          title: Request
          description: Natural language description of desired processor behavior
        files:
          items:
            type: string
            format: binary
          type: array
          title: Files
          description: Example documents (PDFs, images, etc.) to use for testing
        name:
          anyOf:
            - type: string
            - type: 'null'
          title: Name
          description: Short display name for the processor (max 120 chars)
        file_instructions:
          anyOf:
            - type: string
            - type: 'null'
          title: File Instructions
          description: >-
            JSON array of per-file instructions: [{"filename": "doc.pdf",
            "general_instructions": "...", "page_instructions": [{"page": 3,
            "instructions": "..."}]}]
        original_params:
          anyOf:
            - type: string
            - type: 'null'
          title: Original Params
          description: >-
            JSON string of base ChandraParsePipeline parameters (e.g.,
            '{"output_formats": ["markdown"]}')
        eval_rubric_id:
          anyOf:
            - type: integer
            - type: 'null'
          title: Eval Rubric Id
          description: >-
            Optional ID of an EvalRubric to attach as the eval definition for
            this processor
      type: object
      required:
        - request
        - files
      title: Body_submit_custom_pipeline_api_v1_custom_pipelines_post
    CustomProcessorInitialResponse:
      properties:
        success:
          type: boolean
          title: Success
          description: Whether the request was accepted
          default: true
        response_check_url:
          type: string
          title: Response Check Url
          description: >-
            URL to poll for status and results. Once generation completes, the
            status response will include the processor_id for execution.
      type: object
      required:
        - response_check_url
      title: CustomProcessorInitialResponse
      description: >-
        Initial response returned immediately after submitting a custom
        processor request.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key

````