---
title: "List consent events"
method: GET
path: "/consent_events"
tags: ["Consent"]
---

# List consent events

`GET /consent_events`

## Request

- Base URL: `https://www.happyscribe.com/api/v1`
- URL: `https://www.happyscribe.com/api/v1/consent_events`
- Auth: API key in header `Authorization`

Returns the workspace's consent events, newest first — the outcomes the
[Trust Engine](/meetings/consent) records as it collects
consent for your meetings.

## Query parameters

- `workspace_id` string, required
- `bot_id` string
- `participant_email` string
- `action` 'notified' | 'accepted' | 'declined' | 'revoked' | 'deletion_requested'
- `since` string, date-time
- `page` integer
- `per_page` integer

## Response `200`

The workspace's consent events.

- object
  - `results` ConsentEvent[]
    - `object` string: Always `consent_event`.
    - `id` string: Consent event ID, beginning with `cns_`. Treat it as an opaque string.
    - `bot_id` string, nullable: The bot this event belongs to, or `null` for a person-level event.
    - `participant_email` string, nullable: The participant, or `null` for a room-wide notice.
    - `action` 'notified' | 'accepted' | 'declined' | 'revoked' | 'deletion_requested': - `notified` — the person was told about the recording - `accepted` — they consented - `declined` — they said no to this meeting - `revoked` — they withdrew consent going forward - `deletion_requested` — they asked for their speech to be removed
    - `occurred_at` string, date-time
  - `_links` object: Contains `next.url` when more pages exist.

## Other responses

- `401`: Your API key is missing (`missing_api_key`) or wrong (`invalid_api_key`), or it may not access this resource (`unauthorized`).

---

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