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

# List the delivery days the service holds

> Every delivery day currently stored, newest first, with the
`input_hash` of its submission and whether that exact input was
already processed downstream.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/forecasts
openapi: 3.1.0
info:
  title: n:lead Scheduling Bridge — Data Delivery API
  version: 0.4.0
  description: >-
    API for delivering portfolio data to the n:lead scheduling bridge. Send a
    portfolio forecast per delivery day, or — if no forecast is available — the
    market-location master data, metered data and rolled-out profiles the bridge
    needs to build the consumption forecast for you. Everything downstream
    (positions, trader handoff, schedule submission to the TSOs) is operated by
    n:lead. A read-only status endpoint reports the BRP activation state per
    DSO/MGA.
servers:
  - url: https://{host}
    description: Deployed service
    variables:
      host:
        default: >-
          nleadbridge-app.lemonisland-7d6503d3.germanywestcentral.azurecontainerapps.io
        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/forecasts:
    get:
      summary: List the delivery days the service holds
      description: |-
        Every delivery day currently stored, newest first, with the
        `input_hash` of its submission and whether that exact input was
        already processed downstream.
      operationId: list_forecasts_v1_forecasts_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ForecastListResponse'
        '401':
          description: Missing, wrong or expired credential.
        '413':
          description: Body larger than the request-size limit.
        '422':
          description: >-
            Validation failure. `detail` names the offending series/entry and
            the rule it broke - see the troubleshooting page for every message
            and its fix.
        '429':
          description: >-
            Rate limit exceeded - retry after the number of seconds in the
            `Retry-After` header.
        '503':
          description: >-
            Service restarting (deploy/scale) - transient. Wait the seconds in
            the `Retry-After` header and retry the identical request; retries
            are idempotent.
      security:
        - APIKeyHeader: []
        - HTTPBearer: []
      x-codeSamples:
        - lang: bash
          label: cURL
          source: >-
            curl "$NLEAD_BASE_URL/v1/forecasts" --header "X-API-Key:
            $NLEAD_API_KEY"
components:
  schemas:
    ForecastListResponse:
      properties:
        days:
          items:
            $ref: '#/components/schemas/ForecastDaySummary'
          type: array
          title: Days
      type: object
      required:
        - days
      title: ForecastListResponse
      description: The delivery days the service currently holds, newest first.
    ForecastDaySummary:
      properties:
        delivery_day:
          type: string
          format: date
          title: Delivery Day
        input_hash:
          type: string
          title: Input Hash
          description: >-
            Content hash of the stored submission - equals the `input_hash` of
            the acknowledgment that accepted it
        source:
          type: string
          title: Source
          description: >-
            "customer" for a submitted forecast, "generated" when the bridge
            built the day from mirrored data
        processed:
          type: boolean
          title: Processed
          description: >-
            True once the schedules for exactly this input were submitted
            downstream and accepted
      type: object
      required:
        - delivery_day
        - input_hash
        - source
        - processed
      title: ForecastDaySummary
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key
    HTTPBearer:
      type: http
      description: OIDC access token (Auth0 M2M)
      scheme: bearer

````