01
Import the collection
In Postman: File → Import → Link. Paste the JSON URL from the download button above. Postman adds the collection — with its variables — to your workspace.
Developers · Postman collection
Import the collection. Hit the API in five minutes.
A pre-built Postman collection with worked examples for the Fabrixa Integration API. Drop in your credentials, click through the requests, and see real responses against the API before you write a single line of integration code. Tracked across versions — the collection updates when the API does.
What’s in the collection
Every endpoint, with example payloads.
Organised into folders by resource. Each request ships with a worked example body, the two auth headers pre-set, and a saved example response — so you can preview the response shape before you fire.
Auth & products
- GET /ping — verify credentials
- GET /products — list & paginate (SKU + variant_id)
- Full field schemas in the Swagger reference
Orders
- POST /orders — create an order
- GET /orders/{id}/fulfillments — track production
Studio & webhooks
- GET /v2/studio/customizations/{key}/preview
- Webhook payload + HMAC verification (example)
Import in 30 seconds
File → Import → Link → paste URL.
02
Open the Variables tab
The collection ships with its own variables — base_url is pre-filled; access_token and application_key are placeholders. No separate environment file needed.
03
Paste your keys
Drop in the Application Access Token and Application Key from a sales channel in your dashboard, hit Save, and every request authenticates.
Environment variables
What’s in the env file.
One base URL, two credentials, baked into the collection. Build against one sales channel, then paste your live channel’s keys when you ship — same collection, same requests.
Collection variables
{
"base_url": "https://api.fabrixa.com/v2/integration",
"studio_base": "https://api.fabrixa.com/v2/studio",
"access_token": "APPLICATION_ACCESS_TOKEN",
"application_key": "APPLICATION_KEY"
}
Auth pre-configured
Both auth headers, pre-set on every request.
Every request carries Authorization: Bearer {{access_token}} and X-Application-Key: {{application_key}}, pulled from the collection variables — no per-request header setup. Switching from one sales channel to another is just editing those two variables: same collection, different keys.
Worked examples
Each request ships with a sample body and saved response.
The collection isn’t just URL stubs — every request has a worked example body, so you can hit Send and see real data. Saved example responses sit in the Examples panel for offline reference.
Verify auth
Confirms your Application Access Token and Application Key are valid before anything else. 200 on success, 401 if a header is missing.
List products
Paginated catalogue request. Returns products page-by-page in the links / meta / data envelope, with SKU and variant id per item.
Create an order
Sample body for a one-unit T-shirt order with a source PDF, customer and shipping address. Hit Send to see the created order with its Fabrixa id.
Track production
Pulls per-item production steps (print, fix, wash, sew) with pending / in progress / done / rejected states for a placed order.
Studio preview
Returns the rendered preview image for a saved Studio customisation — drop it straight into a cart thumbnail.
Signature check
A worked example of recomputing the HMAC-SHA256 signature and comparing it to x-webhook-signature before processing.
Versioning
The collection updates when the API does.
Every API release ships an updated collection at the same URL. Re-import to pick up new endpoints and example payloads — existing requests in your saved version keep working until that endpoint actually deprecates.
Stable URL
The collection JSON URL is permanent. Re-importing pulls the latest version — the URL never changes between releases.
Changelog reference
See the changelog for the matching API version notes — what moved, what was added, what’s deprecating.
Deprecation policy
Endpoints get a 12-month deprecation window. The collection flags deprecated requests in the description so they’re hard to miss before anything breaks.
FAQ
The Postman collection, answered
How do I import the Fabrixa Postman collection?
In Postman, choose File, then Import, then Link, and paste the collection's JSON URL. Postman adds the collection along with its variables to your workspace — base_url is pre-filled, while access_token and application_key are placeholders you replace with your own Application Access Token and Application Key.
What endpoints are included in the Fabrixa Postman collection?
The collection covers GET /ping to verify credentials, GET /products to list and paginate the catalogue, POST /orders to create an order, GET /orders/{id}/fulfillments to track production, the Studio preview endpoint, and a worked webhook signature verification example. It is built for the v2 Integration API and requires Postman v10 or later.
How is authentication set up in the Fabrixa Postman collection?
Every request in the collection already carries the two required headers — Authorization: Bearer {{access_token}} and X-Application-Key: {{application_key}} — pulled from the collection's variables. Pasting your Application Access Token and Application Key into those variables authenticates every request at once, with no per-request setup.
Does the Fabrixa Postman collection update when the API changes?
Yes — every API release ships an updated collection at the same permanent URL, so re-importing pulls the latest endpoints and example payloads. Endpoints get a 12-month deprecation window, and the collection flags deprecated requests in their description before anything breaks.
What does the GET /orders/{id}/fulfillments request return?
It pulls the per-item production status for a placed order, covering steps such as print, fix, wash, and sew, each reported as pending, in progress, done, or rejected. The Postman collection includes a worked example so the response shape can be checked before it is wired into an integration.
Download & start
Grab the collection. Fire your first request.
Import the collection, drop in your sales-channel credentials and send your first request in minutes — no integration code required to start exploring.