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

# List Confirmed Schedules

> List the confirmed values of your schedules over a range of settlement periods.

Each record in `values` is one point of a series: the confirmation for one settlement period. It is the confirmation that the Scheduling Area Responsible has in force: the value it uses, or a rejection of the series. `values` has at most one record for each series and settlement period, in the sequence of `series_id`, then `isp_time`. A settlement period without a record has no confirmation that Engrate has recorded.

One request covers at most 32 days, thus a whole calendar month fits. [List Confirmed Schedule Series](/api-reference/timeseries/list-confirmed-schedule-series) gives the series and their parties.

The API gives the status code 422 in these conditions:

- `isp_until` is not after `isp_from`, or more than 32 days after it.

- A `series_id` filter is not a UUID, or a `kind` or `finality` filter has   an unknown value.

- A `series_id` or `scheduling_area` filter has more values than its   maximum.



## OpenAPI

````yaml /openapi.json get /market-access/v1alpha1/timeseries/confirmed-schedules
openapi: 3.1.0
info:
  title: Engrate API
  version: 1.0.0
servers:
  - url: https://api.engrate.io
security:
  - apiKeyAuth: []
paths:
  /market-access/v1alpha1/timeseries/confirmed-schedules:
    get:
      tags:
        - timeseries
      summary: List Confirmed Schedules
      description: >-
        List the confirmed values of your schedules over a range of settlement
        periods.


        Each record in `values` is one point of a series: the confirmation for
        one settlement period. It is the confirmation that the Scheduling Area
        Responsible has in force: the value it uses, or a rejection of the
        series. `values` has at most one record for each series and settlement
        period, in the sequence of `series_id`, then `isp_time`. A settlement
        period without a record has no confirmation that Engrate has recorded.


        One request covers at most 32 days, thus a whole calendar month fits.
        [List Confirmed Schedule
        Series](/api-reference/timeseries/list-confirmed-schedule-series) gives
        the series and their parties.


        The API gives the status code 422 in these conditions:


        - `isp_until` is not after `isp_from`, or more than 32 days after it.


        - A `series_id` filter is not a UUID, or a `kind` or `finality` filter
        has   an unknown value.


        - A `series_id` or `scheduling_area` filter has more values than its  
        maximum.
      operationId: >-
        list_confirmed_schedules_market_access_v1alpha1_timeseries_confirmed_schedules_get
      parameters:
        - description: Inclusive lower bound on the settlement period start (RFC 3339).
          in: query
          name: isp_from
          required: true
          schema:
            description: Inclusive lower bound on the settlement period start (RFC 3339).
            format: date-time
            title: Isp From
            type: string
        - description: >-
            Exclusive upper bound on the settlement period start (RFC 3339). It
            must be after `isp_from`, and at most 32 days after it.
          in: query
          name: isp_until
          required: true
          schema:
            description: >-
              Exclusive upper bound on the settlement period start (RFC 3339).
              It must be after `isp_from`, and at most 32 days after it.
            format: date-time
            title: Isp Until
            type: string
        - description: Series to read, by their `series_id`. Omit to read every series.
          in: query
          name: series_id
          required: false
          schema:
            anyOf:
              - items:
                  format: uuid
                  type: string
                maxItems: 500
                type: array
              - type: 'null'
            description: Series to read, by their `series_id`. Omit to read every series.
            title: Series Id
        - description: >-
            EIC codes of the scheduling areas to read, for example
            `10YDE-EON------1`. Omit to read every area.
          in: query
          name: scheduling_area
          required: false
          schema:
            anyOf:
              - items:
                  type: string
                maxItems: 500
                type: array
              - type: 'null'
            description: >-
              EIC codes of the scheduling areas to read, for example
              `10YDE-EON------1`. Omit to read every area.
            title: Scheduling Area
        - description: Kinds of confirmation to read. Omit to read every kind.
          in: query
          name: kind
          required: false
          schema:
            anyOf:
              - items:
                  enum:
                    - confirmed
                    - modified
                    - imposed
                    - rejected
                  type: string
                type: array
              - type: 'null'
            description: Kinds of confirmation to read. Omit to read every kind.
            title: Kind
        - description: >-
            Confirmation finalities to read. Use `final` to read only the values
            that settlement uses. Omit to read both.
          in: query
          name: finality
          required: false
          schema:
            anyOf:
              - items:
                  enum:
                    - intermediate
                    - final
                  type: string
                type: array
              - type: 'null'
            description: >-
              Confirmation finalities to read. Use `final` to read only the
              values that settlement uses. Omit to read both.
            title: Finality
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConfirmedSchedulesResponse'
          description: Successful Response
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
components:
  schemas:
    ConfirmedSchedulesResponse:
      properties:
        values:
          items:
            $ref: '#/components/schemas/ConfirmedScheduleRecord'
          title: Values
          type: array
      required:
        - values
      title: ConfirmedSchedulesResponse
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      type: object
    ConfirmedScheduleRecord:
      description: >-
        The confirmation that is in force for one series at one settlement
        period.
      properties:
        finality:
          description: >-
            The confirmation finality. It is `intermediate` if the confirmation
            can change, and `final` if settlement uses it.
          enum:
            - intermediate
            - final
          examples:
            - final
          title: Finality
          type: string
        isp_resolution_minutes:
          description: >-
            The length of the ISP in minutes. This is usually 15, 30 or 60,
            depending on the market.
          title: Isp Resolution Minutes
          type: integer
        isp_time:
          description: >-
            The start of the Imbalance Settlement Period (ISP), as an ISO 8601
            timestamp in UTC, for example `2026-01-01T00:00:00Z`.
          examples:
            - '2026-10-14T22:00:00Z'
          format: date-time
          title: Isp Time
          type: string
        kind:
          description: >-
            This is `confirmed` if the Scheduling Area Responsible uses your
            value. It is `modified` if the Scheduling Area Responsible uses a
            different value. It is `imposed` if the Scheduling Area Responsible
            sets a value for a series or position that you did not send. It is
            `rejected` if the Scheduling Area Responsible rejected the series,
            and uses no value of it at this settlement period.
          enum:
            - confirmed
            - modified
            - imposed
            - rejected
          examples:
            - confirmed
          title: Kind
          type: string
        known_at:
          description: >-
            When Engrate received the match report that set this confirmation,
            as an ISO 8601 timestamp in UTC.
          format: date-time
          title: Known At
          type: string
        schedule_uid:
          description: The schedule of the delivery day that holds the series.
          format: uuid
          title: Schedule Uid
          type: string
        scheduling_area:
          description: >-
            The EIC of the scheduling area of the schedule. An external series
            is in the schedules of both its areas, and the Scheduling Area
            Responsible of each area confirms it separately. Thus it is a
            different series in each area.
          examples:
            - 10YDE-EON------1
          title: Scheduling Area
          type: string
        series_id:
          description: >-
            The key of the series. It stays the same on each delivery day. Use
            it to find the series in List Confirmed Schedule Series.
          format: uuid
          title: Series Id
          type: string
        stated_at:
          description: >-
            When the Scheduling Area Responsible stated the confirmation, as an
            ISO 8601 timestamp in UTC.
          format: date-time
          title: Stated At
          type: string
        volume_wh:
          anyOf:
            - type: integer
            - type: 'null'
          description: >-
            The energy in Wh that the Scheduling Area Responsible uses for the
            settlement period. It is `null` if the `kind` is `rejected`.
          title: Volume Wh
      required:
        - finality
        - isp_resolution_minutes
        - isp_time
        - kind
        - known_at
        - schedule_uid
        - scheduling_area
        - series_id
        - stated_at
        - volume_wh
      title: ConfirmedScheduleRecord
      type: object
    ValidationError:
      properties:
        ctx:
          title: Context
          type: object
        input:
          title: Input
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          title: Location
          type: array
        msg:
          title: Message
          type: string
        type:
          title: Error Type
          type: string
      required:
        - loc
        - msg
        - type
      title: ValidationError
      type: object
  securitySchemes:
    apiKeyAuth:
      in: header
      name: Authorization
      type: apiKey

````

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