Fake Incident & Status Page API

Q: Do resolved incidents restore their components?

Yes. Every affected component is operational when status is resolved; unresolved component states are derived from impact.

Q: Can I guarantee that a component is affected?

Yes. Set component; it is included exactly once, and componentCount still determines the exact distinct total.

MOCK DATA

Generate coherent status-page incidents with affected components, ordered updates, exact lifecycle dates and impact/status filters.

Generated test data for fixtures and development

Base URL: /api/incidents
Category: Developer Tools
Capabilities: 1 route Seedable
Last updated: July 29, 2026

GET /api/incidents Generate bounded fictional incident timelines Returns a list

Live requestRuns against the public API

No key required

GET/api/incidents?status=monitoring&impact=major&component=api&componentCount=3&count=6&seed=42

Request parameters

status

Pin the exact lifecycle progress and nullable-date mask.

impact

Pin minor, major or critical impact and derived component state.

component

Guarantee this component is included exactly once.

componentCountdefault 2

Exact number of distinct affected components.

from

Earliest creation time. With only from, to resolves 30 elapsed days later; with neither, defaults 30 UTC days before today.

to

Latest creation time. With only to, from resolves 30 elapsed days earlier; with neither, defaults to today's UTC end.

Advanced response options7 options

countdefault 10

How many records to generate (1–100).

seed

Deterministic output: the same seed always returns the same records. Omit for random (the used seed is echoed in meta.seed).

fields

Return only these fields (comma-separated). Mutually exclusive with 'exclude'.

exclude

Return all fields except these (comma-separated).

formatdefault json

Response format: json envelope, ndjson (one record per line) or csv.

prettydefault false

Pretty-print the JSON response.

unwrapdefault false

Drop the envelope: return the raw array/object without data/meta wrapper.

Response

Example parameters are ready. Send the request to inspect the live response.

Route reference

Code, request parameters, response fields and verified examples 13 params · 13 fields · 3 examples

Code samples Ready-to-copy requests in 4 languages

curl JavaScript Python PHP

curl "https://randomapi.dev/api/incidents?component=api&impact=major&status=monitoring&componentCount=3&count=6&seed=42"

const res = await fetch("https://randomapi.dev/api/incidents?component=api&impact=major&status=monitoring&componentCount=3&count=6&seed=42");
const { data, meta } = await res.json();

import requests

data = requests.get("https://randomapi.dev/api/incidents?component=api&impact=major&status=monitoring&componentCount=3&count=6&seed=42").json()["data"]

$json = json_decode(file_get_contents(
  "https://randomapi.dev/api/incidents?component=api&impact=major&status=monitoring&componentCount=3&count=6&seed=42"
), true);
$data = $json["data"];

Parameters Route-specific request inputs 6

Parameter	Type	Default & allowed	Description
`status`	enum	allowed: investigating \| identified \| monitoring \| resolved example: monitoring	Pin the exact lifecycle progress and nullable-date mask.
`impact`	enum	allowed: minor \| major \| critical example: major	Pin minor, major or critical impact and derived component state.
`component`	enum	allowed: api \| dashboard \| webhooks \| uploads \| billing \| authentication example: api	Guarantee this component is included exactly once.
`componentCount`	int	default: 2 allowed: 1 – 4 example: 3	Exact number of distinct affected components.
`from`	date	example: 2026-04-01	Earliest creation time. With only from, to resolves 30 elapsed days later; with neither, defaults 30 UTC days before today.
`to`	date	example: 2026-04-30T23:59:59.999Z	Latest creation time. With only to, from resolves 30 elapsed days earlier; with neither, defaults to today's UTC end.

status enum

Pin the exact lifecycle progress and nullable-date mask.

allowed: investigating | identified | monitoring | resolved

example: status=monitoring

impact enum

Pin minor, major or critical impact and derived component state.

allowed: minor | major | critical

example: impact=major

component enum

Guarantee this component is included exactly once.

example: component=api

componentCount int

Exact number of distinct affected components.

default: 2

allowed: 1 – 4

example: componentCount=3

from date

Earliest creation time. With only from, to resolves 30 elapsed days later; with neither, defaults 30 UTC days before today.

example: from=2026-04-01

to date

Latest creation time. With only to, from resolves 30 elapsed days earlier; with neither, defaults to today's UTC end.

example: to=2026-04-30T23:59:59.999Z

Universal parameters Shared response and formatting options 7

Parameter	Type	Default & allowed	Description
`count`	int	default: 10 allowed: 1 – 100 example: 3	How many records to generate (1–100).
`seed`	int	example: 42	Deterministic output: the same seed always returns the same records. Omit for random (the used seed is echoed in meta.seed).
`fields`	list	example: id,title	Return only these fields (comma-separated). Mutually exclusive with 'exclude'.
`exclude`	list	example: updates	Return all fields except these (comma-separated).
`format`	enum	default: json allowed: json \| ndjson \| csv example: csv	Response format: json envelope, ndjson (one record per line) or csv.
`pretty`	boolean	default: false example: true	Pretty-print the JSON response.
`unwrap`	boolean	default: false example: true	Drop the envelope: return the raw array/object without data/meta wrapper.

count int

How many records to generate (1–100).

default: 10

allowed: 1 – 100

example: count=3

seed int

Deterministic output: the same seed always returns the same records. Omit for random (the used seed is echoed in meta.seed).

example: seed=42

fields list

Return only these fields (comma-separated). Mutually exclusive with 'exclude'.

example: fields=id,title

exclude list

Return all fields except these (comma-separated).

example: exclude=updates

format enum

Response format: json envelope, ndjson (one record per line) or csv.

default: json

allowed: json | ndjson | csv

example: format=csv

pretty boolean

Pretty-print the JSON response.

default: false

example: pretty=true

unwrap boolean

Drop the envelope: return the raw array/object without data/meta wrapper.

default: false

example: unwrap=true

Response schema Fields returned in each record 13

Field	Type	Description	Example
`id`	string	Distinct fictional incident ID.	inc_72d9ae192c00_00
`title`	string	Synthetic impact/component summary.	Major disruption affecting Public API
`status`	string	investigating \| identified \| monitoring \| resolved.	monitoring
`impact`	string	minor \| major \| critical.	major
`createdAt`	string (ISO 8601)	Incident start inside from/to.	2026-04-12T09:00:00.000Z
`updatedAt`	string (ISO 8601)	Exactly the final update timestamp.	2026-04-12T10:20:00.000Z
`identifiedAt` nullable	string (ISO 8601)	Present from identified onward.	2026-04-12T09:20:00.000Z
`monitoringAt` nullable	string (ISO 8601)	Present from monitoring onward.	2026-04-12T10:20:00.000Z
`resolvedAt` nullable	string (ISO 8601)	Present only when resolved.	null
`durationMinutes` nullable	integer	Exact createdAt→resolvedAt minutes, else null.	null
`url`	string (URL)	Fictional status.example.com incident URL.	https://status.example.com/incidents/inc_demo
`affectedComponents`	object[]	One to four distinct components with status derived from impact/lifecycle.	[{"id":"api","name":"Public API","status":"partialOutage"}]
`updates`	object[]	One to four chronological updates ending at top-level status.	[{"id":"upd_demo_1","status":"investigating","message":"Investigating fictional errors affecting Public API.","createdAt":"2026-04-12T09:00:00.000Z"}]

id string

Distinct fictional incident ID.

example: inc_72d9ae192c00_00

title string

Synthetic impact/component summary.

example: Major disruption affecting Public API

status string

investigating | identified | monitoring | resolved.

example: monitoring

impact string

minor | major | critical.

example: major

createdAt string (ISO 8601)

Incident start inside from/to.

example: 2026-04-12T09:00:00.000Z

updatedAt string (ISO 8601)

Exactly the final update timestamp.

example: 2026-04-12T10:20:00.000Z

identifiedAt string (ISO 8601) nullable

Present from identified onward.

example: 2026-04-12T09:20:00.000Z

monitoringAt string (ISO 8601) nullable

Present from monitoring onward.

example: 2026-04-12T10:20:00.000Z

resolvedAt string (ISO 8601) nullable

Present only when resolved.

example: null

durationMinutes integer nullable

Exact createdAt→resolvedAt minutes, else null.

example: null

url string (URL)

Fictional status.example.com incident URL.

example: https://status.example.com/incidents/inc_demo

affectedComponents object[]

One to four distinct components with status derived from impact/lifecycle.

example: [{"id":"api","name":"Public API","status":"partialOutage"}]

updates object[]

One to four chronological updates ending at top-level status.

example: [{"id":"upd_demo_1","status":"investigating","message":"Investigating fictional errors affecting Public API.","createdAt":"2026-04-12T09:00:00.000Z"}]

Documented examples

Build-generated requests and complete responses 3

Major API incidents under monitoring /api/incidents?component=api&impact=major&status=monitoring&componentCount=3&count=6&seed=42

GET /api/incidents?component=api&impact=major&status=monitoring&componentCount=3&count=6&seed=42

{
  "data": [
    {
      "id": "inc_016cfb6a5c85eac5_00",
      "title": "Major disruption affecting Public API",
      "status": "monitoring",
      "impact": "major",
      "createdAt": "2026-07-15T09:42:36.290Z",
      "updatedAt": "2026-07-15T12:28:36.290Z",
      "identifiedAt": "2026-07-15T10:51:36.290Z",
      "monitoringAt": "2026-07-15T12:28:36.290Z",
      "resolvedAt": null,
      "durationMinutes": null,
      "url": "https://status.example.com/incidents/inc_016cfb6a5c85eac5_00",
      "affectedComponents": [
        {
          "id": "api",
          "name": "Public API",
          "status": "partialOutage"
        },
        {
          "id": "billing",
          "name": "Billing",
          "status": "partialOutage"
        },
        {
          "id": "dashboard",
          "name": "Dashboard",
          "status": "partialOutage"
        }
      ],
      "updates": [
        {
          "id": "inc_016cfb6a5c85eac5_00_u1",
          "status": "investigating",
          "message": "Investigating fictional errors affecting Public API, Billing, Dashboard.",
          "createdAt": "2026-07-15T09:42:36.290Z"
        },
        {
          "id": "inc_016cfb6a5c85eac5_00_u2",
    …
    "generatedAt": "2026-07-29T08:13:22.000Z"
  }
}

Resolved critical incidents /api/incidents?status=resolved&impact=critical&count=10&seed=17

GET /api/incidents?status=resolved&impact=critical&count=10&seed=17

{
  "data": [
    {
      "id": "inc_bf24f73252bc1d36_00",
      "title": "Critical disruption affecting Billing",
      "status": "resolved",
      "impact": "critical",
      "createdAt": "2026-07-19T21:36:36.878Z",
      "updatedAt": "2026-07-19T23:47:36.878Z",
      "identifiedAt": "2026-07-19T21:46:36.878Z",
      "monitoringAt": "2026-07-19T22:28:36.878Z",
      "resolvedAt": "2026-07-19T23:47:36.878Z",
      "durationMinutes": 131,
      "url": "https://status.example.com/incidents/inc_bf24f73252bc1d36_00",
      "affectedComponents": [
        {
          "id": "billing",
          "name": "Billing",
          "status": "operational"
        },
        {
          "id": "api",
          "name": "Public API",
          "status": "operational"
        }
      ],
      "updates": [
        {
          "id": "inc_bf24f73252bc1d36_00_u1",
          "status": "investigating",
          "message": "Investigating fictional errors affecting Billing, Public API.",
          "createdAt": "2026-07-19T21:36:36.878Z"
        },
        {
          "id": "inc_bf24f73252bc1d36_00_u2",
          "status": "identified",
          "message": "A synthetic dependency issue affecting Billing, Public API has been identified.",
          "createdAt": "2026-07-19T21:46:36.878Z"
        },
        {
    …
    "generatedAt": "2026-07-29T08:13:22.000Z"
  }
}

Investigations created in April /api/incidents?status=investigating&from=2026-04-01&to=2026-04-30&count=8&seed=8

GET /api/incidents?status=investigating&from=2026-04-01&to=2026-04-30&count=8&seed=8

{
  "data": [
    {
      "id": "inc_d10ec498125864a0_00",
      "title": "Major disruption affecting Webhook delivery",
      "status": "investigating",
      "impact": "major",
      "createdAt": "2026-04-19T07:41:12.152Z",
      "updatedAt": "2026-04-19T07:41:12.152Z",
      "identifiedAt": null,
      "monitoringAt": null,
      "resolvedAt": null,
      "durationMinutes": null,
      "url": "https://status.example.com/incidents/inc_d10ec498125864a0_00",
      "affectedComponents": [
        {
          "id": "webhooks",
          "name": "Webhook delivery",
          "status": "partialOutage"
        },
        {
          "id": "api",
          "name": "Public API",
          "status": "partialOutage"
        }
      ],
      "updates": [
        {
          "id": "inc_d10ec498125864a0_00_u1",
          "status": "investigating",
          "message": "Investigating fictional errors affecting Webhook delivery, Public API.",
          "createdAt": "2026-04-19T07:41:12.152Z"
        }
      ]
    },
    {
      "id": "inc_1d0f2fb232511ae2_01",
      "title": "Critical disruption affecting File uploads",
      "status": "investigating",
      "impact": "critical",
    …
    "generatedAt": "2026-07-29T08:13:22.000Z"
  }
}

About this API

Coverage, behavior and common use cases

Coverage & behavior

Generates fictional operational incidents for status pages, service-health dashboards and incident timelines. Every record follows one strict progression: investigating → identified → monitoring → resolved. The selected top-level status controls exactly how much of that sequence exists and which nullable timestamps are present.

impact controls every affected component's current condition: minor incidents use degraded performance, major incidents use partial outage, critical incidents use major outage, and resolved incidents restore every component to operational. component guarantees one named component is included, while componentCount fixes the exact distinct total. from/to constrain incident creation.

Updates, names and URLs are synthetic. Every URL uses reserved example.com, messages explicitly call the event fictional/synthetic, and the object makes no status-page vendor compatibility claim. Update arrays are capped at four, so generation and response size stay bounded.

Use it for

Populate a public status page with every incident state
Test incident update timelines and affected-component badges
Create reproducible outage fixtures without implying a real service failure

Frequently asked questions

Practical answers about this endpoint 4

Do incident updates follow a valid order?

Yes. Every incident starts at investigating and includes each lifecycle update exactly once up to the selected top-level status.

Do resolved incidents restore their components?

Yes. Every affected component is operational when status is resolved; unresolved component states are derived from impact.

Can I guarantee that a component is affected?

Yes. Set component; it is included exactly once, and componentCount still determines the exact distinct total.

Are these records from a real monitoring service?

No. Titles, updates, component states and example.com URLs are explicitly fictional fixtures with no vendor compatibility claim.

Standards & references

Primary sources behind the contract

RFC 2606 — Reserved Top Level DNS Names

Useful next tools in the catalog

Fake Audit Log API MOCK DATA

Generate coherent fake audit records for authentication, CRUD and permission changes — safely seeded, filterable and bounded by time.

Fake Task & Todo Data API MOCK DATA

Developer-productivity task fixtures with working status, priority, assignment, due-date and tag filters plus coherent subtasks and blockers.

Current Time API REAL DATA

Current time in any IANA timezone — UTC instant, unix seconds, local date & time, UTC offset, ISO week, day of year and a live DST flag.

Fake Calendar Events API MOCK DATA

Generate coherent fake calendar events with bounded durations, attendees, IANA timezones and correct timed or all-day date shapes.