Account
- GET /v1/account — verify auth, view tier
- GET /v1/account/usage — current period usage
- PUT /v1/account/webhook — set webhook URL + events
Pre-built Postman collection with worked examples for every Fabrixa REST endpoint. Drop in your API key, click through the requests, see the actual responses against the sandbox before you write a single line of integration code. Tracked across versions — the collection updates when the API does.
POSTMAN v10+ · SANDBOX + PRODUCTION ENVS · UPDATED EVERY API RELEASE
Organised into folders by resource: Account, Products, Orders, Webhooks, Editor SDK. Each request comes with a worked example body, headers pre-set, and an example successful response saved — so you can preview the response shape before you fire.
In Postman: File → Import → Link. Paste the JSON URL from the download button above. Postman fetches and adds the collection to your workspace.
Same flow, environment URL: .../fabrixa-api.postman_environment.json. Sets up the variable scaffolding (base URL, API key placeholder).
Open the imported environment, fill FABRIXA_API_KEY with your sandbox key. Switch to the production env when you’re ready to ship.
# Sandbox environment { "FABRIXA_BASE_URL": "https://sandbox.api.fabrixa.com/v1", "FABRIXA_API_KEY": "sk_sandbox_yourKeyHere", "FABRIXA_PUBLIC_KEY": "pk_sandbox_yourPublicKey", "FABRIXA_WEBHOOK_URL": "https://your-tunnel.ngrok.io/webhook" } # Production environment (separate file) { "FABRIXA_BASE_URL": "https://api.fabrixa.com/v1", "FABRIXA_API_KEY": "sk_live_yourKeyHere", "FABRIXA_PUBLIC_KEY": "pk_live_yourPublicKey", "FABRIXA_WEBHOOK_URL": "https://api.yourbrand.com/webhook" }
The collection’s Authorization tab is configured to inherit the API key from the active environment. Every request inside the collection picks it up automatically — no per-request header config.
Switching from sandbox to production is one click on the environment dropdown. Same collection, different keys, different base URL. No code changes needed.
The collection isn’t just URL stubs — every request comes with a worked example body so you can hit Send and see real data. Saved example responses are visible in the Examples panel for offline reference.
Sample body for a 2-unit T-shirt order with custom artwork URL, recipient address, and idempotency key. Hit Send to see a 201 Created response with order_id.
Pre-filtered query for the apparel category. Returns the catalogue page-by-page with sizes, GSM, lead time, and pricing tier per SKU.
Manually fire a sample webhook event to your registered URL. Useful for debugging webhook handlers without placing a real order.
Current billing period usage, tier-progression status, projected end-of-period volume. Useful for capacity planning before a big drop.
Cancel an order before it locks production (typically within 24h of placement). Returns 409 if production has already started — idempotency key handles retries.
Preview unit pricing across the volume tiers for a given SKU. Useful for showing customers the per-unit savings as they scale order quantity.
Every Fabrixa API release ships an updated Postman collection at the same URL. Re-import to pick up new endpoints and example payloads — existing requests in your saved version stay working until that endpoint actually deprecates.
The collection JSON URL is permanent. Re-importing pulls the latest version. The URL never changes between API releases.
See Changelog for the matching API version notes — what moved, what was added, what’s deprecating.
Endpoints get a 12-month deprecation window. The collection flags deprecated requests in the description so they’re hard to miss before things break.
Import URL: https://www.fabrixa.com/wp-content/themes/brighthub-fabrixa/assets/downloads/fabrixa-api.postman_collection.json