---
title: "List events"
method: GET
path: "/events"
tags: ["Events"]
---

# List events

`GET /events`

## Request

- Base URL: `https://api.rizamo.com/v1`
- URL: `https://api.rizamo.com/v1/events`
- Auth: HTTP bearer

Every change on the team's posts and accounts in the last 30 days, newest first, with who made it: a person, an API key, an agent, or Rizamo itself; and the inbox's comments and messages as they arrive, the replies sent from Rizamo, and what comment automations do. The same events webhooks send, each as one item of this list. A page at a time: pass `nextCursor` as `cursor` for the next one. Someone limited to some profiles sees only those profiles' events. The inbox's and comment automations' events carry what people wrote: a key or agent reads them only with `inbox:read` (`comment.received`, `message.received`, `message.sent`) or `automations:read` (`comment_automation.*`) too; asking for one of those types without it answers 403.

## Query parameters

- `type` 'post.created' | 'post.updated' | 'post.scheduled' | 'post.unscheduled' | 'post.published' | 'post.failed' | 'post.deleted' | 'post.restored' | 'post.target.published' | 'post.target.failed' | 'post.target.updated' | 'post.target.deleted' | 'comment.received' | 'message.received' | 'message.sent' | 'comment_automation.sent' | 'comment_automation.failed' | 'comment_automation.paused' | 'account.connected' | 'account.disconnected' | 'account.updated' | 'account.removed': Only events of this type.
- `resourceId` string: Only events about this post, account, inbox thread or comment automation. An account's include what happened on it to posts' targets (`post.target.*`), and its inbox's and automations' events.
- `since` string, date-time: Only events at or after this moment, within the last 30 days.
- `until` string, date-time: Only events before this moment.
- `limit` integer: How many to return, up to 200: 50 when left out.
- `cursor` string: `nextCursor` from the page before.

## Response `200`

OK

- object
  - `items` Event[], required
    - `id` string, required
    - `type` 'post.created' | 'post.updated' | 'post.scheduled' | 'post.unscheduled' | 'post.published' | 'post.failed' | 'post.deleted' | 'post.restored' | 'post.target.published' | 'post.target.failed' | 'post.target.updated' | 'post.target.deleted' | 'comment.received' | 'message.received' | 'message.sent' | 'comment_automation.sent' | 'comment_automation.failed' | 'comment_automation.paused' | 'account.connected' | 'account.disconnected' | 'account.updated' | 'account.removed', required
    - `at` string, date-time, required
    - `actor` union, required
      - object
        - `type` 'agent', required
        - `agent` 'claude' | 'chatgpt' | 'claudecode' | 'cursor' | 'codex' | 'gemini' | 'perplexity' | 'openclaw' | 'n8n' | 'make' | 'zapier', nullable, required
        - `name` string, required
        - `agentId` string
        - `onBehalfOf` object: The person whose agent it is, who connected it and whom it acts as, with their role: "Ana via Claude Code". Events from before 2026-11-02 have it too, with the person's name now. Left out of an agent with no person, and of other records from before. After the person's erasure, `name` is "A former member" and `userId` empty.
          - `userId` string, required
          - `name` string, required
      - object
        - `type` 'user', required
        - `userId` string, required
        - `name` string, required
        - `initials` string, required
      - object
        - `type` 'api_key', required
        - `keyId` string, required
        - `name` string, required
      - object
        - `type` 'automation', required
        - `automationId` string, required
        - `name` string, required
    - `summary` string, required: What happened, in one line for a person: a post is named by its caption.
    - `resource` object, required
      - `type` 'post' | 'thread' | 'account' | 'comment_automation', required
      - `id` string, required
    - `data` object, required: The facts of the change, by type. `post.created`: `status`, `scheduledAt`, `targets` (`accountId`, `network`, `format`). `post.updated`: `changed` (`text`, `media`, `targets`, `scheduledAt`, `fields.<key>`), with the new `scheduledAt` and `fields` values that changed. `post.scheduled`: `scheduledAt`, `queued` when it took its time from the profile's queue, and `now` when it was sent to publish at once. `post.updated` carries `queued` with a new `scheduledAt`, or when only that changed. `post.unscheduled`: `status`. `post.deleted`: `stillLive`, the targets Rizamo does not take off their network. `post.restored`: `status`. Removing an account (ADR 0048): a post that went to it alone gets `post.deleted` with `accountRemoved` (`accountId`, `network`), its live targets in `stillLive`; a post with other accounts that lost the account's part that never went out gets `post.updated` with `changed: ["targets"]`, `accountRemoved`, and `status` when that changed it (the old one in `previous`). `post.published` and `post.failed`: `status`, `published` targets (`accountId`, `network`, `format`, `url`) and the others (with `error`, and `status`: `failed`, or `unknown` when it may have gone out and a person must check the network before publishing again). `post.target.*`: `accountId`, `network`, `format`; `url` and `networkPostId` when published, `error` and `status` (`failed`, or `unknown` when a person must check the network) when failed. A chain's (posts after the first, as replies) carry `part` and `of`, the part counted after the first post and how many there are: `post.target.published` once its last part is live, `post.target.failed` for the part that stopped it, while the target stays published. `comment.received` and `message.received`: a comment, a reply under one, or a message to the account from someone else, once, when Rizamo first stores it (never the account's own, never one stored before, never one written more than 72 hours before Rizamo found it, such as the history read when an account connects): `threadId`, `messageId`, `kind` (`comment` or `dm`), `network`, `accountId`, `networkPostId` and `postId` (the post it is on, when Rizamo knows it), `author` (`name`, `handle`; LinkedIn gives no handle, and a LinkedIn commenter Rizamo could not name is "LinkedIn member"), `text`, and for comments `reply` (under another comment) and `hidden`. `message.sent`: a reply sent from Rizamo, by a person, an API key, an agent or a comment automation (`actor`), once it is on the network (a Threads, LinkedIn or YouTube reply when it went out, not when it was asked for): the same ids, `kind` and `network`, `to` (the thread's person, `name` and `handle`, named as `author` is, or null under the account's own comment) and `text`. `comment_automation.sent` and `comment_automation.failed`: a run, by its automation (`actor`): `automationId`, `runId`, `accountId`, `network`, `threadId` (the comment's), `conversationId` (the private conversation, once there is one), `commenter` (`name`, `handle`) and `comment` (its text); `followGate` (`followed`) when it went out after the person followed; `reason` (`refused`, `unclear`) and `error` when it failed. `comment_automation.paused`: `automationId`, `name`, `accountId`, `network`, and `pausedReason`, why Rizamo paused it (null when a person did). Removing an account deletes its inbox and automation events, as it deletes its comments and messages; connecting it again reads its recent ones again, so those of the last hours come again as new events. A comment removed on its network takes its events, and the automation events that quote it. Events stay in the profile they happened in when an account moves. A key or agent reads the inbox's and automations' events only with `inbox:read` or `automations:read` too. `account.*`: `network`, `handle`; `reconnected` or `healed` when connected again; `profileId` when moved. `account.disconnected`: the account is still in the team and lost its login; `reason` says why (`needs_login`, `facebook_action_needed`, `permission_missing`, `account_gone`), and a new login brings it back with its posts. `account.removed`: the account left the team; `reason` says how. `removed_by_team`: a person, API key or agent removed it (`actor`), with `posts`, what happened to the posts that used it (as `Remove an account` answers). `data_deletion`: its network asked Rizamo to delete its data (`dataDeletion`, no `handle`), and its other events are deleted. Events from before 5 November 2026 have no `reason` on `account.removed`.
  - `nextCursor` string, nullable, required: Null on the last page.

## Other responses

- `400`: `invalid_request`: A field is missing or wrong, or the request cannot be done as asked: the message names the field or says what to change.
- `401`: `unauthorized`: No API key or sign-in, or the key does not work: it was deleted, or it expired.
- `403`: `forbidden`: The caller may not do this: the key or agent lacks the scope (the message names it), or the action needs another role or a fresh sign-in.
- `429`: `rate_limited`: Over one of Rizamo's limits, or a network asked Rizamo to slow down: wait for `Retry-After` seconds, or as long as the message says.
- `500`: `internal`: Our side failed: retry, and send the `requestId` if it keeps failing.
- `503`: `timeout`: The request took too long to work out, most often a report: try again in a moment, or ask a report for a shorter period or one profile.

---

[API](https://skmtc.dev/rizamo/apis/rizamo-api.md) - [All operations](https://skmtc.dev/rizamo/apis/rizamo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rizamo/apis/rizamo-api/revisions/31b0c1b1ffb5?raw)
