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

# Post Orchestrate

> Called regularly: run the process steps for every delivery day whose
input changed since the last run. Idempotent when nothing changed.



## OpenAPI

````yaml /setup/internal-openapi.json post /v1/process/orchestrate
openapi: 3.1.0
info:
  title: n:lead Scheduling Bridge — Internal API
  version: 0.4.0
  description: >-
    Internal API of the n:lead scheduling bridge: the process endpoints that
    drive the day-ahead pipeline (aggregate, publish the open position, submit
    schedules, generate forecasts, orchestrate) and the operator console
    endpoints. Requires the process API key; not for customer use.
servers:
  - url: https://{your-service-host}
    description: Deployed service
  - url: http://localhost:8000
    description: Local development
security: []
paths:
  /v1/process/orchestrate:
    post:
      summary: Post Orchestrate
      description: |-
        Called regularly: run the process steps for every delivery day whose
        input changed since the last run. Idempotent when nothing changed.
      operationId: post_orchestrate_v1_process_orchestrate_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OrchestrateResponse'
      security:
        - APIKeyHeader: []
components:
  schemas:
    OrchestrateResponse:
      properties:
        checked_days:
          type: integer
          title: Checked Days
        runs:
          items:
            $ref: '#/components/schemas/OrchestrationRun'
          type: array
          title: Runs
        service_state:
          type: string
          enum:
            - running
            - stopped
          title: Service State
          default: running
      type: object
      required:
        - checked_days
        - runs
      title: OrchestrateResponse
      description: >-
        Result of one orchestrator invocation (scope: process, called
        regularly).


        Only delivery days whose input changed since the last run appear in

        ``runs``; an unchanged system yields an empty list. When the service is

        stopped via the console, ``service_state`` is ``stopped`` and nothing

        runs.
    OrchestrationRun:
      properties:
        delivery_day:
          type: string
          format: date
          title: Delivery Day
        actions:
          items:
            type: string
          type: array
          title: Actions
        error:
          anyOf:
            - type: string
            - type: 'null'
          title: Error
      type: object
      required:
        - delivery_day
        - actions
      title: OrchestrationRun
      description: What the orchestrator did for one delivery day.
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key

````