Get the participation status of the current user in the event calendar.meeting.status.get
Scope:
calendarWho can execute the method: any user
This method retrieves the participation status of the current user in the event.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
eventId* |
Event identifier. You can obtain the identifier using the calendar.event.get or calendar.event.get.nearest methods |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"eventId":651}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/calendar.meeting.status.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"eventId":651,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/calendar.meeting.status.get
try
{
const response = await $b24.callMethod(
'calendar.meeting.status.get',
{
eventId: 651
}
);
const result = response.getData().result;
console.log(result);
}
catch( error )
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'calendar.meeting.status.get',
[
'eventId' => 651
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your logic for processing data
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting meeting status: ' . $e->getMessage();
}
BX24.callMethod(
'calendar.meeting.status.get',
{
eventId: 651
}
);
require_once('crest.php');
$result = CRest::call(
'calendar.meeting.status.get',
[
'eventId' => 651
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": "Y",
"time": {
"start": 1728732695.718461,
"finish": 1728732696.029712,
"duration": 0.256943941116333,
"processing": 0.03064703941345215,
"date_start": "2024-12-10T11:31:35+00:00",
"date_finish": "2024-12-10T11:31:36+00:00"
}
}
Returned Data
|
Name |
Description |
|
result |
The participation status of the current user. Possible values:
|
Error Handling
HTTP status: 400
{
"error": "",
"error_description": "An error occurred while retrieving the status"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Error Message |
Description |
|
Empty string |
The required parameter "eventId" for the method "calendar.meeting.status.set" is not set |
The required parameter |
|
Empty string |
An error occurred while retrieving the status |
Another error |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Calendar Events: Overview of Methods
- Set Participation Status in Event for Current User calendar.meeting.status.set
- Get User Availability from calendar.accessibility.get