API CHANGE TRACKER / PagerDuty

PagerDuty breaking change: PUT /v3/schedules/{id}

Validated schema comparison changed the request accepted instance set.

Specification capture: 2026-09-30 UTC. Published evidence last updated 2026-11-03 UTC. This is captured contract evidence, not an observed outage or a result from scanning your code.

Which field and classification rule changed?

Changed field

Operation-level change

Rule ID

schema.request_acceptance_narrowed

Classifier version

2026-10-15.2

Direction

request

Finding ID

chg_cff38f49d5aa455e2e67c624020f89e47a118e320baf0d92da31223c4169e9a3

What is the recorded before and after evidence?

Previous specification SHA-256: 6c19f1f4b622e7d098e0a5a5f5ce04afdc0a21a5b9c1cb7b1649a594e88f2345

Revised specification SHA-256: 46bd6195063f262aef3b13de96e7c206d5c6f3e6aa79154c5655cce436b584db

Publisher version: 2.0.0 to 2.0.0.

No before/after schema excerpt is available in this bounded snapshot. Use the source revisions and public finding to inspect the contract; no replacement behavior is inferred here.

Inspect the complete release · Public source findings · Publisher specification source

How do I check whether this affects my code?

Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.

Check an authorized repository · Review coverage · Inspect classification rules