Release notes

Partner API v1 baseline.

Changes listed here describe the public contract. Breaking changes require a versioned route or an announced deprecation path.

Partner API v1Public documentation

GET /api/partner/v1/catalog?locale=en
Authorization: Bearer fnx_test_...
Accept: application/json

Credential selects tenantSecrets stay server-sideBounded reads and retries

2026-08-18 - v1 baseline

Added scoped catalog, specialist and availability reads.
Added idempotent guest booking creation with opaque pbr_ references.
Documented the v1 single-service booking shape; composite booking remains a signed widget and first-party flow capability.
Added versioned cancel/reschedule management under business booking rules.
Added signed webhook delivery, retry evidence, pause/replay controls and strict destination validation.

Existing v1 fields and error codes are not silently repurposed.

New optional response fields may appear. Consumers must ignore unknown fields.

A new version or documented deprecation path is required before behavior is removed.

An incompatible change is released on a new versioned route or receives a public changelog notice that identifies the affected route or field, migration action and retirement date.
The retirement date and any support window are published with the deprecation. This documentation does not invent a fixed notice period or SLA.
Use the latest documented version, ignore unknown additive fields and monitor this changelog before changing a production integration.

Loading page