The Fabrixa print on demand API lets any POD platform or storefront send an order, track its lifecycle through order.created and order.updated webhooks, and have Fabrixa print, pack and ship it white-label — from a single piece, right across the EU. You build the buying experience; we run reactive textile production behind it. No minimum order, no setup fees, no Fabrixa branding on the parcel.
This post is a plain-English overview of the Integration API (v2) for developers evaluating Fabrixa as a fulfilment layer. If you want to skim the reference instead, the full API documentation and step-by-step integration guide are ready when you are.
What the API is for
Fabrixa is a reactive textile print platform: one dashboard for sales channels, designs, production and dispatch. Most customers connect through Shopify, WooCommerce or Fabrixa Studio. The Integration API is the fourth route — built for POD platforms and developers who already own their storefront and want programmatic control over fulfilment.
You call the API to send orders. Fabrixa produces them: reactive print on cotton and linen in Portugal and Spain, sublimation on polyester in the Netherlands. Parcels ship under your brand, with your return address, and no Fabrixa marks anywhere on the package. Your customers never learn we exist unless you tell them.
What the API does
- Ping — a lightweight health check to confirm your credentials and connection are live before you send anything real.
- Products — read the catalogue you’re building on: apparel, home textiles and fabric by the metre, with the bases and variants available for print.
- Orders — create an order and read its state. This is the core of any integration: rows, sources, customer and shipping details go in; a tracked order comes back.
- Fulfilments — follow production and dispatch as items are made and shipped, so your platform can surface accurate status to sellers.
- Studio — attach a design personalised in Fabrixa Studio (our embeddable, white-label product customiser) to an order by its
cart_item_key, so what the buyer designed is exactly what gets printed.
Authentication and rate limits
The Integration API (v2) lives at the base URL https://api.fabrixa.com/v2/integration. Every request carries two headers:
| Header | Purpose |
|---|---|
Authorization: Bearer <token> |
Your API token — identifies and authorises the request. |
X-Application-Key: <key> |
Your application key — pairs with the token so both must be present. |
The rate limit is 30 requests per minute. That’s ample for order-driven traffic, but it means bulk operations should be paced rather than fired in a tight loop. Handle the limit gracefully, back off when you hit it, and lean on webhooks (below) instead of polling.
Webhooks: react to state, don’t poll for it
Rather than repeatedly asking “is it done yet?”, subscribe to webhooks and let Fabrixa tell you when something changes. The Integration API emits two events:
- order.created — fires when an order is accepted into production. Use it to confirm receipt back to your seller and mark the order as in progress.
- order.updated — fires as the order moves through production and dispatch, including tracking. Use it to keep your platform’s status in sync without burning through your rate limit.
Between two events and a 30-per-minute ceiling, a well-behaved integration barely touches the limit: send the order, then react to what comes back.
The order flow, end to end
Whichever route you choose, the shape is the same:
- Connect — a store (Shopify or WooCommerce) or the API.
- Design — personalise in Fabrixa Studio, or supply a print-ready PDF.
- Send the order — via the API, with product rows, customer and shipping address.
- We produce and dispatch — Fabrixa prints, packs and ships, white-label.
A quick note on quality, because it’s why sellers choose reactive: the reactive dye forms a covalent bond with the cellulose in cotton fibre and is fixed permanently under heat and steam. The colour becomes part of the fibre — no surface layer, no cracking at flex points — so it feels like unprinted cotton and typically holds colour for 600+ wash cycles. As a lead-time example, apparel made in Portugal is roughly 6–9 business days.
Why platforms build on Fabrixa
- MOQ 1 — from one piece to tens of thousands. No minimum order, no setup fees, no contracts.
- White-label by default — the customer’s brand on every parcel, not ours.
- Short EU supply chain — production across Portugal, Spain and the Netherlands, not long-haul freight.
- Real reactive print — GOTS-certified organic cotton as the default base, plus OEKO-TEX Standard 100 and Made in Green.
FAQ
Do I need to use Fabrixa Studio to use the API?
No. Studio is optional. You can send a print-ready PDF with the order instead. Studio only comes in when you want buyers to personalise a product in your storefront, and you attach that design to the order by cart_item_key.
How do I authenticate requests?
Send two headers on every call: Authorization: Bearer <token> and X-Application-Key: <key>. Both are required together — one without the other will be rejected.
What happens if I hit the rate limit?
The API caps at 30 requests per minute. If you exceed it, back off and retry rather than hammering the endpoint. For status changes, use the order.created and order.updated webhooks instead of polling — they keep you in sync without spending requests.
Is fulfilment really white-label?
Yes. Parcels ship under your brand with your return address and no Fabrixa branding as standard. Your end customers never see us.
Start building
The fastest way in is the integration guide, backed by the full API documentation. If you’d rather see how the whole thing fits together first, the platform overview walks through channels, Studio, production and dispatch. And if you’d like to pressure-test a fit for your platform, talk to our team — we’re happy to walk through your use case.
