Retrieving all events from the last 7 days using ÃÛ¶¹ÊÓƵ I/O Journaling API
When using the ÃÛ¶¹ÊÓƵ I/O Journaling API to fetch events from the last seven days, users often encounter limitations due to the API’s token-based pagination system. The API doesn’t support specifying start or end timestamps, making it necessary to paginate forward through results. This documentation outlines how to retrieve all events within the seven-day retention window effectively.
Description description
Environment
ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service – Sites
Issue / Symptoms
- API returns only a limited subset of recent events when endpoints called without query parameters.
- No support to specify start or end timestamps in API requests.
Resolution resolution
The ÃÛ¶¹ÊÓƵ I/O Journaling API is designed to return paginated responses when retrieving event data. To fetch all events from the last seven days:
- Call the journaling endpoint without any query parameters. This will return the oldest available event(s) within the seven-day retention window.
- Extract the
_page.lasttoken from the response and use it in the next GET request to retrieve the next page of events. - Repeat the process until no further
rel=nextlinks are returned, indicating all events have been retrieved.
Note: Forward pagination is required to retrieve all available events, as the API does not support reverse pagination or bulk data retrieval in a single request.
Additional considerations:
- To segment data by timeframes (for example, hourly or daily), process the results after retrieval.
- Ensure automation tools handle forward pagination to reliably sync event data across environments.