## Get meeting participation status

`GET /v1/calendar-events/:id/meeting-status`

Returns the participation status for a calendar meeting: whether the employee accepted the invitation, declined it, has not responded yet, or is the meeting organizer. The method returns the status of the employee the request runs as.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|----------|
| `id` (path) | number | yes | Meeting ID. Either the event ID in the organizer's calendar or the ID of the meeting copy in an invitee's calendar works — the copy's `parentId` field points to the organizer's event. List: [`GET /v1/calendar-events`](/docs/entities/calendar-events/list) |

## Examples

### curl — personal key

```bash
curl "https://vibecode.bitrix24.com/v1/calendar-events/7773/meeting-status" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl "https://vibecode.bitrix24.com/v1/calendar-events/7773/meeting-status" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/calendar-events/7773/meeting-status', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

const { success, data } = await res.json()
console.log('Participation status:', data.status)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/calendar-events/7773/meeting-status', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const { success, data } = await res.json()
```

## Response fields

| Field | Type | Description |
|------|-----|----------|
| `success` | boolean | Always `true` on success |
| `data.status` | string | Participation status: `invited` — invited and has not responded yet, `accepted` — accepted the invitation, `declined` — declined it, `host` — meeting organizer |

## Response example

```json
{
  "success": true,
  "data": {
    "status": "invited"
  }
}
```

## Error response example

422 — the employee was not invited to this meeting:

```json
{
  "success": false,
  "error": {
    "code": "BITRIX_ERROR",
    "message": "Bitrix24 did not return a participation status"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 400 | `INVALID_PARAMS` | `id must be a positive safe integer` — `id` is not a positive integer |
| 404 | `ENTITY_NOT_FOUND` | `Calendar record not found` — no event with this `id` exists |
| 422 | `BITRIX_ERROR` | `Bitrix24 did not return a participation status` — the employee was not invited to this meeting |
| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request; the error text is in `message`. This is the response for an event that is not a meeting: `isMeeting` is `false` |
| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied the employee access due to insufficient permissions |
| 403 | `SCOPE_DENIED` | The API key does not have the `calendar` scope |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |
| 401 | `TOKEN_MISSING` | The API key has no configured tokens |
| 429 | `RATE_LIMITED` | Bitrix24 rejected the call under its request rate limit for the portal |
| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |
| 503 | `BITRIX_TIMEOUT` | Bitrix24 did not respond in time |

Full list of common API errors — [Errors](/docs/errors).

## Known specifics

- **Other attendees' statuses are in the event.** The responses of all meeting attendees are returned in the event's `attendeeList` field — [`GET /v1/calendar-events/:id`](/docs/entities/calendar-events/get): `Q` — has not responded, `Y` — accepted, `N` — declined, `H` — organizer.

## See also

- [Meeting RSVP](/docs/entities/calendar-events/meeting-status)
- [Change meeting participation status](/docs/entities/calendar-events/meeting-status-set)
- [Get event](/docs/entities/calendar-events/get)
- [List events](/docs/entities/calendar-events/list)