Changelog

Changes that affect integrations are listed here, newest first. Additive changes — a new endpoint, a new optional field, a new event type or a new change.reason value — can ship at any time within v1, so write integrations that ignore fields and values they do not recognise.

27 September 2026#

Technology Providers. Platforms that serve many Localoy partners — ticketing, point-of-sale and booking systems — can now integrate once and act for every partner who connects them. The new Technology Providers book documents it:

• Provider keys (ltp_sbx_… and ltp_live_…), issued by Localoy, and the X-Localoy-Partner-Id header that names the partner a call is for.
• Connection codes: a partner connects a provider from the Partner Portal and hands it a one-time code, which the provider claims with POST /connections/claim.
• A fifth scope, BOOKINGS, that partners can grant only to providers. A partner's API key cannot hold it.
• Self-service webhook endpoints for providers, and two new events, connection.updated and connection.revoked, that only providers can subscribe to.
• Catalogue items now carry managedBy, naming the Technology Provider or store sync that manages them.
• GET /ping now returns principal: PARTNER or TECHNOLOGY_PROVIDER.

26 September 2026#

Documentation published. This site documents version v1 of the Open Network API:

• Authentication with sandbox and production API keys, and four scopes.
• The catalogue: create, list, read, update and delete items, and link them to bookables.
• Payment sessions: read a session, report a result, record a refund.
• Webhooks for bookings, payments and catalogue changes, signed with HMAC-SHA256.
• Live inventory checks from Localoy to your system.