> ## Documentation Index
> Fetch the complete documentation index at: https://collabase.ch/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Respond to invitation

> Record the token owner's own answer to a meeting invitation: accepted, tentative or declined.

Records the token owner's own answer. Answers given in a calendar app never reach Collabase, so this
is the way in. Someone who reads the meeting through the Space but is not invited has nothing to
answer and receives `403 FORBIDDEN`.

<Info>
  Scope `meetings:write`. The meeting must not be closed or cancelled.
</Info>

## Path parameters

<ParamField path="meetingId" type="string" required>The meeting.</ParamField>

## Request body

<ParamField body="rsvp" type="string" required>`ACCEPTED`, `TENTATIVE` or `DECLINED`.</ParamField>

## Response

<ResponseField name="data" type="object" required>
  <Expandable title="properties">
    <ResponseField name="id" type="string" required>The meeting.</ResponseField>
  </Expandable>
</ResponseField>

<RequestExample>
  ```bash cURL theme={"dark"}
  curl -X POST "https://your-collabase.ch/api/v1/meetings/cm2meet0001abcd/rsvp" \
    -H "Authorization: Bearer clb_xYz123ABCD..." \
    -H "Content-Type: application/json" \
    -d '{ "rsvp": "TENTATIVE" }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={"dark"}
  { "data": { "id": "cm2meet0001abcd" } }
  ```

  ```json 403 theme={"dark"}
  { "error": { "code": "FORBIDDEN", "message": "Only invited people can respond" } }
  ```
</ResponseExample>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.