Skip to main content

Changelog

Fabrixa platform changelog — API releases, integrations, and platform updates
DEVELOPERS — CHANGELOG

Every API release. Every breaking change. Logged.

Fabrixa ships API and platform updates on a predictable cadence. Every release goes here with what changed, what’s new, what’s deprecating, and when it actually breaks. Subscribe via RSS or webhook to get notified before you find out the hard way.

SEMANTIC VERSIONING · 12-MONTH DEPRECATION WINDOW · RSS / WEBHOOK / EMAIL

RECENT RELEASES

What changed in the last few weeks.

Most-recent first. Each entry is dated, semver-tagged, and broken into the standard categories: Added / Changed / Deprecated / Removed / Fixed / Security.

v1.18.0

2026-05-02
CURRENT
  • ADDED Editor SDK v1: embeddable customisation editor with theming, event hooks, and signed artwork upload pipeline. See SDK page.
  • ADDED GET /v1/products/:id/pricing — preview unit pricing across volume tiers per SKU.
  • CHANGED Order webhook payload now includes production_hub field (PT or ES). Backwards compatible.

v1.17.0

2026-04-15
  • ADDED 5-mode personalisation pipeline on bedding, table linens, accessories: text, name, numbers, images, dynamic data fields.
  • ADDED order.failed webhook event with structured error reasons (artwork rejection, fabric out-of-stock, etc.).
  • FIXED Pagination edge case on GET /v1/orders when filtering by status across page boundaries.

v1.16.0

2026-03-28
  • ADDED Outdoor cushion + tablecloth + sitting bag SKUs in poly-acrylic with pigment AOP. Available via GET /v1/products?category=home-living.
  • DEPRECATED artwork_base64 field on order body — use artwork_url. Removal target: v1.20.0 (2027-03-28).
  • SECURITY Webhook signature scheme hardened — previous HMAC variant remains valid through v1.18.0; new signing applied automatically going forward.

v1.15.0

2026-03-10
  • ADDED Bedding category (duvet covers 1P / 2P / Lits Jumeaux, bed spreads, fitted sheets) on Spanish hub.
  • ADDED Sublimation napkin SKUs on Dutch hub with 2-3 day SLA.
  • CHANGED Order endpoint now accepts recipient.country as ISO 3166-1 alpha-2; previously accepted ISO 3166-1 alpha-3 fallback removed.

Older releases available on request — email support@fabrixa.com.

VERSIONING POLICY

SemVer with conservative breaking changes.

MAJOR (1.x → 2.x)

Breaking changes to existing endpoints

Rare. Announced 12 months ahead of release. Old major version remains supported for 12 months after the new major ships. We don’t cut majors lightly.

MINOR (1.18 → 1.19)

New endpoints, new fields, new behaviour

Backwards-compatible additions. Existing code keeps working without changes. Most releases are minor. Cadence ~2-4 weeks.

PATCH (1.18.0 → 1.18.1)

Bug fixes, performance, security

Strictly non-breaking. Deployed continuously without prior announcement. Logged in changelog after deployment.

DEPRECATION POLICY

12 months from deprecation notice to removal.

When we deprecate a field, endpoint, or behaviour, the changelog entry tags it DEPRECATED and lists the removal target version + date. The deprecated functionality keeps working for at least 12 months after the deprecation notice.

We send three reminder notifications (6 months / 3 months / 1 month before removal) to the email address on file for the API key. Deprecated endpoints also return an X-Fabrixa-Deprecation header pointing at the migration path.

Fabrixa platform release update — changelog and feature announcements
SUBSCRIBE

Three ways to track releases.

RSS / ATOM

For feed readers + dashboards

Standard RSS feed of changelog entries. Useful for embedding in internal eng dashboards or aggregating with other supplier-changelog feeds.

WEBHOOK

For automated handling

Subscribe a URL to receive JSON POST per release. Handy for automatically opening tickets, posting to Slack, or running compatibility checks against staging.

EMAIL

For team aliases

Subscribe an alias (eg. eng-alerts@yourbrand.com) to release announcements + deprecation reminders. Filterable by major / minor / patch.

BREAKING CHANGE WINDOWS

When breaking changes can ship.

Major version cuts are scheduled into specific release windows so they don’t land on top of customer drop dates or peak retail seasons. Most years see zero major-version cuts.

SAFE WINDOWS

February and September are the typical breaking-change windows. Both are post-major-retail-season and pre-peak: gives integrators time to migrate before their next big drop.

PROTECTED WINDOWS

November-December (holiday retail), March-May (Fespa & spring drops), and the two weeks before known industry events are no-breaking-change windows. Patch releases continue but no minor or major behaviour changes.

Fabrixa platform versioning — API and integration release notes
MIGRATION SUPPORT

Solutions engineering walks integrators through the major bumps.

For major version cuts, we publish a migration guide alongside the release notes. Solutions engineering also runs free 30-minute migration office hours for any active integration partner during the deprecation window — book via the contact-engineer page.

Enterprise customers get dedicated migration support inside their MSA and early access to the new major version on their sandbox environment 90 days before public availability.

Stay up to date with Fabrixa platform releases — API changelog and integration updates
STAY CURRENT

Subscribe before something breaks.

Pick the channel that fits your team’s workflow. Every release lands here first. Deprecations come with a 12-month runway. Major version cuts come with migration support.

Cart (0 items)

Create your account