deleteNamedSchedule
DELETE/agents/:agentId/schedules/:scheduleId
Requires agents:manage. Deterministic stored configuration only; no worker/network/provider reachability evidence. New mutations require API_CONFIGURATION_ENABLED, Idempotency-Key and (except schedule creation) an exact If-Match ETag. Current authority precedes retained replay; matching replay returns the original outcome before testing its historical conditional revision. Disable/delete do not cancel an admitted occurrence. Setup controls require a member-issued key; service credentials may only use explicitly granted named schedules.
Request
Responses
- 204
- 400
- 403
- 404
- 409
- 412
- 428
- 500
- 503
No response body
Response Headers
Present when Idempotency-Key is used: false for the original response, true for a replay.
Opaque retained receipt ID. Outcome lookup is available for covered G02 member and allowed G01 service operations.
Original protected response expiry.
Server-generated synchronous HTTP correlation; no worker lineage implied.
Invalid request body or query parameters. Field errors may be returned as arrays.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Missing/invalid API key, insufficient scope, account eligibility, or communication policy denial.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Resource not found or not accessible to this API key.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Idempotency key reused for a different request, or an incompatible resource state.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Configuration revision changed; reload before using a new retry key.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
If-Match is required for existing-resource mutations.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
Unexpected failure; JSON includes detail and an error_id for support.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.
configuration_unavailable: New REST configuration admission is disabled; authorized replay survives this gate.
Response Headers
Server-generated synchronous HTTP correlation; no worker lineage implied.