Order placement, product catalogue, account management. The endpoint your integration depends on for every order.

Outbound webhook fan-out. Order lifecycle events, retry queue, signature verification. Independently scaled from inbound API.

Customisation editor canvas, asset upload pipeline, artwork composition service. Affects end-customer-facing brand sites.

Print line capacity in Portugal and Spain. Reported as a degraded indicator if there’s queue backup; not a binary up/down.

Carrier handoff and tracking-number issuance. Carrier-specific status fed back from DHL, UPS, GLS, and regional partners.

Account dashboard for keys, billing, audit logs, manual order placement. Internal-tool, secondary to the API for production traffic.

Monthly availability target on REST API and webhook delivery.

p95 response time on order-creation endpoint, measured from EU regions.

Successful delivery of order lifecycle events within 60 seconds of state transition. Retries up to 24h on failure.

Internal monitoring alerts engineering within seconds of degradation. Public dashboard transitions to "investigating" within 5 minutes of confirmed incident.

Subscribed customers receive notifications via their preferred channel (email or webhook). Updates every 30 minutes minimum during the incident window.

Resolution status posted live. Public post-mortem within 5 business days — what happened, root cause, what we’re changing to prevent recurrence.

For ops/eng team aliases

Subscribe a team alias (eg. eng@yourbrand.com) to incident notifications. Filter by service if you only care about specific subsystems.

For automated paging

Receive incident events as JSON POST to your incident-management system. Pipe straight into PagerDuty, Opsgenie, Slack via incoming webhook.

For dashboard widgets

RSS feed of all incidents and updates — useful for embedding on internal status dashboards or aggregating with other supplier-status feeds.

Most upgrades and infrastructure changes are deployed without downtime — rolling restarts, blue/green database changes, gradual rollout. Announced as informational on the status page; no customer-side action required.

Rare; reserved for major migrations or invasive infrastructure changes. Announced 14 days ahead via email + webhook + status banner. Scheduled Sun 03:00–05:00 CET. Maximum 2 hours expected impact window.