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
Most-recent first. Each entry is dated, semver-tagged, and broken into the standard categories: Added / Changed / Deprecated / Removed / Fixed / Security.
GET /v1/products/:id/pricing — preview unit pricing across volume tiers per SKU.production_hub field (PT or ES). Backwards compatible.order.failed webhook event with structured error reasons (artwork rejection, fabric out-of-stock, etc.).GET /v1/orders when filtering by status across page boundaries.GET /v1/products?category=home-living.artwork_base64 field on order body — use artwork_url. Removal target: v1.20.0 (2027-03-28).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.
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.
Backwards-compatible additions. Existing code keeps working without changes. Most releases are minor. Cadence ~2-4 weeks.
Strictly non-breaking. Deployed continuously without prior announcement. Logged in changelog after deployment.
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.
Standard RSS feed of changelog entries. Useful for embedding in internal eng dashboards or aggregating with other supplier-changelog feeds.
Subscribe a URL to receive JSON POST per release. Handy for automatically opening tickets, posting to Slack, or running compatibility checks against staging.
Subscribe an alias (eg. eng-alerts@yourbrand.com) to release announcements + deprecation reminders. Filterable by major / minor / patch.
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.
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.
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.
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.
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.
English English 
Nederlands
Français
Deutsch
Italiano
Português
Español
Українська
