# Prism Crisis Postmortem API (https://www.socialcrawl.dev/platforms/prism/crisis-postmortem)

> Reconstructs a crisis window: content_analysis phrase-trends (volume curve) + anger-ordered search + reddit (sort=new) + hackernews (client-side date-filtered so stale relevance-ranked posts cannot corrupt the chronology) + search/everywhere (items_by_source cross-platform spread), merged into one chronologically-sorted event timeline with the first credible origin, the peak day, and the platform-by-platform propagation order. Pass include= (empty) to drop the LLM narrative and get the raw timeline. Origin is chosen only from natively-dated events (a lagged crawl time cannot establish who-said-it-first). Supply brand plus window_start; window_end defaults to today. Flat 35 credits; losing more than half the timeline sources refunds half.

TL;DR: `GET /v1/prism/crisis-postmortem` costs 35 credits per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `brand` | yes | The brand or entity the crisis is about (required). |
| `window_start` | no | Start of the crisis window (YYYY-MM-DD) — the earliest point on the timeline. Optional; defaults to 30 days ago. |
| `window_end` | no | End of the crisis window (YYYY-MM-DD). Defaults to today. |
| `crisis_terms` | no | Optional CSV of up to 5 terms (e.g. recall,defect) that scope the legs to the actual incident. |
| `include` | no | narrative (default on) adds the grounded LLM propagation narrative; pass an empty value for the raw timeline only. |

## Code example

```bash
curl "https://www.socialcrawl.dev/v1/prism/crisis-postmortem?brand=acme" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### What is the SocialCrawl Crisis Post-Mortem API?

GET /v1/prism/crisis-postmortem takes a brand and a window and reconstructs the incident into one chronologically-sorted timeline across web, Reddit, Hacker News, and social, with a computed origin, peak day, and platform propagation sequence — the who-said-what-first deck agencies bill days for.

### How is the crisis origin chosen?

The origin is the earliest event with a native timestamp. Content-analysis web items carry a lagged crawl fetch_time that cannot establish who said it first, so they are labeled and excluded from origin selection; if only crawl-dated events exist the origin is returned with a low_confidence flag.

### Does it filter stale Hacker News posts?

Yes. Hacker News search is relevance-ranked and ignores date, so it can return posts years old. The endpoint filters Hacker News events to your window on their created_at before merging, so an off-window post never corrupts the chronology. Reddit always uses sort=new for real recency.

### Is there an LLM narrative?

By default the response includes a grounded narrative that summarizes how the crisis propagated, written from the computed timeline — it narrates only the timestamps and platforms already in the data and never invents a figure. Pass an empty include= to drop the narrative and get the raw timeline.

### How much does a crisis-postmortem call cost?

Each call is a flat 35 credits. New accounts get 100 free credits with no credit card. The four timeline sources — anger-ordered search, Reddit, Hacker News, and the universal search leg — are the coverage spine; losing more than half refunds half, and if every source fails the full amount comes back.

See the full Prism API: https://www.socialcrawl.dev/platforms/prism

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- What API reconstructs a crisis timeline across social and web?
- How do I find who broke a story first across Reddit and Hacker News via API?
- best crisis monitoring API with an incident propagation timeline