OnSched API 3.23.0 — Schedule-only appointment override
Schedule-only appointment override
Authenticated company-scoped callers can pass
availabilityMode=schedule_override on appointment create, hold, reserve,
book, reschedule, and resource-validation requests. The mode allows booking
outside operating hours, allocation windows, and clinic/resource schedule
blocks. It also allows overlap with another appointment's padding-only
interval.
The mode continues to enforce actual appointment and hold occupancy against
configured capacity, the candidate appointment's own padding tail, service
quotas, customer booking limits, and normal external-calendar checks. It does
not change GET /v3/availability and is not available on public booking routes.
Holds and reservations carry the mode through booking, and rescheduled IN/RS
appointments retain it for a later book when the mode is passed on reschedule.
The existing ignoreAvailability=true option keeps its broad behavior. The two
modes cannot be combined in one request. See the Appointments Guide.
Explicit service links
POST /v3/service and POST /v3/service/bulk link only the resource ids in the query. An omitted locations query on a COMPANY-scoped service still links every company location. An empty or blank locations value, including locations=, links no locations. An omitted, empty, or blank resources value links no resources.
This is a behavior change. Callers should pass resources explicitly or use the opt-in. linkAllResources=true on a COMPANY-scoped service, with no resource ids, links every company resource. Explicit resource ids still win. The flag does nothing for other scopes, and the default stays no auto-link. An invalid linkAllResources value returns 400 on both create and bulk create, and bulk create does not insert those services.
Association conflicts
POST /v3/location/{id}/setAssociations accepts optional expectedServices and expectedResources. POST /v3/service/{id}/setAssociations and POST /v3/resource/{id}/setAssociations accept optional expectedLocations. A null, a string, or an invalid UUID in expectedLocations returns 400 and changes nothing. When a snapshot is sent, the current links must still match or the API returns 409 ASSOCIATION_CONFLICT and changes nothing. An omitted relation is left as it is. An empty array clears that relation. Omitting the expected field keeps the previous unconditional replacement.
Company Sync no longer adds locations onto a service that already exists. An empty resource services list links the services at that resource's locations, and does not fall back to every company service. A missing or null list still adds none and records a Sync gap, "resource services list missing; retry Company Sync". A repeat sync does not add those links again. The locations form resets its expected baseline when you switch the open service or resource, so the next save uses that entity's locations.
Consumer availability rate limit
A consumer availability read that computes slots directly spends the same company availability budget as GET /v3/availability, once per request. An empty budget returns 429 with Retry-After.
