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

# Read back the schedules Engrate holds for a delivery day

> What actually went out: per TSO the schedule Engrate holds for the
day, its versions with every series as Engrate stored it (``amount``
in MW per quarter-hour), and the TSO's answers (ACK/ANO/CNF) - read
from Engrate's Schedule Management API with the bridge's own key. Next
to it, ``bridge``: the input hash the bridge submitted and Engrate's
answer to that submission. GETs only; nothing is sent.



## OpenAPI

````yaml /setup/internal-openapi.json get /v1/process/delivery-days/{delivery_day}/engrate
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), the operator console endpoints,
    and the read-only operator-app endpoints under /v1/mobile. The process and
    console endpoints require the process API key, /v1/mobile a device key of
    the mobile scope; not for customer use.
servers:
  - url: https://{host}
    description: Deployed service
    variables:
      host:
        default: api.energy.nlead.ch
        description: >-
          The service hostname - n:lead provides it (see the Base URL on the API
          introduction page)
  - url: http://localhost:8000
    description: Local development
security: []
paths:
  /v1/process/delivery-days/{delivery_day}/engrate:
    get:
      summary: Read back the schedules Engrate holds for a delivery day
      description: |-
        What actually went out: per TSO the schedule Engrate holds for the
        day, its versions with every series as Engrate stored it (``amount``
        in MW per quarter-hour), and the TSO's answers (ACK/ANO/CNF) - read
        from Engrate's Schedule Management API with the bridge's own key. Next
        to it, ``bridge``: the input hash the bridge submitted and Engrate's
        answer to that submission. GETs only; nothing is sent.
      operationId: >-
        get_engrate_read_back_v1_process_delivery_days__delivery_day__engrate_get
      parameters:
        - name: delivery_day
          in: path
          required: true
          schema:
            type: string
            format: date
            title: Delivery Day
        - name: all_versions
          in: query
          required: false
          schema:
            type: boolean
            description: Every version, or only the newest per TSO
            default: true
            title: All Versions
          description: Every version, or only the newest per TSO
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
                title: >-
                  Response Get Engrate Read Back V1 Process Delivery Days 
                  Delivery Day  Engrate Get
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
        '502':
          description: Engrate did not answer or refused the request.
      security:
        - APIKeyHeader: []
        - HTTPBearer: []
components:
  schemas:
    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
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key
    HTTPBearer:
      type: http
      description: OIDC access token (Auth0 M2M)
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.