Get all alerts of the current user's feed (V2)
Changed onRetrieve all alerts for targets that are in collections with feed delivery enabled. Results are ordered by newest first. V2 uses the same filtering and feed logic as the Prewave dashboard.
Response: A Page containing a list of alert objects. Standard pagination fields: content, totalElements, totalPages, size, number, first, last. Each alert includes id, title, timestamps (ISO 8601 UTC), event, priority, classification, locations, links, media, primary/mentioned targets, collection paths, optional geo (see includeGeo), and statusUpdates.
Pagination: Use query parameters page (0-based index) and size (items per page). Default page size is 20 when not specified.
Required permission: access_public_user_feed
Note: Geographic information (geo) is only included when includeGeo=true. Fields with null values are omitted from the JSON response.
Migration from V1 (/public/v1/feed)
V1 is deprecated and will be removed on May 31, 2027. Responses from V1 include a Sunset HTTP header (RFC 8594).
What changed
| Aspect | V1 | V2 |
|---|---|---|
| URL | /public/v1/feed | /public/v2/feed |
| Collections | collectionId (singular) | collectionIds (plural); same comma-separated IDs |
| Date filter | from or newerThan (milliseconds) | from only; UTC ISO 8601 (e.g. 2024-01-01T00:00:00Z) |
| Omit date | (varies) | Last 90 days of data |
| Timestamps in response | Numeric (e.g. milliseconds) | ISO 8601 strings in UTC for createdAt, predictedAtStart, predictedAtEnd |
What is new in V2
- Tier control: minTier and maxTier to include specific supply chain tiers (Tier 1 = direct suppliers, Tier 2 = their suppliers, etc.). Omit both for Tier 1 only (default).
- Classification: isSituationReport, active, relevancy on each alert.
- Structured metadata: eventTypes, eventTypeGroups, alertTypes, labels—easier to filter and display than the previous infotags list.
- Context: mentionedTargets, previousAlerts, flagged, useCaseDetails for richer context.
- Status updates: statusUpdates on each alert.
- Performance: V2 is significantly faster than V1—lower latency and higher throughput.
What is removed in V2
- statusId — no longer returned.
- infotags — use the new structured fields instead: eventTypes, eventTypeGroups, alertTypes, labels.
Request
- Base URLhttps://api.prewave.com
- AuthAPI key in header X-Auth-Token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Collection IDs to filter the feed by. Only alerts for targets in these collections will be returned. In V1 this was collectionId (singular); same comma-separated IDs.
Start of the date range (inclusive). Use UTC ISO 8601 format (e.g. 2024-01-01T00:00:00Z). If omitted, V2 returns alerts from the last 90 days filtered by createdAt. In V1 you could use newerThan (milliseconds) or from; V2 uses from only.
Perspective ID to filter the feed by. Defaults to the user's default perspective.
List of priorities to filter the feed by Allowed values: Low, Mid, High, Critical (comma-separated).
If set to true, the response will include the geo information. Set to true when you need coordinates or shapes for mapping.
Impact level IDs to filter the feed by. Valid IDs depend on your tenant configuration.
Minimum supply chain tier depth to include (V2 only). Tier 1 = direct suppliers, Tier 2 = their suppliers, etc. Default 1. Must be ≤ maxTier; max value 5.
Maximum supply chain tier depth to include (V2 only). Tier 1 = direct suppliers, Tier 2 = their suppliers, etc. Default 1. Must be ≥ minTier; max value 5.
Response
Successfully retrieved alerts
Changes
- info
added to the
////response propertyallOflist for the response status - info
added to the
////response propertyallOflist for the response status - info
added to the
/////response propertyallOflist for the response status - info
removed from the
////response propertyallOflist for the response status - info
removed from the
////response propertyallOflist for the response status - info
removed from the
/////response propertyallOflist for the response status
- info
- warning
removed the optional property
////from the response with the status - warning
removed the optional property
////from the response with the status - warning
removed the optional property
////from the response with the status - warning
removed the optional property
////from the response with the status - warning
removed the optional property
////from the response with the status
- warning