Skip to content

Integrations

Status API and feeds

Read Moraph service status from your own systems with the JSON API, the Atom feed and the maintenance calendar: endpoints, example responses and errors.

Applies to Moraph Status as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. Authentication
  2. Available interfaces
  3. Example: the summary
  4. Fields
  5. Example: recent incidents
  6. Errors and edge cases
  7. Client notices

The status page publishes machine-readable status so you can show Moraph’s service health in your own dashboards, monitoring or chat tools.

Authentication

None. The API and feeds are public, read-only and send Access-Control-Allow-Origin: *, so you can call them from a browser.

Available interfaces

Method and pathWhat it returnsCached
GET /api/v1/summary.jsonOverall state, every service and region with its state, open incidents and maintenanceUp to 30 seconds
GET /api/v1/incidents.jsonThe 50 most recent incidents, with their updatesUp to 30 seconds
GET /feed.atomAtom feed of incident and maintenance updates (up to 50 entries); ?component=<id> for one service
GET /maintenance.icsiCalendar feed of upcoming maintenance and the last 90 days

All paths are on https://status.moraph.com. Please poll no more than once a minute.

Example: the summary

http
GET /api/v1/summary.json HTTP/1.1
Host: status.moraph.com
Accept: application/json
json
{
  "page": { "name": "Moraph Status", "url": "https://status.moraph.com/" },
  "overall": "degraded",
  "overall_label": "Some services have degraded performance",
  "updated_at": "2026-10-14T09:31:00Z",
  "generated_at": "2026-10-14T09:31:12Z",
  "components": [
    { "id": "portal", "name": "Portal", "group": "client", "state": "degraded", "label": "Degraded performance",
      "source": "automated", "checked_at": "2026-10-14T09:31:00Z", "url": "https://status.moraph.com/components/portal" },
    { "id": "region-uk", "name": "United Kingdom", "group": "regions", "state": "operational", "label": "Operational",
      "source": "operations", "checked_at": null, "url": "https://status.moraph.com/components/region-uk" }
  ],
  "incidents": [
    { "id": "INC-4K7QPD", "title": "Slow page loads in the portal", "impact": "degraded", "status": "identified",
      "started_at": "2026-10-14T09:05:00Z", "updated_at": "2026-10-14T09:28:00Z", "components": ["portal"],
      "url": "https://status.moraph.com/incidents/INC-4K7QPD" }
  ],
  "maintenance": []
}

The values above are an illustration of the format, not a real incident.

Fields

FieldValues
statusThe same value as overall, for clients that expect that name
components[].hostFor monitored web properties: the Moraph host it checks (portal, app, support, …)
components[].productFor products: the catalog slug, the same one used in Moraph Docs and Apps URLs
overall, components[].stateoperational, maintenance, degraded, partial, major or unknown (no current data; state_reason says why: nodata, delayed, unreported). Show overall_label and each component's label to people.
components[].groupclient, web, products (with vertical), regions
components[].sourceautomated (checked automatically) or operations (reported by Operations)
incidents[].statusinvestigating, identified, monitoring, resolved
incidents[].impactdegraded, partial, major
maintenance[].statusscheduled, in_progress, completed, cancelled
TimesISO 8601 in UTC

Use label and overall_label when you show states to people; they match the wording on the status page.

Example: recent incidents

http
GET /api/v1/incidents.json HTTP/1.1
Host: status.moraph.com

Each incident has id, title, impact, status, started_at, resolved_at, customer_impact, resolution, postmortem_url, components, url and updates (each with status, body and created_at, newest first).

Errors and edge cases

What you seeMeaningWhat to do
"stale": true with stale_sinceThe status database was briefly unreachable, so this is the last saved copy.Use it, and try again shortly.
HTTP 5xxThe status service itself is having trouble.Retry with backoff; don’t treat it as a Moraph outage on its own.
A component ID you used has goneServices can be added or renamed.Read IDs from the summary rather than hard-coding them.

Client notices

Notices that concern only your organization are never in the public API. They appear in the Moraph Portal.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.