Create externalMeetingRegistration (deprecated)
Namespace: microsoft.graph
Important
APIs under the /beta
version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Caution
The external meeting registration API is deprecated and will stop returning data on December 12, 2024. Please use the new webinar APIs. For more information, see Deprecation of the Microsoft Graph meeting registration beta APIs.
Enable registration for an onlineMeeting using an external registration system. An online meeting can only have one registration enabled.
Permissions
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | OnlineMeetings.ReadWrite | Not available. |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Not supported. | Not supported. |
To use application permission for this API, tenant administrators must create an application access policy and grant it to a user to authorize the app configured in the policy to fetch online meetings and/or online meeting artifacts on behalf of that user (with user ID specified in the request path).
HTTP request
To create external meeting registration with delegated (/me
) and app (/users/{userId}/
) permission:
POST /me/onlineMeetings/{meetingId}/registration
POST /users/{userId}/onlineMeetings/{meetingId}/registration
Tip
userId
is the objectId of the meeting organizer.meetingId
is the id of the onlineMeeting object.
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Request body
In the request body, supply a JSON representation of an externalMeetingRegistration object.
Important
You must supply the @odata.type property to specify the registration type. For more details, see the following example.
Response
If successful, this method returns a 201 Created
response code and an externalMeetingRegistration object in the response body.
Example
Request
POST https://graph.microsoft.com/beta/me/onlineMeetings/MSpkYzE3Njc0Yy04MWQ5LTRhZGItYmZ/registration
Content-Type: application/json
{
"@odata.type": "#microsoft.graph.externalMeetingRegistration",
"allowedRegistrant": "everyone"
}
Response
Note: The response object shown here might be shortened for readability.
HTTP/1.1 201 Created
Content-Type: application/json
{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#users('16664f75-11dc-4870-bec6-38c1aaa81431')/onlineMeetings('MSpkYzE3Njc0Yy04MWQ5LTRhZGItYmZ')/registration/$entity",
"@odata.type": "#microsoft.graph.externalMeetingRegistration",
"id": "f23714a3-a2f4-4b1d-96d2-bfe9097e7163",
"allowedRegistrant": "everyone"
}