For AI agents: markdown of this page — /docs-content-en/entities/calendar-events/meeting-status.md documentation index — /llms.txt

Meeting RSVP

The participation status shows whether an employee has accepted an invitation to a calendar meeting, declined it, or has not responded yet. The methods in this section read and change only the status of the employee the request runs as.

Bitrix24 API: calendar.meeting.status.get, calendar.meeting.status.set Scope: calendar

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
Parameterid (path) Typenumber Requiredyes DescriptionMeeting 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

Examples

curl — personal key

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

curl — OAuth application

Terminal 
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
Fieldsuccess Typeboolean DescriptionAlways true on success
Fielddata.status Typestring DescriptionParticipation 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
HTTP400 CodeINVALID_PARAMS Descriptionid must be a positive safe integer — id is not a positive integer
HTTP404 CodeENTITY_NOT_FOUND DescriptionCalendar record not found — no event with this id exists
HTTP422 CodeBITRIX_ERROR DescriptionBitrix24 did not return a participation status — the employee was not invited to this meeting
HTTP422 CodeBITRIX_ERROR DescriptionBitrix24 rejected the request; the error text is in message. This is the response for an event that is not a meeting: isMeeting is false
HTTP403 CodeBITRIX_ACCESS_DENIED DescriptionBitrix24 denied the employee access due to insufficient permissions
HTTP403 CodeSCOPE_DENIED DescriptionThe API key does not have the calendar scope
HTTP401 CodeMISSING_API_KEY DescriptionThe X-Api-Key header is missing
HTTP401 CodeTOKEN_MISSING DescriptionThe API key has no configured tokens
HTTP429 CodeRATE_LIMITED DescriptionBitrix24 rejected the call under its request rate limit for the portal
HTTP502 CodeBITRIX_UNAVAILABLE DescriptionBitrix24 is unavailable or returned a response of an unexpected shape
HTTP503 CodeBITRIX_TIMEOUT DescriptionBitrix24 did not respond in time

Full list of common API errors — 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: Q — has not responded, Y — accepted, N — declined, H — organizer.

See also