Schedules_v3 Early Access header requirement removed (GA promotion)
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
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.