Schema
GET /v1/events/activity - one bounded page of one subject's activity.
Paged exactly like [EventPage]: a seq cursor, oldest first, next_after to continue, and next_after equal to the request's after when the page is empty. One cursor convention across the whole journal is what keeps a page from being silently skipped.
Type object
| Field | Type | Description |
|---|---|---|
| entriesrequired | array of ActivityEntry | |
| next_afterrequired | integer (uint64, >= 0) | Pass back as |
| retention_daysrequired | integer (uint32, >= 0) | How far back this answer can possibly reach. Activity is device-local and the journal keeps nothing beyond this window, so an empty page has two readings - nothing happened, or it happened longer ago than this - and a surface can only say the honest one if it is told the number. It is carried on every page rather than only on an empty one, because a full page is equally horizonless without it. |
{
"entries": [
{
"seq": 0,
"name": "string",
"occurred_at_ms": 0,
"actor": {},
"actor_token": "string",
"correlation_id": {},
"attrs": {
"key": {
"t": "id",
"v": "00000000-0000-4000-8000-000000000000"
}
}
}
],
"next_after": 0,
"retention_days": 0
}The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.
Generated from contract version 1. Last updated .