[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-pagerduty-rest-openapi-2026-05-18-schedules-v3-early-access-header-requirement-removed-ga":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"pagerduty-rest-openapi","PagerDuty REST API","pagerduty","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002FPagerDuty\u002Fapi-schema\u002Fmain\u002Freference\u002FREST\u002Fopenapiv3.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KRXSN7YXE54FD3SJX2JQ5S57","2026-05-18-schedules-v3-early-access-header-requirement-removed-ga","Breaking","Schedules_v3 Early Access header requirement removed (GA promotion)","The `X-EARLY-ACCESS: flexible-schedules-early-access` required header parameter has been removed from all **Schedules_v3** endpoints, and the \"Early Access\" warning notices have been stripped from all endpoint descriptions. This means the API is no longer in early access — clients that were conditionally sending this header no longer need to, but more importantly, clients that were **not** sending it (because the API was gated) can now call these endpoints freely. However, if any server-side enforcement still exists in the opposite direction (rejecting the old header), existing integrations that send it would break; treat this as a potentially breaking change for existing early-access integrations.","2026-05-18T15:00:49.757Z"]