---
title: "Become a meeting participant"
method: PUT
path: "/v1/meetings/{meetingId}/participants/{uid}"
tags: ["Attendees"]
---

# Become a meeting participant

`PUT /v1/meetings/{meetingId}/participants/{uid}`

## Request

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

Create a new participant in a meeting. Essentially makes the reference user "join" a meeting.

The user in question is normally yourself, i.e. the access token you are using should match the user you're making a participant.

Depending on the target meeting you might need to provide extra identifying information to pass access control checks.

Note that some meetings will refuse to let you in altogether unless you're using a compatible attendee session.

## 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.
- `uid` string, required: A common ID format for various objects like polls or Q&A topics or items therein.

## Request body

- object
  - `name` string: A name to use to identify you within a meeting. If omitted, you'll be assigned either a numerical name (Attendee \#N), or be Anonymous, depending on meeting settings.
  - `email` string: Your email to be made available to the meeting manager. Doesn't get shown to other participants.
  - `password` string: Meeting password to join a meeting that's password-protected

## Response `204`

Meeting join OK

## Other responses

- `401`: Access token is missing or invalid
- `403`: Join request denied; consult the actual error text for more info.
- `404`: Reference meeting does not exist
- `422`: Join request is malformed

---

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