---
title: "Get all Pulse events for a meeting"
method: GET
path: "/v1/meetings/{meetingId}/pulse"
tags: ["Pulse"]
---

# Get all Pulse events for a meeting

`GET /v1/meetings/{meetingId}/pulse`

## Request

- Base URL: `https://app.meet.ps/api`
- URL: `https://app.meet.ps/api/v1/meetings/{meetingId}/pulse`
- Auth: HTTP bearer

Returns a list of all pulse events emitted in a meeting, enumerating the users who emitted these events as well as pulse types.

Note that in JSON format neither the pulse types nor the emitters' names are resolved. In CSV mode both of those data types are resolved.

A **meeting role** of an *owner*, *presenter* or *reporter* is required to access this kind of data.

## Path parameters

- `meetingId` string, required: A canonical meeting ID string that's generated automatically for new meetings. Normally consists of just alphanumericals; legacy meetings can have dashes and underscores.

## Response `200`

List of Pulse events

- object
  - `result` object[]
    - `uid` string: A user identifier
    - `timestamp` integer: Timestamp for a given Pulse event
    - `pulse` integer: Type of Pulse avent - a base-1 index corresponding to the Pulse button index

## Other responses

- `401`: Access token is missing or invalid
- `403`: A meeting-specific role is missing to perform an action
- `404`: Reference meeting not found

---

[API](https://skmtc.dev/meet/apis/meetingpulse-api.md) · [All operations](https://skmtc.dev/meet/apis/meetingpulse-api/llms.txt) · [OpenAPI document](https://skmtc.dev/meet/apis/meetingpulse-api/revisions/dc29466adc0e?raw)