curl "https://yogataraapi.prahlad.app/api/hazard/suicide-attacks/" \
-H "X-API-Key: $OCCULT_API_KEY"A stored dataset of suicide bombing incidents with location and casualty figures. It is a historical event record rather than an astrological calculation; it is here so that mundane analysis can draw event data and chart data from the same API. Records are located by city and province rather than by country, and the loaded data is centred on Pakistan (Balochistan, Khyber Pakhtunkhwa, Punjab, Sindh). Filter with `city` and `province`, both case-insensitive substring matches, with `start_date` and `end_date` on the incident date, and with `min_killed`, `max_killed`, `min_injured` and `no_of_suicide_blasts`. `sort` accepts 'newest' (the default), 'oldest', 'killed_desc', 'killed_asc', 'injured_desc' and 'injured_asc'. Paging uses `page` and `itemsPerPage`, fifty per page by default and up to five hundred. The response is a paged envelope of `count`, `next`, `previous` and `results`. Each result gives an id, the date, a local time string, city, province, latitude and longitude, a free-text `location` naming the exact spot, `killed_min` and `killed_max` (reported casualty figures often being a range), `injured_min` and the number of blasts in the incident.
| Parameter | Type | Example | What it does | |
|---|---|---|---|---|
| city | string | — | Filter by city name (case-insensitive contains) | |
| end_date | string | — | Filter by end date (YYYY-MM-DD) FORMAT constraint: 'YYYY-MM-DD'. Compared with `date__lte`. | |
| itemsPerPage | integer | — | Number of items per page | |
| max_killed | integer | — | Filter by maximum killed (max count) | |
| min_injured | integer | — | Filter by minimum injured (min count) | |
| min_killed | integer | — | Filter by minimum killed (max count) | |
| no_of_suicide_blasts | integer | — | Filter by exact number of suicide blasts | |
| page | integer | — | Page number | |
| province | string | — | Filter by province name (case-insensitive contains) | |
| sort | string | — | Sort order: 'newest' (default), 'oldest', 'killed_desc'/'killed_asc' (by killed count), or 'injured_desc'/'injured_asc' (by injured count) Case-insensitive and stripped. Default 'newest'. There is NO name_asc/name_desc here because no name_field is passed. 'killed_*' sorts on killed_max, 'injured_*' on injured_min. Unrecognised values silently fall back to 'newest'. one of: newest, oldest, killed_desc, killed_asc, injured_desc, injured_asc | |
| start_date | string | — | Filter by start date (YYYY-MM-DD) FORMAT constraint: 'YYYY-MM-DD'. Compared with `date__gte`. |