REST API
api.fabrixa.com
Order placement, product catalogue, account management. The endpoint your integration depends on for every order.
Developers · System status
Live status, SLA targets, and how we handle incidents.
The operational status of every Fabrixa service: REST API, webhook delivery, Fabrixa Studio, production lines in Portugal, Spain and the Netherlands, and dispatch. Subscribe via email or webhook for incident notifications. SLA targets, response policy and the historical uptime record are below.
Monitored services
Six services tracked separately.
Independent uptime tracking per service. The live dashboard at status.fabrixa.com reflects the current state — the labels below are descriptive, not real-time on this page.
Webhook delivery
outbound event delivery
Outbound webhook fan-out: order.created / order.updated, retry queue, HMAC signature. Scaled independently of the inbound API.
Fabrixa Studio
studio.fabrixa.com
Embeddable product customiser (iframe): saved customisations and preview rendering. White-label inside your end-customer-facing storefronts.
Production hubs
PT · ES · NL
Print-line capacity in Portugal, Spain and the Netherlands. Reported as a degraded indicator on queue backup — not a binary up/down.
Dispatch
carrier handoff
Tracking-number issuance and carrier handoff. Carrier-specific status fed back from our shipping partners.
Dashboard
account.fabrixa.com
Account dashboard for keys, billing, audit logs and manual order placement. Secondary to the API for production traffic.
SLA targets
What we publicly commit to.
Public targets for the standard tier. Enterprise customers get higher SLAs written into their MSA — talk to our team. We track against these targets monthly and publish the actual uptime.
99.9%
Monthly availability target on the REST API and webhook delivery.
<400ms
p95 response time on the order-creation endpoint, measured from EU regions.
99.5%
Successful delivery of order lifecycle events within 60 seconds of the state transition. Up to 10 retry attempts before the endpoint is disabled.
Incident response
How we handle outages.
Public incident reporting on the live dashboard. Subscribers get email or webhook notifications within five minutes of an incident being declared, updates every 30 minutes during the incident, and a post-mortem within five business days of resolution.
01
Detection
Internal monitoring alerts engineering within seconds of degradation. The public dashboard moves to “investigating” within five minutes of a confirmed incident.
02
Communication
Subscribed customers are notified on their preferred channel — email or webhook — with updates every 30 minutes minimum during the incident window.
03
Resolution + post-mortem
Resolution status is posted live. A public post-mortem follows within five business days: what happened, root cause, and what we’re changing to prevent recurrence.
Subscribe
Three ways to get notified.
Email
For ops / eng team aliases
Subscribe a team alias (e.g. ops@yourcompany.com) to incident notifications. Filter by service if you only care about specific subsystems.
Webhook
For automated paging
Receive incident events as a JSON POST to your incident-management system. Pipe straight into PagerDuty, Opsgenie or Slack via an incoming webhook.
RSS / Atom
For dashboard widgets
An RSS feed of all incidents and updates — handy for embedding on internal status dashboards or aggregating with other supplier-status feeds.
Scheduled maintenance
Notice windows for planned work.
Maintenance windows are announced at least seven days ahead. Typical maintenance is rolling and zero-downtime; high-impact maintenance is rare, scheduled in low-traffic windows and announced 14 days ahead.
Rolling / zero-downtime
Most upgrades and infrastructure changes deploy without downtime — rolling restarts, blue/green database changes, gradual rollout. Announced as informational on the status page; no customer-side action required.
High-impact maintenance
Rare; reserved for major migrations or invasive infrastructure changes. Announced 14 days ahead via email, webhook and a status banner. Scheduled Sun 03:00–05:00 CET, with a maximum two-hour expected impact window.
Enterprise SLA
Higher targets, written into the MSA.
The standard targets above are public commitments. Enterprise customers — 10,000+ units a month, multi-property hospitality groups, or platform integrations — get higher SLAs written into the Master Supply Agreement, plus dedicated incident-escalation paths, reserved production capacity and named technical account management. Talk to our team for enterprise SLA terms, dedicated-capacity options and the MSA template.
Check before you debug
Live status: status.fabrixa.com
Anything looking flaky in your integration? Check the live status dashboard before opening a support ticket — most short-lived disruptions resolve before a ticket gets seen.