Update a schedule
Use this endpoint to update an existing reconciliation schedule. You can modify the cron expression and enabled status.
Authorizations
Bearer token authentication (format: "Bearer {token}")
Headers
A unique identifier for tracing the request across services.
Optional idempotency key for safe retries. Matcher reads the key only from this header, and only when you send one. A request that carries a key only in X-Idempotency-Key or Idempotency-Key is refused with 400 (MTCH-0015), and nothing is processed. If the same key is sent again and the original request was already processed, the stored response is returned with X-Idempotency-Replayed: true. A malformed key returns 400, a key whose first request is still in progress returns 409, and an idempotency storage failure returns 500. These refusals are problem documents.
Path Parameters
The unique identifier of the reconciliation context. Context ID
The unique identifier of the schedule. Schedule ID
Body
Fields to update
Response
Schedule updated.
Identifier of the context this schedule belongs to.
"550e8400-e29b-41d4-a716-446655440000"
Creation timestamp in RFC 3339 format.
"2025-01-15T10:30:00Z"
Cron expression (5-field) defining when the reconciliation runs.
"0 0 * * *"
Whether the schedule is active.
true
Unique identifier of the schedule.
"550e8400-e29b-41d4-a716-446655440000"
Last update timestamp in RFC 3339 format.
"2025-01-15T10:30:00Z"
Timestamp of the last successful run in RFC 3339 format; omitted if it has never run.
"2025-01-15T10:30:00Z"
Timestamp of the next scheduled run in RFC 3339 format; omitted when disabled.
"2025-01-16T00:00:00Z"

