This page tracks notable changes to the v2 API specification. Entries are ordered newest-first. Subscribe to this page or check back regularly to stay informed about upcoming and recently shipped changes.

2.1.0 (2026-04-28)

• New optional locale field on POST /v2/reservations controls the language of confirmation, reminder, and cancellation emails sent to the guest. If omitted, the server uses the entity's default_locale. See the Localization guide for supported codes and resolution behavior.
• Entities now accept a default_locale (settable on create and update) that serves as the fallback locale for reservations that do not specify one. Defaults to en-US.
• New _Locale reusable schema: a BCP 47-style string enum with 22 supported locale codes, shared by reservation and entity endpoints.
• Seating area names are now constrained to a maximum of 32 characters across all responses that include a seating_area object.
• Documentation fix: the _Address schema's street fields are now correctly documented as line1 and line2 (previously shown as line_1 / line_2 in the spec). The actual API response has always used line1 / line2 — this only updates the spec to match.

2.0.0 (2026-02-26)

Initial v2 release.