Skip to Content

Retired the legacy FuzeMetrix GET /member endpoint

Shipped 2026-08-26

GET /api/external/fuse-metrix/member/:memberId is removed. It was the last survivor of the pre-consolidation FuzeMetrix integration, and FuzeMetrix have confirmed they no longer call it — all traffic is on the v2 POST /api/external/fuse-metrix/get-member, which returns the same data.

Removing the route also removes the entire parallel stack that sat behind it: a second controller, service, repository and model that duplicated the modern booking flow while only getMember was ever reachable from a route. The req-validate-old middleware — a hand-rolled HMAC check separate from the shared req-validate — goes with it, as do the endpoint’s Bruno requests.

With that stack gone, the connectors_ifly_history audit table has no writer, and the last code reading the pre-TUN-661 fuse_metrix credentials table is gone.

Follow-up

Dropping the old per-vendor tables (fuse_metrix*, convergence*) and connectors_ifly_history ships as a separate deploy. Production migrations run as a DigitalOcean pre-deploy command, so schema changes land before the new code starts — bundling the drop with this removal would leave a window where the still-live legacy route queried tables that no longer existed.

Docs corrected alongside

  • The provisioning runbook’s direct-to-database shortcut still issued partner credentials with INSERT INTO fuse_metrix. Since TUN-661 the connector endpoints read connector filtered by vendor, so a credential provisioned that way was invisible to the live endpoints. It now targets connector (vendor = 'fuse_metrix').

  • The integration page’s schema section still published the retired per-vendor CREATE TABLE definitions; it now documents the shared connector_* set.

  • Jira: TUN-793 

  • PR: #905 

  • Author: @alexhobday

Last updated on