| title | Create virtualEventWebinar |
|---|---|
| description | Create a new virtualEventWebinar object in draft mode. |
| author | frankpeng7 |
| ms.localizationpriority | medium |
| ms.subservice | cloud-communications |
| doc_type | apiPageType |
| ms.date | 08/08/2024 |
Namespace: microsoft.graph
Create a new virtualEventWebinar object in draft mode.
[!INCLUDE national-cloud-support]
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.
[!INCLUDE permissions-table]
POST /solutions/virtualEvents/webinars| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
| Content-Type | application/json. Required. |
In the request body, supply a JSON representation of the supported derived types of virtualEventWebinar object.
You can specify the following properties when you create a virtualEventWebinar.
| Property | Type | Description |
|---|---|---|
| audience | meetingAudience | The audience to whom the webinar is visible. The possible values are: everyone, organization, and unknownFutureValue. |
| coOrganizers | communicationsUserIdentity collection | The identity information of coorganizers of the webinar. |
| description | itemBody | A description of the webinar. |
| displayName | String | The display name of the webinar. |
| endDateTime | dateTimeTimeZone | The date and time when the webinar ends. |
| settings | virtualEventSettings | The webinar settings. Inherited from virtualEvent. |
| startDateTime | dateTimeTimeZone | The date and time when the webinar starts. |
If successful, this method returns a 201 Created response code and a virtualEventWebinar object in the response body.
The following example shows a request.
POST https://graph.microsoft.com/v1.0/solutions/virtualEvents/webinars
Content-Type: application/json
{
"displayName": "The Impact of Tech on Our Lives",
"description": {
"contentType": "text",
"content": "Discusses how technology has changed the way we communicate."
},
"startDateTime": {
"dateTime": "2024-03-30T10:00:00",
"timeZone": "Pacific Standard Time"
},
"endDateTime": {
"dateTime": "2024-03-30T17:00:00",
"timeZone": "Pacific Standard Time"
},
"audience": "organization",
"coOrganizers": [
{
"id": "7b7e1acd-a3e0-4533-8c1d-c1a4ca0b2e2b",
"tenantId": "77229959-e479-4a73-b6e0-ddac27be315c"
}
],
"settings": {
"isAttendeeEmailNotificationEnabled": false
}
}[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
Note: The response object shown here might be shortened for readability.
HTTP/1.1 201 Created
Content-Type: application/json
{
"id": "a57082a9-7629-4f74-8da0-8d621aab4d2d@4aa05bcc-1cac-4a83-a9ae-0db84b88f4ba",
"status": "draft",
"displayName": "The Impact of Tech on Our Lives",
"description": {
"contentType": "text",
"content": "Discusses how technology has changed the way we communicate."
},
"startDateTime": {
"dateTime": "2024-03-30T10:00:00",
"timeZone": "Pacific Standard Time"
},
"endDateTime": {
"dateTime": "2024-03-30T17:00:00",
"timeZone": "Pacific Standard Time"
},
"audience": "organization",
"createdBy": {
"application": null,
"device": null,
"user": {
"id": "b7ef013a-c73c-4ec7-8ccb-e56290f45f68",
"displayName": "Diane Demoss",
"tenantId": "77229959-e479-4a73-b6e0-ddac27be315c"
}
},
"coOrganizers": [
{
"id": "7b7e1acd-a3e0-4533-8c1d-c1a4ca0b2e2b",
"displayName": "Kenneth Brown",
"tenantId": "77229959-e479-4a73-b6e0-ddac27be315c"
}
],
"settings": {
"isAttendeeEmailNotificationEnabled": false
},
"externalEventInformation": []
}