Every API release. Every breaking change. Logged.
Fabrixa ships API and platform updates on a predictable cadence. Every release lands here first — what changed, what’s new, what’s deprecating, and when it actually breaks. Check here before you upgrade.
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.
- CHANGEDBreaking: base path moved to
/v2/integration. The v1 endpoints are superseded — existing v1 integrations keep working through the deprecation window; see the integration guide. - CHANGEDBreaking: authentication is now two headers —
Authorization: Bearer(Application Access Token) plusX-Application-Key. Single-token v1 auth is no longer accepted. - ADDEDFabrixa Studio — embeddable white-label product customiser: embed via iframe, attach a saved design to an order row with
cart_item_key, and pull a preview from/v2/studio/customizations/{key}/preview. - CHANGEDStandard response envelope on list endpoints:
links/meta/datawith pagination links. - CHANGEDWebhooks consolidated to
order.createdandorder.updated, signed withx-webhook-signature(HMAC-SHA256) and tagged withx-webhook-topic. - CHANGEDRate limit set to 30 requests per application per minute, surfaced via
X-RateLimit-LimitandX-RateLimit-Remainingheaders.
- ADDED
GET /v1/products/:id/pricing— preview unit pricing across volume tiers per SKU. - CHANGEDOrder webhook payload now includes a
production_hubfield (PT, ES or NL). Backwards compatible.
- ADDEDFive-mode personalisation pipeline on bedding, table linens and accessories: text, name, numbers, images and dynamic data fields.
- ADDED
order.failedwebhook event with structured error reasons (artwork rejection, fabric out of stock, and similar). - FIXEDPagination edge case on
GET /v1/orderswhen filtering by status across page boundaries.
- ADDEDOutdoor cushion, tablecloth and sitting-bag SKUs for synthetic outdoor use. Available via
GET /v1/products?category=home-living. - DEPRECATED
artwork_base64field on the order body — supply a source-file URL instead. Removal target: v1.20.0 (2027-03-28). - SECURITYWebhook signature scheme hardened. The previous HMAC variant stays valid through v1.18.0; new signing is applied automatically going forward.
- ADDEDBedding category (duvet covers 1P / 2P / Lits Jumeaux, bed spreads, fitted sheets) on the Spanish hub.
- ADDEDSublimation napkin SKUs on the Dutch hub with a 2–3 business-day SLA.
- CHANGEDOrder endpoint now accepts
recipient.countryas ISO 3166-1 alpha-2; the alpha-3 fallback was removed.
Older releases available on request — email developers@fabrixa.com.
SemVer, with conservative breaking changes.
Breaking changes to existing endpoints
Rare. Announced 12 months ahead of release. The old major stays supported for 12 months after the new major ships. We don’t cut majors lightly.
New endpoints, fields, behaviour
Backwards-compatible additions. Existing code keeps working without changes. Most releases are minor, on a roughly two-to-four-week cadence.
Bug fixes, performance, security
Strictly non-breaking. Deployed continuously without prior announcement, and logged in the changelog after deployment.
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 and date. The deprecated functionality keeps working for at least 12 months after the notice.
We send three reminder notifications — six months, three months and one month before removal — to the email address on file for the API key.
Deprecated endpoints also return an X-Fabrixa-Deprecation response header pointing at the migration path, so it’s visible in your logs.
How to keep track of changes.
No feeds to wire up — this page is the source of truth. Here’s how to stay ahead of anything that affects your integration.
Check here first
Every release lands on this page, most-recent at the top. Bookmark it and scan before you upgrade a dependency or ship a new integration.
A clear runway
When something is sunsetting, its entry is tagged DEPRECATED with the removal target version and date — advance notice, in context.
Ask about a change
Planning around a change or a major-version migration? A solutions engineer can walk you through timing and impact for your integration.
When breaking changes can ship.
Major version cuts are scheduled into specific windows so they don’t land on top of customer drop dates or peak retail seasons. Most years see zero major-version cuts.
February and September are the typical breaking-change windows — both post-major-retail-season and pre-peak, which gives integrators time to migrate before their next big drop.
November–December (holiday retail), March–May (Fespa and 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.
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 in their MSA, plus early access to the new major on a staging sales channel 90 days before public availability.
Check here before you upgrade.
Every release lands here first — what changed, and when it breaks. Deprecations come with a runway, and major-version cuts come with migration support.