Developer docs

Changelog

What changed in the public API, the JavaScript and .NET SDKs and the WordPress plugin, release by release, newest first.

Curated from the GitHub releases: only what an integration can notice is listed, and internal, console and infrastructure changes are left out. Versions are the vX.Y.Z tags; the same version names the CDN path, the NuGet packages and the WordPress zip of that release (Versions and releases).

v0.7.0 — 2026-09-16

  • Docs — Tutorials: Booking flow (what the widget does end to end) and Azure Static Web Apps (zero to a live venue page); this changelog. No change to the public API, the SDKs or the WordPress plugin.

v0.6.0 — 2026-09-16

  • API — Every /api/venues/** call requires an API key: a publishable bdp_pk_… key from an allowed origin in the browser, a secret bdp_sk_… key on a server. A missing, wrong or misused key is refused with one of six RFC 7807 problem types (Authentication, Errors).
  • API — Booking lengths are configurable per resource type: the venue profile lists bookingDurations, availability and reservations accept durationMinutes, and availability echoes the length its slots represent.
  • API — Availability and reservation creation resolve a resource's own booking length the same way, so a slot that was offered can no longer be refused for its length; a party that needs several resources is grouped identically by both calls.
  • APIphone on reservation creation is optional: 3–40 characters when given, and a blank value counts as not supplied.
  • JavaScript SDK — Published on the CDN: sdk/<version>/bookdineplay.js (immutable, with an SRI hash in sri.txt next to it) and sdk/v0/bookdineplay.js (five-minute alias). renderBookingWidget now requires publishableKey and takes theme (auto, light, dark); nine --bdp-* custom properties theme the widget from the host page; window.BookDinePlay.version names the loaded release (JavaScript SDK, Theming).
  • JavaScript SDKdurationMinutes is sent only when the guest picked a length; the venue's default applies otherwise.
  • .NET SDKBookDinePlay.Sdk and BookDinePlay.Shared are on nuget.org, versioned in lockstep with the release (.NET SDK).
  • WordPress — The plugin ships as bookdineplay-<version>.zip on the release, loads the SDK from the v0 alias, stores the publishable key under Settings → BookDinePlay, and the shortcode gains a key attribute (WordPress plugin).
  • Docs — This site.

v0.5.0 — 2026-09-09

  • No change to the public API, the SDKs or the WordPress plugin. Operator console only.

v0.4.1 — 2026-09-02

  • No change to the public API, the SDKs or the WordPress plugin. Operator console only.

v0.4.0 — 2026-07-23

  • API — Messages and problem responses are localized: send Accept-Language: de for German title and detail; English is the default (Errors). The guest's confirmation email uses the language of the request that created the reservation.
  • API — Bookable extras: the venue profile lists extras; a reservation accepts extras: [{ "extraId": "…", "quantity": 1 }] and returns priced extras lines and extrasTotal.
  • API — Per-game pricing: a slot can carry pricingModel: "PerGame"; a reservation accepts and returns games (1–10).
  • API — Group bookings: a party too large for one resource is offered a group slot (groupResourceCount, groupResourceNames); the reservation returns groupReference and groupResources.
  • API — New resource type BowlingLane; food ordering is a per-resource setting (allowsFoodOrdering on resources).
  • JavaScript SDK, WordPressBowlingLane in the resource-type list and in the plugin's default types; the widget collects games per player and extras where the venue offers them.

Releases before v0.4.0 predate the public integration paths and are not listed.