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

# Update a schedule

> Use this endpoint to update an existing reconciliation schedule. You can modify the cron expression and enabled status.



## OpenAPI

````yaml /en/openapi/v3-current/matcher.yaml patch /v1/contexts/{contextId}/schedules/{scheduleId}
openapi: 3.1.0
info:
  title: Matcher APIs
  description: >-
    Complete API reference for the Matcher reconciliation engine, providing
    automated transaction matching between Midaz Ledger and external systems.
  version: v2.1.1
  license:
    name: Elastic License 2.0
    url: https://www.elastic.co/licensing/elastic-license
servers:
  - url: https://matcher.sandbox.lerian.net
security: []
paths:
  /v1/contexts/{contextId}/schedules/{scheduleId}:
    patch:
      tags:
        - Configuration Schedules
      summary: Update a schedule
      description: >-
        Use this endpoint to update an existing reconciliation schedule. You can
        modify the cron expression and enabled status.
      operationId: updateSchedule
      parameters:
        - description: A unique identifier for tracing the request across services.
          in: header
          name: X-Request-Id
          schema:
            type: string
        - description: The unique identifier of the reconciliation context.
          in: path
          name: contextId
          required: true
          schema:
            type: string
        - description: The unique identifier of the schedule.
          in: path
          name: scheduleId
          required: true
          schema:
            type: string
        - $ref: '#/components/parameters/XIdempotencyKey'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateScheduleRequest'
        description: Fields to update
        required: true
      responses:
        '200':
          description: >-
            Schedule updated.


            The response includes the `X-Idempotency-Replayed` header.


            If the value is false, the request was just processed. If the value
            is true, the response is a replay of a previously processed request.


            See [Retries and idempotency](/en/reference/retries-idempotency) for
            more details.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ScheduleResponse'
          headers:
            X-Idempotency-Replayed:
              $ref: '#/components/headers/XIdempotencyReplayed'
        '400':
          description: The request contains invalid parameters or payload.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: The request lacks valid authentication credentials.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: You do not have permission to access this resource.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Schedule not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: An unexpected error occurred on the server.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - BearerAuth: []
components:
  parameters:
    XIdempotencyKey:
      name: X-Idempotency-Key
      in: header
      required: false
      description: >-
        Optional idempotency key for safe retries. Also accepts
        `Idempotency-Key` as an alternative header name. If the same key is sent
        again and the original request was already processed, the cached
        response is returned with `X-Idempotency-Replayed: true`.


        See [Retries and idempotency](/en/reference/retries-idempotency) for
        details.
      schema:
        type: string
  schemas:
    UpdateScheduleRequest:
      description: Payload for updating a reconciliation schedule
      properties:
        cronExpression:
          description: Updated cron expression
          example: 0 6 * * *
          maxLength: 100
          type: string
        enabled:
          description: Updated enabled status
          example: false
          type: boolean
      type: object
    ScheduleResponse:
      description: Cron-based reconciliation schedule
      properties:
        id:
          description: Unique identifier for the schedule
          example: 019c96a0-2b20-7123-9a1b-2c3d4e5f6a7b
          format: uuid
          type: string
        contextId:
          description: Context this schedule belongs to
          example: 019c96a0-2a10-7dfe-b5c1-8a1b2c3d4e5f
          format: uuid
          type: string
        cronExpression:
          description: Cron expression defining the schedule
          example: 0 0 * * *
          maxLength: 100
          type: string
        enabled:
          description: Whether the schedule is active
          example: true
          type: boolean
        lastRunAt:
          description: Last successful run time in RFC 3339 format
          example: '2025-01-15T10:30:00Z'
          format: date-time
          type: string
        nextRunAt:
          description: Next scheduled run time in RFC 3339 format
          example: '2025-01-16T00:00:00Z'
          format: date-time
          type: string
        createdAt:
          description: Creation timestamp in RFC 3339 format
          example: '2025-01-15T10:30:00Z'
          format: date-time
          type: string
        updatedAt:
          description: Last update timestamp in RFC 3339 format
          example: '2025-01-15T10:30:00Z'
          format: date-time
          type: string
      type: object
    ErrorResponse:
      description: Standard error response returned by all API endpoints
      type: object
      required:
        - code
        - title
        - message
      properties:
        code:
          type: string
          description: HTTP status code as a string.
          example: '404'
        title:
          type: string
          description: Error type identifier.
          example: not_found
        message:
          type: string
          description: Human-readable error message with details.
          example: context not found
        error:
          type: string
          description: Deprecated. Error message for backward compatibility.
          deprecated: true
        details:
          description: Additional error context as key-value pairs
          additionalProperties: {}
          type: object
  headers:
    XIdempotencyReplayed:
      description: >-
        Indicates whether this response was served from the idempotency cache.
        When `true`, the response is a replay of the original request with the
        same idempotency key.


        See [Retries and idempotency](/en/reference/retries-idempotency) for
        details.
      schema:
        type: boolean
      example: false
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: 'Bearer token authentication (format: "Bearer {token}")'

````