Create meetings

A user must be an Administrator to create a Adobe Connect meeting, which means the user is a member of the Meeting Hosts group. In the response from principal-list , this group has type=live-admins .

A meeting can be public, protected, or private , and to create each, you need to set a specific combination of principal-id and permission-id :

Public, equivalent to Anyone who has the URL for the meeting can enter the ro om
```
principal-id=public-access&permission-id=view-hidden
```
Protected, equivalent to Only registered users and accepted guests can enter the room
```
principal-id=public-access&permission-id=remove
```
If a meeting is protected, registered users invited as meeting participants can enter by clicking the meeting room URL and logging in. Users who are not invited can log in as guests. The meeting host receives a guest’s request to enter (known as knocking ) and can accept or decline.
Private, which is equivalent to Only registered users and participants can enter . The login page does not allow guests to log in.
```
principal-id=public-access&permission-id=denied
```

Create a public meeting and add host, presenter, and participants

Call principal-list to check that the user creating the Adobe Connect meeting is a member of the live-admins group:

https://example.com/api/xml?action=principal-list&group-id=624523 
        &filter-is-member=true&filter-like-name=bob

Call sco-shortcuts to obtain the sco-id of the user’s my-meetings folder:
```
https://example.com/api/xml?action=sco-shortcuts
```

Parse the response for the sco element with type=my-meetings :

<sco tree-id="624530" sco-id="2006258750" type="my-meetings"> 
    <domain-name>http://example.com</domain-name>  
</sco>

Call sco-update to create the meeting room:

https://example.com/api/xml?action=sco-update 
    &type=meeting&name=October All Hands Meeting 
    &folder-id=2006258750&date-begin=2006-10-01T09:00 
    &date-end=2006-10-01T17:00&url-path=october

The folder-id is the sco-id of the user’s my-meetings folder.

Parse the response for the sco-id of the new meeting:

<sco folder-id="2006258750" lang="en" account-id="624520"  
        type="meeting" icon="meeting" sco-id="2007184134" version="0"> 
    <date-begin>2006-10-01T09:00</date-begin>  
    <date-end>2006-10-01T17:00</date-end>  
    <url-path>/october/</url-path>  
    <name>October All Hands Meeting</name>  
</sco>

You might want to store the url-path to the meeting, if you plan to create a URL to the meeting room later.

Call permissions-update to make the meeting public. Use the sco-id of the meeting as the acl-id :

https://example.com/api/xml?action=permissions-update&acl-id=2007018414 
    &principal-id=public-access&permission-id=view-hidden

Call permissions-update to add a host, a presenter, and participants:
```
https://example.com/api/xml?action=permissions-update 
    &principal-id=2006258745&acl-id=2007018414&permission-id=host
```
- Use a permission-id of host for the meeting host.
- Use mini-host for the presenter.
- Use view for meeting participants.
- You can specify multiple trios of principal-id , acl-id , and permission-id on one call to permissions-update .
Create the URL to the meeting room (see Create meeting room URLs ).

Create a private meeting and add host, presenter, and participants

Follow the steps for creating a public meeting, but set the meeting permission to private:

https://example.com/api/xml?action=permissions-update&acl-id=2007018414 
    &principal-id=public-access&permission-id=denied

Call permissions-update again to add a host, a presenter, and guests.
Create the URL to the meeting room (see Create meeting room URLs ).