---
title: "Get the invite list"
method: GET
path: "/v1/meetings/{meetingId}/invites"
tags: ["Invites"]
---

# Get the invite list

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

## Request

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

Get all would-be participants provisioned through the [Invitation system](https://help.meet.ps/en/articles/2039552-how-do-individual-attendee-codes-work).

This data is provisioned through the app client or via separate API-based CSV upload. Useful for grabbing auto-generated invite codes.

Requires a **meeting role** of *owner*, *manager*, *reporter*, or *auditor*.

## 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`

- object
  - `result` object
    - `data` object: Custom data associated with the invite
    - `id` string: An in-app UID for the user. Note that said user might not exist yet.
    - `name` string: Display name for the invitee.
    - `externalId` string: A third-party UID for the user the invite is for. The email field is a drop-in replacement for this if this field is missing.
    - `email` string: An email to be used to send an invite. Either an *email* or an *externalId* field should be present.
    - `password` unknown
    - `notified` integer: Timestamp of the email notification for the invitee.

## Other responses

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

---

[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)