Status

Developers

Status API and webhooks

Read StoreConnect status from your own tools. The JSON endpoints are public and read-only, send CORS headers, and are cached for 60 seconds.

Base URL: https://status.storeconnect.com

Endpoints and feeds

Status summary

GET/api/v1/summary

The overall system status, every component with its current status, and active (unresolved) incidents.

Example response
{
  "status": {
    "indicator": "none",
    "description": "All Systems Operational"
  },
  "components": [
    {
      "id": "abc123",
      "name": "Store Availability",
      "status": "operational",
      "description": "...",
      "groupId": null,
      "isGroup": false,
      "position": 0
    }
  ],
  "incidents": [
    {
      "id": "def456",
      "name": "DNS Latency",
      "type": "incident",
      "status": "investigating",
      "impact": "minor",
      "createdAt": "2026-04-14T01:00:00.000Z",
      "updatedAt": "2026-04-14T01:05:00.000Z"
    }
  ]
}

Recent incidents

GET/api/v1/incidents

The 50 most recent incidents and maintenance windows, active and resolved, newest first.

Example response
{
  "incidents": [
    {
      "id": "def456",
      "name": "DNS Latency",
      "type": "incident",
      "status": "resolved",
      "impact": "minor",
      "affectedComponentIds": ["abc123"],
      "createdAt": "2026-04-14T01:00:00.000Z",
      "updatedAt": "2026-04-14T02:00:00.000Z",
      "resolvedAt": "2026-04-14T02:00:00.000Z",
      "scheduledFor": null,
      "scheduledUntil": null
    }
  ]
}

Atom feed

GET/history.atom

Atom 1.0 feed of the 50 most recent incidents, for any feed reader.

RSS feed

GET/history.rss

RSS 2.0 feed of the 50 most recent incidents, for any feed reader.

Webhook notifications

Instead of email, subscribe an HTTPS endpoint and we'll POST incident updates to it as JSON. Every request uses the same flat seven-field payload, so it works with Slack Workflow Builder, Microsoft Teams incoming webhooks, Zapier, n8n or your own service. Subscribe a webhook

Payload fields

Every POST has these seven fields, in this order. Use type to tell verification posts from incident updates. Unused fields are empty strings, never omitted.

FieldDescription
titleIncident name, or a short summary for verification posts.
type"Incident", "Maintenance", or "Verification".
status"Investigating", "Identified", "Monitoring", "Resolved", "Scheduled", "In Progress", "Verifying", "Completed", or "Pending verification".
impact"None", "Minor", "Major", "Critical", or empty for verification posts.
messageUpdate text. For verification posts it includes the code and instructions.
urlIncident URL, or the subscribe page URL for verification posts.
unsubscribeurlPer-subscriber opt-out link on incident updates. Empty on verification posts.

Verification post

Sent once when you submit a webhook URL. Take the code from message (or title) and enter it on the subscribe page to prove you own the endpoint. The code expires in 15 minutes, and nothing else is sent until you verify.

{
  "title": "StoreConnect Status verification code: A7K2QM",
  "type": "Verification",
  "status": "Pending verification",
  "impact": "",
  "message": "Your StoreConnect Status subscription verification code is A7K2QM. Paste it into https://status.storeconnect.com/subscribe to confirm this webhook. The code expires in 15 minutes.",
  "url": "https://status.storeconnect.com/subscribe",
  "unsubscribeurl": ""
}

Incident update post

Sent whenever we publish an incident or maintenance update with “Notify subscribers” turned on, for incidents that affect a system you subscribed to.

{
  "title": "DNS Latency",
  "type": "Incident",
  "status": "Investigating",
  "impact": "Minor",
  "message": "We're seeing elevated DNS lookup times in ap-southeast-2. Investigating now.",
  "url": "https://status.storeconnect.com/incidents/def456",
  "unsubscribeurl": "https://status.storeconnect.com/subscribe?action=unsubscribe&token=..."
}

Endpoints must be HTTPS. We don't follow redirects, requests time out after 10 seconds, and non-2xx responses are logged but not retried, so keep your endpoint resilient.

Set up a Slack workflow

Post incident updates to a Slack channel in about two minutes with Workflow Builder.

  1. In Slack, open Tools → Workflow Builder, select New Workflow, and choose From a webhook as the trigger.
  2. Add these seven text variables. The names must match the payload keys exactly:
    • title
    • type
    • status
    • impact
    • message
    • url
    • unsubscribeurl
  3. Add a Send a message step. Set the destination channel in the step itself (don't map a variable to it), and use the variables in the message, for example:
    *<{{url}}|{{title}}>*
    {{type}} · {{status}} · {{impact}} impact
    
    {{message}}
  4. Publish the workflow and copy its https://hooks.slack.com/triggers/… URL.
  5. Paste the URL into the subscribe page under Webhook. We'll post a verification code to the channel; enter it to finish subscribing.

Tip: send updates to a shared channel such as #status-updates rather than a DM so the whole team sees them.

Unsubscribing

Every incident update carries a per-subscriber unsubscribeurl. Open it in a browser to remove the subscription straight away. On verification posts the field is empty because no subscription exists yet.

Embeddable widgets

Framework-agnostic web components you can drop into any page.

Status badge

Shows the overall system status and links to this page.

<script src="https://status.storeconnect.com/embed/status.js"></script>
<storeconnect-status></storeconnect-status>

Subscribe widget

An inline email sign-up form for status updates.

<script src="https://status.storeconnect.com/embed/subscribe.js"></script>
<storeconnect-subscribe></storeconnect-subscribe>