AdobeConnectAPI
AdobeConnectAPI
ADOBE® CONNECT™ 9
Web Services
Legal notices
Legal notices
For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html.
Contents
Chapter 1: Before you begin
Introduction to Adobe Connect Web Services .......................................................................... 1
Development environment for Adobe Connect Web Services ........................................................... 1
Additional resources .................................................................................................. 1
Conventions .......................................................................................................... 2
Chapter 2: Architecture
Introduction to Adobe Connect Web Services Architecture ............................................................. 3
Data flow ............................................................................................................. 3
Making your first API call ............................................................................................... 6
Chapter 4: Basics
Getting started with Adobe Connect Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Find a principal-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
List principals or guests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Create users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Update users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Create custom fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Create groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Find SCOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Download files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Check permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 5: Meetings
Using web services with Adobe Connect meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Find meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Display meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Create meeting room URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Create meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Set or reset a meeting passcode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Create customized meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Invite users to meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Remove users from meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Calculate meeting usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Check meeting quotas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Get meeting archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Get meeting poll results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 6: Training
Using web services with Adobe Connect Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Training library permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Find courses and curriculums . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Create a course . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
View a user’s training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Enroll one user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Enroll a large number of users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
View curriculum information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Report scores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Additional resources
You can find many useful resources on the Internet that provide information about Adobe Connect, web services and
XML, and other technologies that Adobe Connect uses.
Adobe Connect
Adobe Connect User Community The Adobe Connect User Community at connectusers.com is the hub of the
Adobe Connect community. This site has forums, tutorials, events, announcements, a partner showcase and much
more.
Adobe Connect Help Support Center The Adobe Connect Help and Support Center contains the Adobe Connect
documentation and Support contact information.
The XML Tutorial at the W3Schools website (w3schools.com) can help you get started with XML.
The XPath Tutorial also at the W3Schools website (w3schools.com), describes XPath, which parses an XML document
so that you can use it in an application.
The XSLT Tutorial, a third tutorial at the W3Schools website (w3schools.com), teaches you XSL Transformations,
which you use to convert XML data to other formats.
The XSL Transformations (XSLT) specification at the W3C website (w3.org) is the official definition of XSLT, from the
standards committee who created it.
Numeric Representation of Dates and Time, at the International Organization for Standardization website (iso.org),
provides information about how to use the ISO 8601 standard date and time format.
Date and Time Formats at the W3C website (w3.org) is the official definition of the ISO 8601 date and time format.
Generic Syntax of URI for information on reserved characters and percent encoding is available in RFC3986. URLs
must be properly encoded, using percent encoding for reserved characters.
Other technologies
Flash Player Developer Center and Flash Media Server Developer Center, both available from the Adobe Developer
Center, offer articles, samples, and insights to developing applications that use Adobe Flash Player and Adobe Flash
Media Server.
SCORM Concepts, at the Eduworks Corporation website (eduworks.com), is a tutorial about the Shareable Content
Object Reference Model and describes Shareable Content Objects (SCOs) and Learning Management Systems (LMSs).
An LDAP Roadmap at the Kings Mountain Systems website (www.kingsmountain.com), provides a useful overview of
the Lightweight Directory Access Protocol (LDAP). This site might provide good background material or links for
developers integrating an LDAP directory with Adobe Connect.
Microsoft SQL Server Adobe Connect uses a Microsoft SQL Server database, which your custom applications
retrieve data from and write data to. You may find useful resources at the Microsoft SQL Server Developer Center
(msdn.microsoft.com) including references, community, support, and other information.
Conventions
This guide uses industry standard conventions for displaying code that you are already familiar with.
However, API reference is a formal definition of the API contract between a calling application and the server. As such,
the syntax definitions of request URLs should be described.
We have placed distinct sections of a request URL on separate lines for readability, like this:
http://server_name/api/xml
?action=custom-fields
&filter-definition=value
&session=BreezeSessionCookieValue
When you enter a request URL in the address bar of a browser or construct it in an application, enter it or construct it
as a single line:
https://example.com/api/xml?action=custom-fields&filter-name=location
Syntax elements in blue code font represent definitions that you construct, with a hyperlink to the syntax of the
definition.
Chapter 2: Architecture
Deployment Models
Adobe Connect Web Services provides meeting, training, and events functionality to your applications through its XML API.
As an example, you might have a central user management system, such as an LDAP directory, Microsoft Active
Directory, or another third-party system, that is an integral part of your business processes.
Using web services, you can write an application that synchronizes users between your system and Adobe Connect.
The application can use the J2EE platform or another technology of your choice to pull a list of users from the
directory, compare it against a list of Adobe Connect users, and then perform requested updates within the Adobe
Connect user repository, such as adding or deleting users or groups.
Data flow
The data flows between client applications and Adobe Connect are shown in the following diagram. Custom
applications that you write use paths 1 to 2 and A to B. Adobe Connect applications (such as Adobe Connect Meeting,
Adobe Connect Training, or Adobe Connect Events) can use any of the data flow paths.
1 HTTP:80 2
Web
Web/application
Web browser Services
server
A HTTPS:443 B API
C RTMPS:443 D
SQL database
1 The client web browser requests an Adobe Connect meeting or content URL over port HTTP:80 (connection paths may
vary).
2 The web server responds with content transfer or provides the client browser with information to enter Adobe Connect.
3 Adobe Flash® Player requests a connection to Adobe Flash Media Server over RTMP:1935 and HTTP:80.
4 Flash Media Server responds, and a persistent connection is opened to stream meeting traffic to the browser.
3a (alternate) In some cases, Flash Player requests a connection to the Flash Media Server, but can only obtain a tunneled connection
over RTMPT:80.
4a (alternate) Flash Media Server responds, and a tunneled connection is opened to stream meeting traffic to the browser.
Encrypted If the data flow is encrypted, connections are made securely over HTTPS and RTMPS (Real Time
Messaging Protocol over SSL), as follows.
A The client web browser requests a secure meeting or content URL over an encrypted connection on HTTPS:443
(connection paths may vary).
B The web/application server responds with an encrypted content transfer or provides the client with information to
make an encrypted connection to Adobe Connect.
C Flash Player requests an encrypted connection to Flash Media Server over RTMPS:443.
D Flash Media Server responds, and a persistent connection is opened to stream meeting traffic to the browser.
Custom applications
Adobe Connect Web Services provides an XML API, so your application must be able to communicate with Adobe
Connect using XML over HTTP or XML over HTTPS. Your application calls the API by building a request URL and
passing it one or more parameters, either as name/value pairs or as an XML document. Web Services returns an XML
response, from which you can extract values.
Custom applications retrieve metadata from the Adobe Connect database. Metadata includes meeting or course names
and times, meeting room URLs, content URLs, and report information.
The data flow for a custom application retrieving metadata from the database is from a client web browser, to the client
web application server, to the XML API, the Adobe Connect web application server, and the SQL database—and then
back again.
The data flow between a custom application and Adobe Connect works like this:
1 A user accesses your custom application from a web browser.
2 The application calls the XML API over HTTP:80 or HTTPS:443.
3 The Adobe Connect web application server authorizes the application and its users, retrieves metadata from the
SQL database, and returns the metadata.
4 On the client side, your web or application server, XML parser, and software libraries handle the response and
return it to your application.
5 The user continues to work in your custom application, and clicks a meeting or content URL. At this point, the user
accesses a Adobe Connect application to enter a meeting room, and the typical data flow between a Adobe Connect
application and the server begins.
Flash Media Server Flash Media Server is the muscle of Adobe Connect. Flash Media Server streams audio, video, and
rich media content using RTMP. When a meeting is recorded and played back, audio and video are synchronized, or
content is converted and packaged for real-time screen sharing, Flash Media Server does the job.
Flash Media Server also plays a vital role in reducing server load by caching frequently accessed web pages, streams,
and shared data.
The SQL database Adobe Connect uses the Microsoft SQL Server database for persistent storage of transactional and
application metadata, including users, groups, content, and reporting information. The XML API retrieves metadata
stored in the database. The database can be implemented with either the Microsoft SQL Server Desktop Engine
(MSDE) or the full version of Microsoft SQL Server 2005.
If you have access to a Adobe Connect account in which you can test API calls, you can experiment. In fact, Adobe
recommends testing API calls in the browser while you learn the API and write applications.
Before you begin, it’s useful to install a tool that allows you to view HTTP request and response headers in your
browser.
The response from common-info gives you information about your session with the server, especially the cookie
that identifies your session:
When you log a user in from an application, you need to send the cookie value back to the server to identify the
user’s session (see Log in from an application).
2 Check the request header. This time it sends the BREEZESESSION cookie value back to the server:
GET /api/xml?action=principal-list HTTP/1.1
Accept: */*
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Host: example.com
Connection: Keep-Alive
Cookie: BREEZESESSION=breezbryf9ur23mbokzs8
3 Check the response, which lists all principals on the server, each in its own principal element.
• filter-like-name=jazz (which matches any results that contain jazz in the name)
• filter-out-type=user (which returns any results that do not have a type of user)
These are just a few filter types, and you can find more in filter-definition. Check an action in the reference (at
“Action reference” on page 58) to see whether its response can be filtered. In general, if an action allows filters, you can
use them on any response element or attribute.
A sort is another special parameter that starts with the keyword sort (or sort1 or sort2), followed by a field name
and then one of the keywords asc or desc, for example:
• sort-name=asc (to sort in ascending order by name)
These are just a few sort examples. You can test sorts in the browser or see sort-definition for more.
2 To tighten the response, choose a group from the list and filter on its name:
https://example.com/api/xml?action=principal-list&filter-name=developers
http://example.com/api/xml?action=login&[email protected]
&password=football
6 When the user logs out or the user’s session ends, do not reuse the cookie value.
The domain is equivalent to the account-id, but by using it you can avoid sending an account ID over the Internet,
especially if you use a non-encrypted connection.
6 Parse the response for a status code of ok.
7 (Optional) If you prefer, you can call login before common-info, extract the cookie value from the response
header, and manage it yourself or using a cookie management code library.
With HTTP header authentication, a user logs in to your authentication server. Once the user is authenticated, you
add an HTTP request header that identifies the user, or configure a proxy server to add the header. The authentication
filter on Adobe Connect (named HeaderAuthenticationFilter) converts your user identifier to an Adobe Connect
login ID and authenticates the user.
Authentication Server Proxy Server Authentication Filter Adobe Connect Server
SQL database
External authentication works in addition to standard Adobe Connect authentication. Each user who needs to access
Adobe Connect server needs a valid Adobe Connect server login and password.
When you send a login request to Adobe Connect server with an external authentication credential:
• The authentication filter intercepts the request and checks for a user on Adobe Connect server with an ext-login
field that matches your external credential.
• If a match exists, the filter passes your external authentication to Adobe Connect server, and the server logs the user in.
• If no match exists, the filter passes the login request to the server, which displays its login page. The user must then
log in to Adobe Connect server.
• If the user logs in successfully, Adobe Connect server updates the ext-login field in the user’s profile with the
external credential from your request. The next time you send a request with the user’s external credential, Adobe
Connect server finds a match in ext-login, and the user does not need to log in to Adobe Connect.
• If the user does not log in successfully, the user is not allowed access to Adobe Connect server applications, content,
or meetings.
The steps that follow describe how to call login when you use HTTP header authentication.
3 In the filter element for HeaderAuthenticationFilter, enable the /api/ pattern for request URLs. You have
two choices for how to do this:
If your application uses the XML API and any Adobe Connect applications In the filter element for
HeaderAuthenticationFilter, use comment tags to disable the init-param element with a param-value
of/api/:
<!--
<init-param>
<param-name>ignore-pattern-0</param-name>
<param-value>/api/</param-value>
</init-param>
-->
If your application uses only the XML API Change the filter-mapping element for your filter type to use the URL
pattern /api/* instead of /*:
<filter-mapping>
<filter-name>HeaderAuthenticationFilter</filter-name>
<url-pattern>/api/*</url-pattern>
</filter-mapping>
Then, in the filter element for your filter type, add comment tags around all init-param elements with a param-
name of ignore-pattern-x:
<filter>
<filter-name>HeaderAuthenticationFilter</filter-name>
<filter-class>
com.macromedia.airspeed.servlet.filter.HeaderAuthenticationFilter
</filter-class>
<!--
<init-param>
<param-name>ignore-pattern-0</param-name>
<param-value>/api/</param-value>
</init-param>
...
<init-param>
<param-name>ignore-pattern-4</param-name>
<param-value>/servlet/testbuilder</param-value>
</init-param>
-->
</filter>
4 Configure Adobe Connect server so that users are created with the field ext-login set to the external user ID you
send (see Adobe Connect Installation and Configuration Guide for details).
By default, ext-login has the same value as login, the Adobe Connect server login ID.
5 Once your system authenticates the user, create a login request. Add the parameter external-auth=use, but no
login or password parameters:
https://example.com/api/xml?action=login&external-auth=use
6 Add your authenticated user ID to the HTTP request header. By default, use the header name x-user-id:
x-user-id: joesmith
You can specify a different header name by setting a value for HTTP_AUTH_HEADER in the custom.ini file. You can
also configure a proxy server to set the HTTP header value. See Adobe Connect Installation and Configuration
Guide for details of either.
Be sure not to reuse the cookie value when the user’s session ends.
• You can only send one action in the params root element. You cannot batch multiple actions to be executed
sequentially.
• The XML document you send must be valid and well-formed. Try validating the document in an XML editor
before you send it.
2 Write code that sends an HTTP POST request to Adobe Connect and receives an XML response.
The specific code will vary according to your programming language and development environment.
3 In your code, send the XML document to Adobe Connect in the body of the HTTP POST request.
• Read the XML document into the request.
• Be sure to set a content-type header of text/xml or application/xml.
e = request("sco-shortcuts", null);
xpath = XPath.newInstance("//domain-name/text()");
String url = ((Text) xpath.selectSingleNode(e)).getText();
You can also use string pattern matching to check for a status code of ok. A successful action always returns this
response:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
no-access Shows that the current user does not have permission to call the action, and includes a subcode attribute
with more information.
no-data Indicates that there is no data available for the action to return, when the action would ordinarily return data.
too-much-data Means that the action should have returned a single result but is actually returning multiple results.
When the status code is invalid, the response also has an invalid element that shows which request parameter is
incorrect or missing:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="invalid">
<invalid field="has-children" type="long" subcode="missing" />
</status>
</results>
All valid values for code, subcode, and invalid are described in status, in the API reference. Your application needs
to read and handle status codes and subcodes.
2 When you call an action, parse the response for the status.
3 If the status is not ok, return a null value, display the error status code for debugging, or throw an application
exception.
The action to take depends on which call you are making and how your application is designed.
If you are managing the BREEZESESSION cookie, invalidate the value so it is not reused after a user logs out.
2 Parse for a status code of ok to make sure the logout was successful.
3 Set the cookie value to null or otherwise invalidate it. For example, in this Java code snippet, the breezesession
variable stores the cookie value and is set to null:
public void logout() throws XMLApiException {
request("logout", null);
this.breezesession = null;
}
Chapter 4: Basics
Find a principal-id
A principal is a user or group that has a defined permission to interact with a SCO on the server. You can create users
and groups for your organization and modify their permissions.
Adobe Connect also has built-in groups: Administrators, Limited Administrators, Authors, Training Managers, Event
Managers, Learners, Meeting Hosts, and Seminar Hosts. You can add users and groups to built-in groups, but you
can’t modify the permissions of built-in groups.
Note: The built-in groups that are available depend on your account.
Each Adobe Connect user and group has a principal-id. In some API calls, the principal-id is called a group-id
or user-id to distinguish it from other values. The value of the ID that identifies a user or group is always the same,
regardless of its name. You can check the syntax of any action in “Action reference” on page 58
It is best to use filter-name, filter-login, or filter-email for an exact match. Be careful with filter-like-
name, as it may affect server performance.
Here, the principal-id is called user-id, because it always represents a user who is authenticated to Adobe
Connect. A group cannot log in to the server. You can pass the user-id value as a principal-id in other actions.
This call returns all Adobe Connect users, so be prepared for a large response.
2 Parse the principal elements in the response for the values you want:
<principal principal-id="2006282569" account-id="624520" type="user"
has-children="false" is-primary="false" is-hidden="false">
<name>jazz doe</name>
<login>[email protected]</login>
<email>[email protected]</email>
</principal>
You can use the manager’s principal-id with principal-list to list all users who are assigned to the manager.
1 Call principal-list, filtering on manager-id:
https://example.com/api/xml?action=principal-list&filter-manager-id=2006282569
Create users
To create a new user, you need Administrator privilege. Adobe recommends that you create a user who belongs to the
admins group for your application to use to make API calls that require Administrator privilege.
The type must be user, has-children must be 0 or false, send-email must be true, and email must have a
valid e-mail address.
The server sends a welcome e-mail with login information to the user’s e-mail address.
3 Parse the principal element in the response for the user’s principal-id:
<principal type="user" principal-id="2007184341" has-children="0"
account-id="624520">
<login>[email protected]</login>
<ext-login>[email protected]</ext-login>
<name>jamm doe</name>
</principal>
In the response, ext-login has the same value as login by default, until the user logs in successfully using external
authentication (see Log in using HTTP header authentication).
Update users
Once you create users, you often need to update their information. You can update standard fields that Adobe Connect
defines for users by calling principal-update with the user’s principal-id. The standard fields include email,
login, first-name, and last-name.
If you have defined custom fields for the principal, use acl-field-update to update them.
You need Administrator privilege to update users, so your application must first log in as a user in the admins group.
You cannot log in as the user and then have the user update his or her own profile.
The name field defines the field name as your application displays it, so use appropriate spelling and capitalization.
The custom field in this example is defined for all Adobe Connect principals.
2 Parse the field element in the response for the field-id:
<field field-id="2007184366" object-type="object-type-principal"
display-seq="9" account-id="624520" is-primary="false"
permission-id="manage" is-required="true" field-type="text">
<comments>test</comments>
<name>Country</name>
</field>
Create groups
To add users to groups, you need to call principal-update as your application’s Administrator user.
https://example.com/api/xml?action=principal-update
&first-name=jazzwayjazz&last-name=doe&[email protected]
&password=nothing&type=user&has-children=0
2 Parse for a principal element in the response. A successful response looks like this:
<principal-list>
<principal principal-id="624660" account-id="624520" type="user"
has-children="false" is-primary="false" is-hidden="false">
<name>Bill Jones</name>
<login>[email protected]</login>
<email>[email protected]</email>
<is-member>true</is-member>
</principal>
</principal-list>
https://example.com/api/xml?action=principal-list&filter-type=group
&filter-name=developers
Find SCOs
All objects on Adobe Connect are Shareable Content Objects, or SCOs. The word Shareable comes from learning
management systems in which content is combined into courses or curriculums and shared among them.
On the server, a SCO can be any content object that is combined with other content objects into a course or
curriculum. Courses, curriculums, presentations, and other types of content are SCOs. Meetings, events, folders, trees,
links, graphics files, or any other object are also SCOs.
Each SCO has a unique integer identifier called a sco-id. The sco-id is unique across the entire server. On a Adobe
Connect hosted account, the sco-id is unique across all accounts.
Each SCO also has a type, such as content, course, meeting, and so on. You can see the sco-id and type values in
the response from sco-info or other actions:
Characteristics of SCOs
When you study the XML responses of various calls, you notice more characteristics of SCOs:
• A SCO’s identifier is called a sco-id in some actions, but can also be called folder-id, acl-id, or another name
in other actions. It’s the same unique ID.
• Each SCO can be accessed by various principals, either users or groups. The specific principals who can access a
SCO are defined in access control lists, or ACLs.
• Each SCO has a unique URL, with two parts: a domain name (like http://example.com) and an URL path (like
/f2006123456/). You can concatenate these to form the full URL that accesses the SCO.
• Each SCO has a navigation path that describes where it resides in the folder hierarchy.
• Each SCO has a permission defined for each principal who can access it.
• Some SCOs have description fields, which are text strings that give you information about the SCO.
Often you need to find the ID of a SCO or some information about it. SCOs are arranged in a specific folder hierarchy
where folders have names that indicate whether they are at the top level, contain shared content or templates, or hold
user content and templates.
When you call sco-shortcuts, it returns a list of folders. Notice that folders have different types:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<shortcuts>
<sco tree-id="624530" sco-id="2006258751" type="my-meeting-templates">
<domain-name>http://example.com</domain-name>
</sco>
<sco tree-id="624530" sco-id="2006258750" type="my-meetings">
<domain-name>http://example.com</domain-name>
</sco>
<sco tree-id="624529" sco-id="624529" type="meetings">
<domain-name>http://example.com</domain-name>
</sco>
<sco tree-id="624530" sco-id="624530" type="user-meetings">
<domain-name>http://example.com</domain-name>
</sco>
...
</shortcuts>
</results>
The folders shown in this example happen to be for meetings, but folders for other types of SCOs follow a similar
pattern. Each folder type stores certain types of objects, with certain access privileges, as follows:
content, courses, meetings, events, seminars These are shared folders, such as Shared Meetings, Shared Training, and
so on. The Adobe Connect Administrator has access to this folder. The Administrator can assign Manage permission
to any user, but only members of the built-in group associated with the folder can create new content or meetings
within it.
user-content, user-meetings, user-courses, user-events These folders each contain a folder for each user who can
create content within it (for example, one folder for each meeting host or training developer).
my-courses, my-events, my-meetings, my-meeting-templates, my-content Users create their own content in these
folders and have Manage permission on the content. For example, meeting hosts create meetings in their my-
meetings folder and have Manage permission on those meetings.
shared-meeting-templates This folder is within the Shared Meetings folder, contains meeting templates, and inherits
permissions from Shared Meetings.
You can list the contents of any folder to get information about a specific SCO. When you need to search for a SCO
but do not have a sco-id, move through folders using sco-shortcuts and sco-expanded-contents. Do not use
sco-search, as it returns only certain types of SCOs.
2 Parse the response for a type of the root folder that would logically contain the SCO, for example, my-courses for
a course the user has created.
3 Parse the resulting sco element for a sco-id:
<sco tree-id="4930295" sco-id="2006258748" type="my-courses">
<domain-name>http://example.com</domain-name>
</sco>
4 Create a call to <<UNRESOLVED XREF>> sco-expanded-contents to list the contents of the folder, adding an
exact match filter, if possible:
https://example.com/api/xml?action=sco-expanded-contents
&sco-id=2006258748&filter-name=All About Web Communities
2 Parse the response for the domain-name value in any sco element:
<sco tree-id="624530" sco-id="2006258750" type="my-meetings">
<domain-name>http://example.com</domain-name>
</sco>
The url-path has both leading and trailing slashes. You can take the url-path from report-my-meetings,
report-my-training, or any call that returns it.
Download files
You can download zip files from Adobe Connect to a user’s local computer. A zip file is a SCO. To download it, you
need to construct a download URL to the zip file, which looks like this:
http://server-domain/url-path/output/url-path.zip?download=zip
You probably already know the domain name of your server (such as example.com). If you do not, you can get it by
calling sco-shortcuts.
Be sure to remove the trailing slash from the url-path value before adding .zip to it (so you have a value like
/quiz.zip, not /quiz/.zip).
Check permissions
Permissions define the ways in which a principal can interact with a SCO.
A permission mapping, indicating what permissions a principal has for a particular SCO, is called an access control list
or ACL. An ACL consists of three pieces of information:
• The ID of a principal (a principal-id).
• The ID of a SCO, account, or principal being acted on. In permission calls, it’s called an acl-id. In other calls, the
ID might be called a sco-id, account-id, or principal-id.
• A keyword that indicates the permission level the principal has, which is one of the valid values in permission-id.
To check for permissions on a SCO, the acl-id is a sco-id. The acl-id can also be a principal-id or account-id.
2 Parse the response for a permission-id:
If a principal does not have an explicit permission to the SCO (in other words, if permission-id=""), the
principal’s permissions on the SCO’s parent object apply.
2 Iterate through the principal elements and parse them for permission-id values:
<principal principal-id="2596608" is-primary="false" type="user"
has-children="false" permission-id="view">
<name>Jay Arnold</name>
<login>[email protected]</login>
</principal>
Chapter 5: Meetings
report-bulk-consolidated-transactions To calculate meeting usage, especially the amount of time each user has spent
in the meeting.
report-quiz-interactions To get the results of a meeting poll.
Some actions that handle meetings require Administrator privilege, as noted in the task instructions. Create a Adobe
Connect user who is a member of the admins group for your application to use to make these calls.
Find meetings
You often need to locate the sco-id of a meeting so that you can invite users, get report information about it, or update
it in some other way.
You should understand the structure of folders in which meetings can be stored. By default, meetings are stored in the
host’s My Meetings folder (called my-meetings in the API). For more details on the folder structure, see
Characteristics of SCOs.
2 Parse the response for the sco-id of a meetings folder that is likely to contain the meeting:
<sco tree-id="624530" sco-id="624530" type="user-meetings">
<domain-name>http://example.com</domain-name>
</sco>
The folder name should be meetings, user-meetings, or my-meetings. Use a folder as far down the tree as you can.
3 Call sco-contents on the folder, adding a filter or two to reduce the response:
https://example.com/api/xml?action=sco-contents&sco-id=2006258750
&filter-type=meeting&filter-name=Intro to Film
• The more specific you can make the filters, the better. Good filters to use are filter-name, filter-url-path,
or a date filter. Be careful with using filter-like-name, as it might affect system performance.
• You can also call sco-expanded-contents to list subfolders and their contents. However, sco-contents is
better for server performance, if you know the sco-id of the folder that contains the meeting.
4 Parse the response for the sco-id of the meeting:
<sco sco-id="2006743452" source-sco-id="-1625529" folder-id="2006258750"
type="meeting" icon="meeting" display-seq="0" is-folder="0">
<name>Intro to Film</name>
<url-path>/film/</url-path>
<date-begin>2006-06-09T14:00:00.000-07:00</date-begin>
<date-end>2006-06-09T20:00:00.000-07:00</date-end>
<date-modified>2006-06-09T14:07:13.767-07:00</date-modified>
<duration>06:00:00.000</duration>
</sco>
The response has a row element for each meeting, showing the meeting URL, name, and dates:
<row sco-id="2007372149" type="meeting">
<url>/monday/</url>
<name>Monday Staff Meeting</name>
<date-created>2006-12-18T14:15:00.000-08:00</date-created>
<date-end>2006-12-19T02:15:00.000-08:00</date-end>
<date-modified>2006-12-18T17:38:11.660-08:00</date-modified>
</row>
Display meetings
In your application, you might want to lists of Adobe Connect meetings, such as a user’s present or future scheduled
meetings.
An application workflow might log a user in and display the user’s meetings, or it might add the user to a meeting and
then display meetings. Displaying the user’s meetings means listing the contents of the my-meetings folder.
You can add a filter to reduce the response. For example, you can exclude meetings that have ended:
https://example.com/api/xml?action=report-my-meetings
&filter-expired=false
4 Create the URL to the meeting room by concatenating http:// or https://, domain-name, and url-path.
Use a permission-id of view for a participant, mini-host for presenter, or host for a meeting host.
5 Log out as the Administrator user, and log in as the user you just added to the meeting.
6 Display the user’s current meetings:
https://example.com/api/xml?action=report-my-meetings
&filter-expired=false
Create the URL to a meeting room for which the user is host
1 If you are logged in as a user, and you want to create a URL to a meeting in the user’s my-meetings folder, call
report-my-meetings:
https://example.com/api/xml?action=report-my-meetings
3 Concatenate the two values and add http:// or https:// at the beginning:
https://example.com/online/
If you are using HTTPS and you do not explicitly add https://, the URL defaults to http://, and the user might
not be able to access the meeting room.
Create the URL to a meeting room for which the user is not host
1 Get the sco-id of the meeting (see Find meetings).
2 Call sco-info with the sco-id:
https://example.com/api/xml?action=sco-info&sco-id=2006258750
4 (Optional) If you know the domain name of your Adobe Connect Server account, create the URL using http://
or https://, then the domain-name, then the url-path.
5 If you do not know the domain name, call common-info:
https://example.com/api/xml?action=common-info
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 room
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
You might want to store the url-path to the meeting, if you plan to create a URL to the meeting room later.
6 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
• You can specify multiple trios of principal-id, acl-id, and permission-id on one call to permissions-
update.
8 Create the URL to the meeting room (see Create meeting room URLs).
http://<server>/api/xml?action=acl-field-update&acl-id=<sco-id>&field-id=meeting-
passcode&value=
Note: Only administrators and meeting hosts can call acl-field-update with field-id=meeting-passcode.
Check whether a meeting has a passcode
http://<server>/api/xml?action=acl-field-info&filter-field-id=meeting-passcode&acl-id=<sco-id>
3 Parse the response for the sco-id of a folder that contains meeting templates:
<sco tree-id="624529" sco-id="-625529" type="shared-meeting-templates">
<domain-name>http://example.com</domain-name>
</sco>
<sco tree-id="624530" sco-id="2006258751" type="my-meeting-templates">
<domain-name>http://example.com</domain-name>
</sco>
5 Parse the response for the sco-id of the meeting template you want.
6 Create the meeting using sco-update. Pass it the sco-id of the meeting template as a source-sco-id:
https://example.com/api/xml?action=sco-update&type=meeting
&name=August%20All%20Hands%20Meeting&folder-id=2006258750
&date-begin=2006-08-01T09:00&date-end=2006-08-01T17:00
&url-path=august&source-sco-id=2006349744
7 Continue to set permissions for the meeting and add participants, host, and presenter (see Create meetings).
8 Create the URL to the meeting room (see Create meeting room URLs).
2 Parse the response for the meeting name, date, or other values:
3 Construct the URL to the meeting room (see Create meeting room URLs).
4 Call permissions-info to get the principal-id values of the presenters or participants, filtering on
permission-id:
https://example.com/api/xml?action=permissions-info
&acl-id=2007018414&filter-permission-id=mini-host
11 Parse the principal element of the response for the name and login (or name and email):
<principal account-id="624520" disabled="" has-children="false"
is-hidden="false" is-primary="false" principal-id="2006282569"
type="user">
<ext-login>[email protected]</ext-login>
<login>[email protected]</login>
<name>jazz doe</name>
<email>[email protected]</email>
<first-name>jazz</first-name>
<last-name>doe</last-name>
<x-2006293620>E3612</x-2006293620>
<x-2007017651>San Francisco</x-2007017651>
</principal>
These are for the sender of the e-mail, who is the meeting host.
If the meeting is in progress and the user has already entered the room, the user is not removed from the meeting.
However, when the user’s session times out, the user cannot reenter.
However, you do not need to know the specific permission the principal has before you remove the permission.
2 Get the meeting’s sco-id (see Find meetings).
3 Get the user’s principal-id (see Find a principal-id).
4 Call permissions-update, using the meeting’s sco-id as the acl-id and permission-id=remove:
https://example.com/api/xml?action=permissions-update
&acl-id=2007018414&principal-id=2006258745&permission-id=remove
• The second filter can be for the date the transaction began or ended, the principal-id of the user, the sco-id
of a specific meeting, or another valid filter that meets your needs.
• This call returns all transactions that meet the filter criteria. Be prepared for a large response.
• The call also returns only users who logged in to the meeting as participants, not users who entered as guests.
2 Parse the row elements in the response for date-created and date-closed:
<row transaction-id="2007071217" sco-id="2007071193" type="meeting" principal-
id="2007003123" score="0">
<name>Thursday Meeting</name>
<url>/thursday/</url>
<login>[email protected]</login>
<user-name>jazzwayjazz doe</user-name>
<status>completed</status>
<date-created>2006-08-03T12:33:48.547-07:00</date-created>
<date-closed>2006-08-03T12:34:04.093-07:00</date-closed>
</row>
3 In your application, calculate the time difference between the two dates.
One way to do this (in Java™) is to write a utility method that converts the ISO 8601 datetime values returned in the
response to a GregorianCalendar object. Then, convert each GregorianCalendar date to milliseconds, calculate
the difference between the creation and closing times, and convert the difference to minutes.
4 Repeat for all the meeting transactions that meet your criteria, and total the meeting usage times.
The quota has both a limit and a soft limit. The soft limit is the concurrency limit purchased for the account. It is the
same as the limit, unless you purchase a Burst Pack for meetings, which allows additional participants to join past the
limit, on an overage basis.
Without a Burst Pack, Adobe Connect enforces the concurrency limit and participants who try to enter after the quota
is reached are rejected. If your limit is 20 attendees, attendee 21 receives a notice that the meeting room is full.
All accounts enforce the quotas that are set when the account is created. Accounts do not allow overages, unless you
have a Burst Pack. Furthermore, Burst Packs are only for meetings, not for training or seminars.
2 Parse the response for the quota element with a quota-id value of concurrent-user-per-meeting-quota.
3 Extract the value of soft-limit, the limit defined by your Adobe Connect license.
4 Call report-meeting-concurrent-users to check the peak number of concurrent meeting participants on your
server or in your account:
https://example.com/api/xml?action=report-meeting-concurrent-users
5 Parse the response for the report-meeting-concurrent-users element. Read the value of the max-users
attribute and compare it to the value of soft-limit:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-meeting-concurrent-users max-users="18"
max-participants-freq="3" />
</results>
2 Call sco-expanded-contents with the sco-id and filter-icon=archive to list all archives associated with the
meeting:
https://example.com/api/xml?action=sco-contents&sco-id=2007018414
&filter-icon=archive
3 Parse the response for the sco element and extract the information you want, such as name, date-created, or url-path:
<sco sco-id="2598402" source-sco-id="" folder-id="2598379"
type="content" icon="archive" display-seq="0" is-folder="0">
<name>EN - Monday Night Football_0</name>
<url-path>/p71144063/</url-path>
<date-begin>2004-05-17T15:51:54.670-07:00</date-begin>
<date-end>2004-05-17T15:54:52.920-07:00</date-end>
<date-modified>2004-05-17T15:55:00.733-07:00</date-modified>
<duration>00:02:58.250</duration>
</sco>
• filter-interaction-id=2007027923 to check all responses to a poll (a meeting might have several polls)
• Retrieve the value of the BREEZESESSION cookie from the response header:
Set-Cookie: BREEZESESSION=breezqw4vtfarqxvf9pk2;
domain=.macromedia.com;path=/
3 Create a meeting room URL (see Create meeting room URLs for details).
4 Append a session parameter and the BREEZESESSION cookie value to the meeting room URL:
http://example.com/employeeMeeting/?session=breezbityp829r9ozv5rd
5 Open the meeting room URL that has session appended. One way to do this is with a JavaScript onClick
command:
<a href="http://example.com/employeeMeeting/"
onClick="javascript:window.open('http://example.com/employeeMeeting/?session=breezbityp82
9r9ozv5rd','Breeze', 'toolbar=no,menubar=no,width=800,height=600,resizable=yes'); return
false">http://example.com/employeeMeeting/</a>
• Retrieve the value of the BREEZESESSION cookie from the response header after calling login:
Set-Cookie: BREEZESESSION=breezqw4vtfarqxvf9pk2;
domain=.macromedia.com;path=/
3 In your application, create a meeting room URL (see Create meeting room URLs).
4 Append a guestname parameter and the user’s guest display name to the meeting room URL:
http://example.com/employeeMeeting/?guestName=joy
5 Open the meeting room URL that has the guestname parameter. One way to do this is with a JavaScript onClick
command:
<a href="http://example.com/employeeMeeting/"
onClick="javascript:window.open('http://example.com/employeeMeeting/?guestName=joy','Bree
ze', 'toolbar=no,menubar=no,width=800,height=600,resizable=yes'); return
false">http://example.com/employeeMeeting/</a>
Disabling pods
When you disable pods, the layout of a meeting room is affected and may have more empty white space than you want.
Administrators can either resize remaining pods to occupy the empty space (the recommended approach), or create
new meeting room templates. Otherwise, after a meeting starts, the host can manually resize pods as they see fit.
If a pod with persistent data, such a Chat pod, is disabled and then re-enabled between different sessions of the same
meeting, the contents of the old pod are lost.
3 Get the list of chat transcripts for a particular meeting by calling sco-contents with the chat transcripts tree-id
and the filter source-sco-id:
[http://example.com/api/xml?action=sco-contents&sco-id=10026&filter-source-sco-id=10458]
In the example above, 10026 is the sco-id of the chat transcripts tree and 10458 is the sco-id of the meeting. (You
can get the sco-id of the meeting from the URL of the meeting information page.)
The list of SCOs that is returned represents the chat transcripts for the meeting.
4 Find the chat transcript in the Adobe Connect directory [RootInstall]/content/account-id/transcript-sco-id/output/.
https://example.com/api/xml?action=meeting-feature-update&account-id=7&feature-id=fid-
archive&enable=false&feature-id=fid-archive-force&enable=true
The following table lists the feature IDs for share settings. For a full list of feature IDs, see feature-id.
Share a computer screen or control of the screen; share a document or white board fid-meeting-desktop-sharing
Upload and manage files using the File Share pod fid-meeting-file-share
Chapter 6: Training
report-my-training To list all courses and curriculums the current user is enrolled in, including the URL to access the
course or curriculum.
report-curriculum-taker To get details of a user’s progress within a curriculum.
report-user-trainings-taken To view the latest status of all of a user’s courses and curriculums.
These actions work on courses, curriculums, and training folders and use the permissions allowed for objects in the
Training library.
Each folder, course, and curriculum in the library is a SCO. As you navigate the Training library, you see the sco-id
of the current course or curriculum in the browser URL. You can also retrieve the sco-id by calling sco-contents
or sco-expanded-contents on a folder in the Training library.
Each course, curriculum, or content object in the Training library has permissions that define which users can access
it. As you design your application, be aware of these permission levels:
Enrollee permissions Courses and curriculums have permissions that define which users are enrolled and can access
them. The two permissions available are Enrolled and Denied.
Training library permissions Courses, curriculums, and folders in the Training library have either Manage or Denied
permission. Manage permission means a user can create, delete, edit, or assign permissions. By default, users have
Manage permission on their own training folders, and Administrators have Manage permission on any folder in the
training library.
An Administrator can assign a user Manage permission on an individual course, curriculum, or folder with
permissions-update or check the permissions a user has with permissions-info.
In XML API calls, you read, use, or set values of permission-id as you work with the Training library. These values
of permission-id apply to courses and curriculums:
view The user has access to the course or curriculum, and permission is Enrolled.
You should also be aware of the permission a user has on a folder before executing an API call. Log in as a user with
appropriate permission, or when needed, as your application’s Administrator user. These values of permission-id
apply to training folders:
manage The user can add, delete, change, or assign permissions to courses, curriculums, and content in a folder. The
user can also list the contents of the folder with sco-contents or sco-expanded-contents.
denied The user cannot add, delete, change, or assign permissions to anything in the folder, but can list the contents
of the folder.
https://example.com/api/xml?action=sco-shortcuts
You cannot use a filter with sco-shortcuts, but you can parse the response for the sco element that has
type=courses.
3 Call sco-contents, passing the sco-id of the courses folder and filtering for your specialized training folders:
https://example.com/api/xml?action=sco-contents&sco-id=624528
&filter-name=Sales Training
• You can use filter-name, filter-url-path, another exact match filter, or a date filter. However, be careful
when using filter-like-name, as it might affect server performance.
• You can also get the sco-id of your specialized training folder from the browser URL in Adobe Connect Central
and pass it to sco-contents.
4 Parse the response for the sco-id of your specialized training folder:
<sco sco-id="2007122244" source-sco-id="" folder-id="624528"
type="folder" icon="folder" display-seq="0" is-folder="1">
5 Call sco-contents, passing it the sco-id of the specialized training folder and adding a filter that identifies the
course or curriculum:
https://example.com/api/xml?action=sco-contents
&sco-id=2007122244&filter-name=Java 201
• You can call sco-contents, rather than sco-expanded-contents, if all courses and curriculums are stored at
the top level of your specialized training folder. This improves performance.
• You can define custom fields for SCOs if it helps you identify them in searches (see “Create custom fields” on
page 22).
6 Parse the sco elements in the response for the sco-id of the course or curriculum:
<sco depth="2" sco-id="2006745673" folder-id="2006745671" type="content"
icon="course" lang="en" source-sco-id="2006744233"
display-seq="1" source-sco-type="0">
<name>All About Web Communities</name>
<url-path>/p33096345/</url-path>
<description>Web 2.0 course</description>
<date-created>2006-06-12T14:48:25.870-07:00</date-created>
<date-modified>2006-06-12T14:48:25.870-07:00</date-modified>
</sco>
The best practice is to create the specialized training folders one level deep. By doing so, you can call sco-contents
rather than sco-expanded-contents. This gives better performance.
3 Parse the response for name, url-path, or any values you want to display:
<sco sco-id="2007035246" source-sco-id="2006334909"
folder-id="2006258748" type="content" icon="course"
display-seq="0" is-folder="0">
<name>Java 101</name>
<url-path>/java101/</url-path>
<date-begin>2006-07-20T17:15:00.000-07:00</date-begin>
<date-modified>2006-07-20T17:21:38.860-07:00</date-modified>
</sco>
Create a course
You can use either Adobe Connect Central or Adobe Connect Web Services to create a course. If you use Web Services,
first create an empty SCO and then add content to it.
1 Call sco-update to create a new SCO for the course:
https://example.com/api/xml?action=sco-update&name=salescourse&folder-
id=12345&icon=course&type=content
2 Parse the response for the sco-id value of the new course.
3 Add content to the new SCO, using the sco-id returned by sco-update:
https://example.com/api/xml?action=sco-update&sco-id=77711&source-sco-id=33444
4 Enroll users in the course (see Enroll one user and Enroll a large number of users).
3 Parse the response for name, url, or any other values you want to display:
<row sco-id="2007035246" type="content" icon="course"
permission-id="view">
<name>Java 101</name>
<url>example.com/java101/</url>
<date-created>2006-07-20T17:21:11.940-07:00</date-created>
<date-modified>2006-07-20T17:21:38.860-07:00</date-modified>
<date-begin>2006-07-20T17:15:00.000-07:00</date-begin>
<url-path>/java101/</url-path>
<expired>false</expired>
<completed>false</completed>
</row>
A course can have many allowed values for status, but a curriculum can only have a status of completed or
incomplete. The allowed values of status are described in status attribute in the reference.
https://example.com/api/xml?action=permissions-update
&acl-id=2007035246&principal-id=2006258745&permission-id=view
4 Call report-my-training to list all courses and curriculums the user is enrolled in:
https://example.com/api/xml?action=report-my-training
5 Parse the row elements in the response for values you want to display:
6 Parse the row elements in the response for values you want to display:
<row sco-id="2006745669" type="curriculum" icon="curriculum"
permission-id="view">
<name>A Day in the Life</name>
<url>example.com/day/</url>
<date-created>2006-06-12T14:47:59.903-07:00</date-created>
<date-modified>2006-06-12T14:47:59.903-07:00</date-modified>
<date-begin>2006-06-12T14:45:00.000-07:00</date-begin>
<url-path>/day/</url-path>
<expired>false</expired>
<completed>false</completed>
</row>
Without a principal-id, this call returns a list of all principals enrolled in the course.
https://example.com/api/xml?action=principal-update&type=group
&has-children=1&name=developersc5
With Adobe Connect Central Create the group at Administration > Users and Groups > New Group. Take the
principal-id of the new group from the browser URL.
2 Add the users you want to enroll to the group. You can use an API call or Adobe Connect Central, but you can add
only 200 users at a time.
With the XML API Call group-membership-update, using multiple trios of group-id, principal-id, and is-
member=true:
https://example.com/api/xml?action=group-membership-update
&group-id=4930296&principal-id=2006258745&is-member=true
&group-id=4930296&principal-id=2007343711&is-member=true
If any trios have incorrect information, group-membership-update returns an ok status, but the user in the
incorrect trio is not added to the group.
With Adobe Connect Central Navigate to Administration > Users and Groups > Import. You can import users
from a CSV (comma-delimited) file with at least a login ID for each user.
3 Get the sco-id of the course (see Find courses and curriculums) using the sco-id of the specialized training folder
that contains the course.
4 Call permissions-update to enroll the group in the course:
https://example.com/api/xml?action=permissions-update
&acl-id=2007064258&principal-id=2007105030&permission-id=view
3 Call permissions-update with a permission-id of denied to remove the group’s access to the course:
https://example.com/api/xml?action=permissions-update
&acl-id=2007064258&principal-id=2007105030&permission-id=denied
You may, for example, want to display all users enrolled in a curriculum or all courses a curriculum has. Another
common task is to display the courses in a curriculum the user has completed so far, and then display the remaining
courses.
The response returns a flat list of sco elements, including the curriculum and each SCO it contains. You can build
a hierarchy using the sco-id, folder-id, and depth values. The SCO with type=curriculum is the curriculum
that contains the courses.
4 Parse the response for the status attribute of each sco element and any other values you want to display in your
application:
<sco transcript-id="2006745722" path-type="prereq-none" asset-id=""
sco-id="2006745674" depth="1" folder-id="2006745669" type="15"
icon="course" lang="en" max-retries="" source-sco-id="2006745673"
source-sco-type="0" status="user-passed" score="0" certificate=""
max-score="0" attempts="0">
<access>access-open</access>
<credit-granted>true</credit-granted>
<name>All About Web Communities</name>
<url-path>/l80422078/</url-path>
<description>test</description>
<date-created>2006-06-12T15:06:02.947-07:00</date-created>
<date-modified>2006-06-12T14:48:25.980-07:00</date-modified>
<date-taken>2006-06-12T15:06:02.947-07:00</date-taken>
<override>false</override>
</sco>
Report scores
Many courses offer learners a certain number of retries. If you use server-side review mode, a training manager can
specify the maximum attempts the learner has to complete or pass the course successfully (see Adobe Connect User
Guide for details of how course retry works in both server-side and client-side review mode).
This means that a learner can attempt a course multiple times and have multiple scores. In your application, you may
want to display only the learner’s highest score.
4 Parse the response for the highest score, which should be in the first row element in the list:
• “events-attendance” on page 81
• “report-event-participants-complete-information” on page 82
• “schedule-recording-job” on page 61
• “get-recording-job” on page 63
• “cancel-recording-job” on page 64
• “list-recordings” on page 64
• “list-generated-recordings” on page 67
• “seminar-session-sco-update” on page 68
• “get-next-seminar-event-session” on page 70
• “sco-session-seminar-list” on page 71
• “can-extend-live-seminar” on page 72
• “get-all-seminar-sessions-events” on page 72
• “telephony-profile-dial-in-number-update” on page 74
Sample action
All action (XML API), parameter, element, and attribute names are case sensitive. In other words, name is not the same
as Name, and sco-id is not equivalent to sco-ID. You must enter them exactly as shown in this reference, unless a
specific entry indicates an item is not case sensitive.
action name
Availability
The first version of Adobe Connect to support the action. Unless stated, the action is supported in all subsequent
versions of Adobe Connect.
Description
A description of what the action does and when to use it.
Request URL
The syntax of an HTTP request URL.
Parameters
A detailed desription of the parameters in the request.
Filters
Specifies whether or not results can be filtered or sorted. For more information about filtering and sorting, see “Filter
and sort reference” on page 240.
Response structure
The structure of an XML response.
Response values
A detailed description of the XML elements in a response.
Sample request
A sample HTTP request URL.
Sample response
A sample XML response.
See also
Links to related actions.
Actions
list-recording-jobs
Availability
Adobe Connect 9.1
Description
Provides a list of MP4 recording jobs for a specified folder.
Request URL
The syntax of an HTTP request URL.
Parameters
folder-id Integer No Folder ID for which the recording jobs are listed. If it is
missing, the sco-id parameter must be present.
sco-id Integer No Sco entry from which the folder ID is taken and
recording jobs listed for. If folder-id parameter is
present, this is ignored.
Response structure
The structure of an XML response.
Response values
recording-job->date- NA time- The last time any changes were applied to this job
modified period
recording-job- NA String Job's ID on Zappa (possibly missing if the job still isn't
>encoder-service-job-id picked up from the queue)
recording-job- NA String Job's status on Zappa (possibly missing if the job still isn't
>encoder-service-job- picked up from the queue)
status
recording-job- NA Integer Error code (only present if the job is in error state)
>encoder-service-error-
code
Sample request
https://sample.com/api/xml?action=list-recording-jobs&folder-id=11903
Sample response
<results>
<status code="ok"/>
<recording-jobs>
<recording-job job-id="15607" sco-id="15606" source-sco-id="15112" account-id="7" job-
status="job-error" encoder-service-job-progress="0" folder-id="11903" duration="0">
<date-created>2013-06-27T17:14:28.790+02:00</date-created>
<date-modified>2013-07-02T12:02:38.833+02:00</date-modified>
<encoder-service-job-id>10000000000_1372759253_93bb50bb5e73c9b6_0000</encoder-service-job-
id>
<encoder-service-job-status>ERROR</encoder-service-job-status>
<encoder-service-job-params>ac://http%3A//l-
005763.pstech.rs/common/meetingAS3/shell/shell.swf?login=proxy-
[email protected]&password=#V1#0vpMbun01ngZLnQPpS4f0w==&connect_recording_url=http%3A//l-
005763.pstech.rs/p3wdbw0hdnx/&pbMode=zappa&makeMP4=true&width=1024&height=768&bandwidth=22&d
uration=3000&clustername=l-005763.pstech.rs</encoder-service-job-params>
<encoder-service-error-code>101</encoder-service-error-code>
<name>recording_1</name>
<url-path>/p2xmrb6sp4o/</url-path>
</recording-job>
<recording-job job-id="18502" sco-id="18501" source-sco-id="21003" account-id="7" job-
status="job-queued" encoder-service-job-progress="0" folder-id="11903" duration="0">
<date-created>2013-07-15T16:43:36.467+02:00</date-created>
<date-modified>2013-07-15T16:43:36.467+02:00</date-modified>
<encoder-service-job-params>ac://http%3A//l-
005763.pstech.rs/common/meetingAS3/shell/shell.swf?login=proxy-
[email protected]&password=#V1#0vpMbun01ngZLnQPpS4f0w==&connect_recording_url=http%3A//l-
005763.pstech.rs/p4wvpfpga53/&pbMode=zappa&makeMP4=true&width=1280&height=768&bandwidth=22&d
uration=42817&clustername=l-005763.pstech.rs</encoder-service-job-params>
<name>recording_2</name>
<url-path>/p77trjvlop6/</url-path>
</recording-job>
</recording-jobs>
</results>
schedule-recording-job
Availability
Adobe Connect9.1.
Description
Creates a new recording conversion job that eventually results in creating a new MP4 recording, based on an existing
FLV recording.
Parameters
source-sco-id Integer Yes Sco ID of the recording which is being submitted for
conversion.
Response values
recording-job- NA time-period The last time any changes were applied to this
>date-modified job
Sample request
https://sample.com/api/xml?action=report-dw-query-trainings-taken&start=2013-01-01&end=2013-
06-30&split-period=-1&account-id=7
Sample response
<results>
<status code="ok"/>
<report-dw-query-trainings-taken>
<row count="0">
<period>01-2013</period>
</row>
<row count="0">
<period>02-2013</period>
</row>
<row count="1">
<period>03-2013</period>
</row>
<row count="1">
<period>04-2013</period>
</row>
<row count="1">
<period>05-2013</period>
</row>
<row count="1">
<period>06-2013</period>
</row>
</report-dw-query-trainings-taken>
</results>
get-recording-job
Availability
Adobe Connect 9.1.
Description
Provides recording conversion job for the specified recording ID.
Parameters
Response values
Sample request
https://sample.com/api/xml?action=get-recording-job&job-id=18502
Sample response
<results>
<status code="ok"/>
<recording-job account-id="7" credit-minute="0" debit-minute="6" encoder-service-job-
progress="0" job-id="18605" job-status="job-queued" principal-id="11068" retry-number="0"
sco-id="18604" source-sco-id="13633">
<date-created>2013-07-16T12:17:37.287+02:00</date-created>
<date-modified>2013-07-16T12:17:37.287+02:00</date-modified>
<encoder-service-job-params>ac://http%3A//l-
005763.pstech.rs/common/meetingAS3/shell/shell.swf?login=proxy-
[email protected]&password=#V1#0vpMbun01ngZLnQPpS4f0w==&connect_recording_url=http%3A//l-
005763.pstech.rs/p4tc3hz7erj/&pbMode=zappa&makeMP4=true&width=1280&height=768&bandwidth=22&d
uration=384926&clustername=l-005763.pstech.rs</encoder-service-job-params>
</recording-job>
</results>
cancel-recording-job
Availability
Adobe Connect 9.1.
Description
Cancels a conversion job with the specified Sco ID.
Parameters
Response values
This API returns only the status code indicating the success or failure of the request.
Sample request
https://sample.com/api/xml?action=cancel-recording-job&sco-id=18501
Sample response
<results>
<status code="ok"/>
</results>
list-recordings
Availability
Adobe Connect 9.1.
Description
Provides a list of recordings (FLV and MP4) for a specified folder.
Parameters
folder-id Integer Yes ID of the folder from which the recordings are listed.
Response values
sco encoder-service-job- Integer Conversion job progress value (empty for regular
progress recordings)
sco->date- NA time-period The last time any changes were applied to this entry
modified
Sample request
https://sample.com/api/xml?action=list-recordings&folder-id=11914
Sample response
<results>
<status code="ok"/>
<recordings>
<sco sco-id="13633" source-sco-id="13402" folder-id="11914" type="content" icon="archive"
display-seq="0" job-id="13634" account-id="" job-status="" encoder-service-job-progress=""
is-folder="0" no-of-downloads="0">
<name>content_test</name>
<url-path>/p4tc3hz7erj/</url-path>
<date-begin>2013-06-06T14:28:37.457+02:00</date-begin>
<date-end>2013-06-06T14:35:02.383+02:00</date-end>
<date-created>2013-06-06T14:28:37.457+02:00</date-created>
<date-modified>2013-06-24T14:24:26.973+02:00</date-modified>
<duration>00:06:24.927</duration>
<filename>/common/meetingAS3/shell/shell.swf</filename>
</sco>
<sco sco-id="18604" source-sco-id="13633" folder-id="11914" type="content" icon="mp4-archive"
display-seq="0" job-id="18605" account-id="7" job-status="job-pending" encoder-service-job-
progress="0" is-folder="0" no-of-downloads="0">
<name>content_test(2)</name>
<url-path>/p494q2774vb/</url-path>
<date-begin>2013-06-06T14:28:37.457+02:00</date-begin>
<date-end>2013-06-06T14:35:02.383+02:00</date-end>
<date-created>2013-07-16T12:17:37.287+02:00</date-created>
<date-modified>2013-07-16T12:17:37.287+02:00</date-modified>
<duration>00:06:24.927</duration>
<encoder-service-job-status>QUEUED</encoder-service-job-status>
<encoder-service-job-params>ac://http%3A//l-
005763.pstech.rs/common/meetingAS3/shell/shell.swf?login=proxy-
[email protected]&password=#V1#0vpMbun01ngZLnQPpS4f0w==&connect_recording_url=http%3A//l-
005763.pstech.rs/p4tc3hz7erj/&pbMode=zappa&makeMP4=true&width=1280&height=768&bandwidth=22&d
uration=384926&clustername=l-005763.pstech.rs</encoder-service-job-params>
<job-date-created>2013-07-16T12:17:37.287+02:00</job-date-created>
<job-date-modified>2013-07-16T16:33:49.070+02:00</job-date-modified>
</sco>
</recordings>
</results>
list-generated-recordings
Availability
Adobe Connect 9.1.
Description
Provides a list of recording conversions generated from a specified recording.
Parameters
source-sco-id Integer Yes ID of the recording from which the conversions were
generated.l
Response values
sco->date- NA time- The last time any changes were applied to this Sco entry
modified period
sco->encoder- NA String Job's ID on Zappa (possibly missing if the job still isn't
service-job-id picked up from the queue)
sco->encoder- NA String Job's status on Zappa (possibly missing if the job still
service-job- isn't picked up from the queue)
status
sco->job-date- NA time- The last time any changes were applied to this
modified period conversion job
Sample request
https://sample.com/api/xml?action=list-recording-jobs&folder-id=11903
Sample response
<results>
<status code="ok"/>
<generated-recordings>
<sco sco-id="18604" source-sco-id="13633" folder-id="11914" type="content" icon="mp4-archive"
display-seq="0" job-id="18605" account-id="7" job-status="job-error" encoder-service-job-
progress="0" is-folder="0">
<name>content_test(2)</name>
<url-path>/p494q2774vb/</url-path>
<date-begin>2013-06-06T14:28:37.457+02:00</date-begin>
<date-end>2013-06-06T14:35:02.383+02:00</date-end>
<date-created>2013-07-16T12:17:37.287+02:00</date-created>
<date-modified>2013-07-16T12:17:37.287+02:00</date-modified>
<duration>00:06:24.927</duration>
<encoder-service-job-id>10000000000_1373986069_c7d5915da289f51f_0000</encoder-service-job-
id>
<encoder-service-job-status>ERROR</encoder-service-job-status>
<encoder-service-job-params>ac://http%3A//l-
005763.pstech.rs/common/meetingAS3/shell/shell.swf?login=proxy-
[email protected]&password=#V1#0vpMbun01ngZLnQPpS4f0w==&connect_recording_url=http%3A//l-
005763.pstech.rs/p4tc3hz7erj/&pbMode=zappa&makeMP4=true&width=1280&height=768&bandwidth=22&d
uration=384926&clustername=l-005763.pstech.rs</encoder-service-job-params>
<job-date-created>2013-07-16T12:17:37.287+02:00</job-date-created>
<job-date-modified>2013-07-16T16:49:04.333+02:00</job-date-modified>
</sco>
</generated-recordings>
</results>
seminar-session-sco-update
Availability
Adobe Connect 9.1.
Description
This API is used to create seminar sessions.
Parameters
sco-id Integer Yes ID of the seminar session. Prior to using this API, create
the seminar session ID using sco-update API. Call
acl-field-update API after seminar-session-
sco-update call to associate the load with the seminar
session ID.
field-id=seminar- String No If this value is provided then the seminar load is set to
expected- this value. Otherwise the seminar is set as a normal
load,value meeting (<600 participants).
Response values
Sample request
Below is a seminar session creation flow using a combination of sco-update and seminar-session-sco-update.
A sample call of sco-update API to get the sco-id is
http://connect-domain-url/api/xml?action=sco-update&account-id=7&folder-
id=11101&type=seminarsession&name=b1
Lastly, use acl-field-update API call to set the seminar-expected-load value. A sample request is http://connect-
domain-url/api/xml?action=acl-field-update&acl-id=%3Cseminar-session-sco-id%3E&field-
id=311&value=expected-load-in-integer
Note: acl-id is seminar session id or sco-id, created using sco-update API.
Sample response
Sample response of seminar-session-sco-update to create a session and of acl-field-update to set the seminar-
expected-load value are the same and is as below.
<results>
<status code="ok"/>
</results>
Note: If the time of a seminar session overlaps with another seminar session, it results in an error in the response
indicating a conflict.
get-next-seminar-event-session
Availability
Adobe Connect 9.1.
Description
This API returns information about upcoming seminar session or event for a given seminar ID. This API is used by
meeting client to show upcoming session information, especially when a meeting is running in the stand-by mode.
Parameters
Response values
Sample request
https://sample.com/api/xml?action=get-next-seminar-event-session&sco-id=11903
Sample response
<results>
<status code="ok"/>
<nextsession>
<buffer>1800000</buffer>
<current-session-name>asdasfaf</current-session-name>
<datebegin/>
<limit>10</limit>
<meeting-end-time>2013-07-23T21:45:00.000+00:00</meeting-end-time>
<meeting-start-time>2013-07-23T20:45:00.000+00:00</meeting-start-time>
<s_seminarSessionId>33201</s_seminarSessionId>
<session-name/>
<standby>false</standby><type/>
</nextsession>
</results>
sco-session-seminar-list
Availability
Adobe Connect 9.1.
Description
This API returns all seminar sessions where user has at least Host permission.
Parameters
Response values
Sample request
https://sample.com/api/xml?action=sco-session-seminar-list&sco-id=11903
Sample response
<results>
<status code="ok"/>
<session-seminar-list>
<sco depth="2" sco-id="27001" folder-id="11158" type="meeting" icon="meeting" lang="en"
source-sco-id="11166" display-seq="0" source-sco-type="3" source-sco-icon="3" content-source-
sco-icon="3" duration="120">
<name>bug1</name>
<url-path>/r3a1e37svvs/</url-path>
<date-begin>2013-05-29T13:15:05.720-07:00</date-begin>
<date-end>2013-05-29T15:15:05.720-07:00</date-end>
<date-created>2013-05-29T13:15:13.597-07:00</date-created>
<date-modified>2013-06-11T16:00:00.760-07:00</date-modified>
<seminar-name>Default Event Template</seminar-name>
</sco>
<sco depth="2" sco-id="27015" folder-id="11158" type="meeting" icon="meeting" lang="en"
source-sco-id="11166" display-seq="0" source-sco-type="3" source-sco-icon="3" content-source-
sco-icon="3" duration="120">
<name>bug2</name>
<url-path>/r8t91bpe5me/</url-path>
<date-begin>2013-06-10T16:14:03.577-07:00</date-begin>
<date-end>2013-06-10T18:14:03.577-07:00</date-end>
<date-created>2013-05-29T13:49:35.063-07:00</date-created>
<date-modified>2013-06-10T16:14:12.153-07:00</date-modified>
<seminar-name>Default Event Template</seminar-name>
</sco>
<sco depth="2" sco-id="11609" folder-id="11158" type="meeting" icon="meeting" lang="en"
source-sco-id="11166" display-seq="0" source-sco-type="3" source-sco-icon="3" content-source-
sco-icon="3" duration="120">
<name>cd1</name>
<url-path>/r4w66ncj4sc/</url-path>
<date-begin>2013-05-31T21:05:56.080-07:00</date-begin>
<date-end>2013-05-31T23:05:56.080-07:00</date-end>
<date-created>2013-04-29T11:24:46.213-07:00</date-created>
<date-modified>2013-06-05T19:49:38.763-07:00</date-modified>
<seminar-name>Default Event Template</seminar-name>
</sco>
<sco depth="2" sco-id="11172" folder-id="11157" type="meeting" icon="meeting" lang="en"
source-sco-id="11166" display-seq="0" source-sco-type="3" source-sco-icon="3" content-source-
sco-icon="3" duration="120">
<name>Demo</name>
<url-path>/r3pa40kms6h/</url-path>
<date-begin>2013-04-26T12:01:38.687-07:00</date-begin>
<date-end>2013-04-26T14:01:38.687-07:00</date-end>
<date-created>2013-04-26T12:01:53.953-07:00</date-created>
<date-modified>2013-05-16T15:40:09.017-07:00</date-modified>
<seminar-name>Default Event Template</seminar-name>
</sco>
</session-seminar-list>
</results>
can-extend-live-seminar
Availability
Adobe Connect 9.1.
Description
This API is used by meeting client to check if a running seminar's session can be extended. API throws status exception
(Denied or MaxExtensionReached ) in case session can not be extended.
Parameters
Response values
Sample request
Sample response
get-all-seminar-sessions-events
Availability
Adobe Connect 9.1.
Description
This API is used by seminar calender to return all the sessions and events for an account in given time frame.
Parameters
Filters
Specifies whether or not results can be filtered or sorted. For more information about filtering and sorting, see “Filter
and sort reference” on page 240.
Response values
Sample request
https://sample.com/api/xml?action=get-all-seminar-sessions-events&sco-id=11106&date-
end=2013-07-23T23:59:59.000&account-id=7&date-begin=2013-07-23T00:00:00.000
Sample response
<results>
<status code="ok"/>
<seminars>
<seminarxml>
<account actid="7" name="Enterprise Account" domain="srai-w7" >
<semlicense licid="11157" accountid="7" name="Seminar License # 176094" startdate="2011-09-
13T14:45:00.000-07:00" displaystartdate="1315950300000" enddate="2014-09-13T14:45:00.000-
07:00" displayenddate="1410644700000" limit="1500" >
</semlicense>
<semlicense licid="11158" accountid="7" name="Seminar License # 176096" startdate="2011-09-
13T14:45:00.000-07:00" displaystartdate="1315950300000" enddate="2014-09-13T14:45:00.000-
07:00" displayenddate="1410644700000" limit="10" >
<seminar semid="27001" accountid="7" name="bug1" ><session sessionid="33201" semid="27001"
accountid="7" expected-load="10" name="asdasfaf" type="seminarsession" startdate="2013-07-
23T13:45:00.000-07:00" displaystartdate="1374612300000" enddate="2013-07-23T15:15:00.000-
07:00" displayenddate="1374617700000" /></seminar>
</semlicense>
<semlicense licid="11159" accountid="7" name="Seminar License # 176098" startdate="2011-09-
13T14:45:00.000-07:00" displaystartdate="1315950300000" enddate="2014-09-13T14:45:00.000-
07:00" displayenddate="1410644700000" limit="1000" >
</semlicense>
<semlicense licid="11160" accountid="7" name="Seminar License # 176100" startdate="2011-09-
13T14:45:00.000-07:00" displaystartdate="1315950300000" enddate="2013-04-13T14:45:00.000-
07:00" displayenddate="1365889500000" limit="2000" >
</semlicense>
</account>
</seminarxml>
</seminars></results>
telephony-profile-dial-in-number-update
Availability
Adobe Connect 9.1.
Description
This API replaces a given list of conference numbers in the existing telephony profile.
Note: It deletes any existing conference numbers. To execute this API the administrator, be aware of the location and
country codes mapping. Country codes, needed to support internationalization, are provided in the following mapping.
Parameters
profile-id Integer Yes Telephony profile ID for which the conference number
is to be updated.
Location String Yes Country code (for example, UK) of the location to be
updated
Response values
This API returns only the status code, which indicates successful execution of the API or not.
Sample request
https://sample.com/api/xml?action=telephony-profile-dial-in-number-update&profile-
id=12066&session=breezbreeznnqd4ssqpmo5v6ph&location={BELBSL}&conf-
number=+%2b32+(0)2+792+0488&location={CHEZUR}&conf-
number=+%2b41+(0)44+567+1868&location={DEUFRK}&conf-
number=+%2b49+(0)69+71044+5483&location={DEUMNC}&conf-
number=+%2b49+(0)89+2444+32959&location={DNKCPN}&conf-
number=+%2b45+32+71+09+38&location={ESPMRD}&conf-
number=+%2b34+91+791+7135&location={FRAPRS}&conf-
number=+%2b33+(0)1+70+37+13+83&location={GBRLON}&conf-
number=+%2b44+(0)20+3059+5694&location={GBRREA}&conf-
number=+%2b44+(0)11+8370+0022&location={IRLDUB}&conf-
number=+%2b353+(0)1+5530128&location={ITAMLN}&conf-
number=+%2b39+02+3041+3136&location={NLDASD}&conf-
number=+%2b31+(0)20+708+5022&location={SWESKM}&conf-
number=+%2b46+(0)8+5051+3913&location={USANYC}&conf-number=+%2b1+212+444+0909
Sample response
<results>
<status code="ok"/>
</results>
event-register
Availability
Adobe Connect 9.
Description
This action registers a new or an existing user for an event. While registering, it performs the following backgrounds
tasks:
• If SiteCatalyst analytics is enabled, the action updates it with this registration information.
• If registration limit is enabled, the action checks if the limit is reached. If the limit is reached, the action prevents
the registration. It also sends the registration limit threshold notification email, if the registration threshold count
is reached with this registration.
• If campaign tracking is enabled for an event and a campaign-id is passed as a request parameter, the action registers
the specified campaign channel.
• The action creates a new user or updates an existing user in the Connect system with the specified details like first
name, last name, password, login and so on.
• If registrants do not require approval after the registration, the registrant is automatically made event participant
up on successful registration.
• If registrants do not require approval after registration, the registrant is sent an email containing the event
registration details.
Request URL
http://example.com/api/xml
?action=event-register
&sco-id=12605&
[email protected]
&password=1234
&password-verify=1234
&first-name=api2
&last-name=api2
&campaign-id=xyz
Parameters
Filters
Results cannot be filtered or sorted.
Response structure
<results>
<status code>=<status-code/>
</results>
Response values
NA
Sample request
http://example.com/api/xml?action=event-register&sco-
id=12605&[email protected]&password=1234&password-verify=1234&first-name=api2&last-
name=api2&campaign-id=xyz
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
</results>
events-attendance
Availability
Adobe Connect 9.
Description
Given a user’s login or principal-id, this action returns the list of events that the user attended. If an account-id is not
provided, the currently active login account is used. If principal-id is not provided, the currently active principal is used.
Request URL
http://example.com/api/xml
?action=events-attendance
&[email protected]
&account-id=11143
Parameters
principal-id Integer No The list of the events attended by the user whose ID is
specified here.
login String No The list of the events attended by the user whose login is
specified here.
Filters
Results cannot be filtered or sorted.
Response structure
<results>
<status code=<status-code>/>
<event-attendance>
<event sco-id=<sco-id> account-id=<account-id> folder-id=<folder-id> type=<type>icon=<icon>
max-retries=<number> lang=<language> display-seq=<number> source-sco-id=<source-sco-id>
version=<number> principal-id=<principal-id>>
<name>Event Name</name>
<url-path>Event Url</url-path>
<date-begin>Begin Date</date-begin>
<date-end>End Date</date-end>
<date-created>Creation Date</date-created>
<date-modified>Modification date</date-modified>
<recordcreated>Record Creation Date</recordcreated>
</event>
</event-attendance>
</results>
Response values
The API returns the list of events attended by the specified user.
event principal-id Integer Principal id of the user whose attended events are
being listed
Sample request
http://example.com/api/xml?action=events-attendance&[email protected]&account-id=11143
Sample response
<results>
<status code="ok"/>
<event-attendance>
<event sco-id="12605" account-id="11143" folder-id="11191" type="event" icon="event" max-
retries="" lang="en" display-seq="0" source-sco-id="12600"version="2" principal-id="12631">
<name>event9</name>
<url-path>/event9/</url-path>
<date-begin>2011-10-01T14:30:00.000+05:30</date-begin>
<date-end>2011-10-01T15:30:00.000+05:30</date-end>
<date-created>2011-10-31T14:38:37.497+05:30</date-created>
<date-modified>2011-10-31T15:53:02.053+05:30</date-modified>
<recordcreated>2011-10-31T20:08:37.817+05:30</recordcreated>
</event>
</event-attendance>
</results>
report-event-participants-complete-information
Availability
Adobe Connect 9.
Description
This action lists all the users associated with an event. For each user, the action shows lead qualification status,
registration question responses like, name and email ID, and meeting interactions like, poll responses and file
download activity.
Request URL
http://server_name/api/xml?action=report-event-participants-complete-information&sco-
id=integer
Parameters
Filters
Results cannot be filtered or sorted.
Response structure
<results>
<status code=allowedValue/>
<poll_questions>
<question id=integer description=string/>
... more question elements...
</poll_questions>
<registration_questions>
<question id=integer description=string/>
... more question elements...
</registration_questions>
<user_list>
<user principal_id=integer permission_id=allowedValue name=string login=string
registration_time=datetime attendance_status=allowedValue first_in_time=datetime
last_end_time=datetime duration=time isLead=string registration_question_<id>=string
poll_question_<id>=string >
<qa>
<question<n> description=string>
<answer<n> description=string/>
...more answer<n> elements...
</question<n>>
... more question<n> elements...
</qa>
<files_downloaded>
<file<n> name=string/>
...more file<n> elements...
</files_downloaded>
</user>
... more user elements...
</user_list>
</results>
Response values
user permission_id String The permission rights of the user with this event.
user attendance_stat Integer Whether the user has attended the event or not.
us
user first_in_time datetime The last logout time from the event. This attribute is
defined only if event is associated with a live content.
user last_end_time datetime The last logout time from the event. This attribute is
defined only if event is associated with a live content.
user duration time Total duration for which event is attended by the
user. This attribute is defined only if event is
associated with a live content.
user isLead Boolean Whether user is qualified lead or not depending upon
Qualified Lead criteria set.
Sample request
http://example.com/api/xml?action=report-event-participants-complete-information&sco-
id=14968
Sample response
<results>
<status code="ok"/>
<poll_questions>
<question id="14017" description="Poll question 1?"/>
<question id="14018" description="Poll question 2?"/>
</poll_questions>
<registration_questions>
<question id="13725" description="Registration question 1?"/>
<question id="13727" description="Registration question 2?"/>
</registration_questions>
<user_list>
<user principal_id="13796" permission_id="View" name="User 1"
login="[email protected]" registration_time="05/30/2012 2:50 PM" attendance_status="Attended"
first_in_time="05/30/2012 3:15 PM" last_end_time="05/30/2012 3:40 PM" duration="0:24:30"
isLead="Yes" registration_question_13725=" " registration_question_13727="yes"
poll_question_14017="user 1 poll 1 answer" poll_question_14018="user 1 poll 2 answer" >
<qa>
<question1 description="QnA user 1 question 1"/>
<question2 description="QnA user 1 question 2">
<answer1 description="QnA user 2 question 2 answer"/>
</question2>
</qa>
<files_downloaded>
<file1 name="SampleFile.txt"/>
</files_downloaded>
</user>
<user principal_id="13728" permission_id="View" name="User 2"
login="[email protected]" registration_time="05/30/2012 2:28 PM" attendance_status="Attended"
first_in_time="05/30/2012 3:26 PM" last_end_time="05/30/2012 3:33 PM" duration="0:6:34"
isLead="No" registration_question_13725="user 2 registration question 1 answer"
registration_question_13727="no" poll_question_14017=" user 2 poll 1 answer"
poll_question_14018="user 2 poll 2 answer" >
<qa>
<question1 description="QnA user 2 question 1"/>
<question2 description="QnA user 2 question 2"/>
</qa>
<files_downloaded/>
</user>
</user_list>
</results>
account-expiry-info
Availability
Acrobat Connect Pro Server 7
Description
Returns the expiration date of an account.
Request URL
http://server_name/api/xml
?action=account-expiry-info
&account-id=integer
&session=BreezeSessionCookieValue
Parameters
account-id Integer N The ID of the account for which you want expiration information. If you
don’t provide an account ID, the expiration date for the current user is
returned.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
<Account account-id=integer>
<name>String</name>
<date-expired>Datetime</date-expired>
</Account>
</results>
Response values
Sample request
https://example.com/api/xml?action=acount-expiry-info&account-id=7
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
<Account account-id="7">
<name>Enterprise Account</name>
<date-expired>2009-09-11T18:15:00.000+05:30</date-expired>
</Account>
</results>
See also
expiry-settings-info, expiry-settings-update
acl-field-info
Availability
Breeze 5
Description
Returns information about a principal, account, or SCO, as defined in an access control list (ACL).
The returned information includes fields and their values. Each field has an ID—a name that describes the field.
To call acl-field-info, you must have view permission for the principal, account, or object. You must also specify
a value for acl-id, which is the object the principal has access to. The acl-id can be a sco-id, an account-id, or a
principal-id. You can call principal-list to determine the account-id or principal-id, or sco-shortcuts
or sco-contents to get a sco-id.
Request URL
http://server_name/api/xml
?action=acl-field-info
&acl-id=integer
&session=BreezeSessionCookieValue
&filter-field-id=seminar-expected-load
Parameters
acl-id Integer Y The ID of the SCO, account, or principal for which you want field
information. Can be a valid sco-id, account-id, or principal-id.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<acl-fields>
<field acl-id=integer field-id=string>
<value>string</value>
</field>
...
</acl-fields>
</results>
Response values
code Allowed value A code indicating the response status (see status).
acl-fields Container Information about all fields describing the principal, account, or
object.
Sample request
https://example.com/api/xml?action=acl-field-info&acl-id=2006258745
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<acl-fields>
<field acl-id="2006258745" field-id="email">
<value>[email protected]</value>
</field>
<field acl-id="2006258745" field-id="first-name">
<value>Joy</value>
</field>
<field acl-id="2006258745" field-id="last-name">
<value>Smith</value>
</field>
<field acl-id="2006258745" field-id="seminar-expected-load">
<value>7</value>
</field>
</acl-fields>
</results>
See also
acl-field-list, acl-field-update
acl-field-list
Availability
Breeze 5
Description
Returns a list of values for all instances of a field name on your Adobe Connect Server account.
For example, to list the first names of all users in the account, call acl-field-list with field-id=first-name.
You can call acl-field-info first to get a list of field names.
Request URL
http://server_name/api/xml
?action=acl-field-list
&field-id=string
&session=BreezeSessionCookieValue
Parameters
field-id String Y The name of a field in the access control list for which you want values and
IDs. Only one field name is allowed.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<acl-field-list>
<acl acl-id=integer>
<value>string</value>
</acl>
...
</acl-field-list>
</results>
Response values
code Allowed value A code indicating the response status (see status).
acl-field-list Container Information about all of the values in the account for the specified
field.
acl Container Information about one value for the specified field.
acl-id Integer The ID of the principal, SCO, or account the field belongs to.
Sample request
https://example.com/api/xml?action=acl-field-list&field-id=first-name
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
<acl-field-list>
<acl acl-id="381223">
<value>John</value>
</acl>
<acl acl-id="381302">
<value>Daryl</value>
</acl>
<acl acl-id="381405">
<value>Mary</value>
</acl>
</acl-field-list>
</results>
See also
acl-field-info, acl-field-update
acl-field-update
Availability
Breeze 5
Description
Updates the passed in field-id for the specified acl-id.
Note: To update a standard field for a principal (a user or a group), use the principal-update action. To update a
custom field for a principal, use the acl-field-update action.
Each SCO or account belongs to at least one access control list (ACL). The ACL lists the principals that have
permission to access the SCO or account.
Call acl-field-info to determine the fields in the ACL for a SCO or account. The response contains the field-id
you need for the request to acl-field-update:
<?xml version="1.0" encoding="utf-8" ?>
<results><status code="ok"/></results>
You can specify multiple trios of acl-id, field-id, and value. If you do, use an HTTP POST method, rather than a
GET, to make the request. The GET method has limitations that might cause the request to be truncated. With a POST,
you can add about 50 trios to the request.
To call acl-field-update, you need modify permission on the SCO or account.
Request URL
http://server_name/api/xml
?action=acl-field-update
&acl-id=integer
&field-id=string
&value=string
&session=BreezeSessionCookieValue
Parameters
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=acl-field-update&acl-id=2007035246
&field-id=name&value=Java 101
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
acl-field-list
acl-preference-update
Availability
Breeze 4
Description
Updates a user profile with new language and time zone settings.
Request URL
http://server_name/api/xml
?action=acl-preference-update
&acl-id=integer
&lang=allowedValue
&time-zone-id=allowedValue
&session=BreezeSessionCookieValue
Parameters
acl-id Integer Y The ID of the user whose preferences will be updated. Can be a valid
principal-id.
lang Allowed value N An abbreviation for the new language (see lang for valid values).
time-zone-id Allowed value N An integer setting for the new time zone (see time-zone-id for
values).
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://server.com/api/xml?action=acl-preference-update&acl-id=12345
&lang=fr&time-zone-id=0
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
common-info
Availability
Breeze 4
Description
Returns basic information about the current user and the Adobe Connect server or Adobe Connect hosted account,
including the value of the BREEZESESSION cookie.
If you call common-info without logging in, the response does not contain user and account elements, because the
server cannot identify a user. However, even without logging in, common-info returns a BREEZESESSION cookie value.
The response also contains host, local-host, and admin-host elements. If Adobe Connect is hosted on a cluster,
host is the cluster name; local-host is the name of the server in the cluster that executes the call to common-info;
and admin-host is the name of the secure host on a cluster that supports SSL. Your application can use the value of
admin-host to convert HTTP URLs to more secure HTTPS URLs.
Request URL
http://server_name/api/xml
?action=common-info
&domain=string
&session=BreezeSessionCookieValue
Parameters
domain String N A domain name identifying a Adobe Connect hosted account. Use
to get information about your hosted account.
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<common locale=allowedValue time-zone-id=integer>
<cookie>string</cookie>
<date>datetime</date>
<host>url</host>
<local-host>hostname</local-host>
<admin-host>hostname</admin-host>
<url>/api/xml?action=common-info</url>
<version>string</version>
<account account-id=integer />
<user user-id=integer type="user">
<name>string</name>
<login>string</login>
</user>
<user-agent>string</user-agent>
</common>
</results>
Response values
code Allowed value A code indicating the response status (see status).
locale Allowed value A setting that defines how Adobe Connect Central or your
application displays information to a user (see lang for values).
time-zone-id Allowed value A code that defines the user’s time zone (see time-zone-id for
values).
cookie String The value of the BREEZESESSION cookie (a string the server
returns identifying this user for this login session).
date Datetime The date and time the call to common-info was made, in ISO 8601
format.
host String If Adobe Connect runs on a server, the URL of the fully qualified host
name of the server. If a cluster, the name that identifies the cluster.
local-host String The name of the computer that executed the action (on a single
server, the same as host; on a cluster, the name of the server that
executed the action).
admin-host String The name of the secure host on a cluster that supports SSL.
url String The part of the URL making this call that identifies the action name.
account Empty, with Information about the account the user belongs to. Returned if you
attribute are logged in to Adobe Connect or are making the call on a Adobe
Connect hosted account.
user Container Information about the user who established a session with the
server. Returned only if the user making the call is logged in.
user-id Integer The ID of the user who established a session with the server.
type Allowed value The type of principal who has a session (usually user; see allowed
values for principals at type).
name String The full name of the user who established a session with the server.
login String The login name of the user who is logged in to the server, often the
user’s e-mail address.
user-agent String The identifier of the web browser or client that established a session
with the server.
Sample request
https://example.com/api/xml?action=common-info
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<common locale="en" time-zone-id="4">
<cookie>breezsi4dundh5srw2fq6</cookie>
<date>2006-09-08T11:17:04.470-07:00</date>
<host>https:example.com</host>
<local-host>localserver17</local-host>
<admin-host>securehost.com</admin-host>
<url>/api/xml?action=common-info</url>
<version>connect_6000</version>
<account account-id="624520" />
<user user-id="2006258745" type="user">
<name>Joy Smith</name>
<login>[email protected]</login>
</user>
<user-agent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
.NET CLR 1.1.4322)</user-agent>
</common>
</results>
curriculum-contents
Availability
Adobe Connect Pro 7
Description
Lists all of the SCOs in a curriculum, including the contents of subfolders.
Note: To list the contents of a curriculum, use this action instead of sco-expanded-contents
To find a sco-id to pass in the request URL, call sco-shortcuts. For more information, see “Find SCOs” on page 24.
Request URL
http://server_name/api/xml
?action=curriculum-contents
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter
if you do not use a client-side cookie management library.
Filters
You cannot sort or filter the response to this API call.
Response structure
<results>
<status code=allowedValue/>
<curriculum-contents>
<sco depth=integer sco-id=integer folder-id=integer type=allowedValue
icon=allowedValue lang=allowedValue source-sco-id=integer display-seq=integer source-sco-
type=integer source-sco-icon=integer content-source-sco-icon=integer>
<name>string</name>
<url-path>string</url-path>
<description>
string
</description>
<date-created>datetime</date-created>
<date-modified>datetime</date-modified>
</sco>
...more sco elements...
</curriculum-contents>
</results>
Response values
code Allowed value A code indicating the response status (see status).
sco Container Details about one SCO. This SCO can be a folder or any other type of
object.
depth Integer The depth in the content tree at which this object appears, with top-
level objects at 1.
sco-id Integer The unique ID of the SCO. If the SCO is a folder, same as folder-id.
type Allowed value The type of this content object (see type).
icon Allowed value The name of the icon that visually identifies this object.
lang Allowed value The language in which information about the SCO is displayed (see
lang for values).
source-sco-id Integer The ID of a SCO from which this SCO was created, such as a meeting
template or course content.
display-seq Integer The sequence in which Adobe Connect Central (or your application, if
you use this value) displays a list of SCOs. Values are not necessarily
unique, so multiple SCOs can have the same display-seq value. In
that case, the application must define the display sequence. The
default is 0.
source-sco- Integer An integer indicating the type of SCO from which this SCO was created.
type
source-sco- Integer An integer indicating the type of icon from which this icon was created.
icon
content- Integer An integrer indicating the type of content from which this icon was
source-sco- created.
icon
description String The summary in the UI. If a SCO has a summary, this field exists,
otherwise, the field does not exist.
date-created Datetime The date and time the principal began interacting with the SCO and the
transaction was created.
Sample request
http://example.com/api/xml?action=curriculum-contents&sco-
id=11697&session=breezq7dyhc7m3de8dksr
Sample response
<results>
<status code="ok"/>
<curriculum-contents>
<sco depth="1" sco-id="31949" folder-id="11697" type="link" icon="course" lang="en"
source-sco-id="41184" display-seq="0" source-sco-type="0" source-sco-icon="1" content-source-
sco-icon="1025">
<name>FlashBelt09</name>
<url-path>/l66176109/</url-path>
<date-created>2009-05-27T03:48:54.277+05:30</date-created>
<date-modified>2009-05-27T03:48:54.277+05:30</date-modified>
</sco>
<sco depth="0" sco-id="11697" folder-id="41177" type="curriculum" icon="curriculum"
lang="en" source-sco-id="" display-seq="0" source-sco-type="" source-sco-icon="" content-
source-sco-icon="">
<name>Backyard Cooking</name>
<url-path>/cooking/</url-path>
<description>
Learn how to cook with things you can find in most urban backyards.
</description>
<date-begin>2009-05-27T03:45:00.000+05:30</date-begin>
<date-created>2009-05-27T03:48:40.383+05:30</date-created>
<date-modified>2009-05-27T03:48:40.383+05:30</date-modified>
</sco>
</curriculum-contents>
</results>
custom-fields
Availability
Breeze 4
Description
Lists all custom fields defined in an account and details about the fields.
Custom fields provide information about objects (SCOs) or principals that is not already defined in Adobe Connect
Central. You can create custom fields, or update their value, using custom-field-update.
Request URL
http://server_name/api/xml
?action=custom-fields
&filter-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
You can filter the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<custom-fields>
<field permission-id=allowedValue object-type=allowedValue
field-id=string account-id=integer display-seq=integer
field-type=allowedValue is-primary=boolean is-required=boolean>
<name>string</name>
</field>
</custom-fields>
</results>
Response values
code Allowed value A code indicating the response status (see status).
custom-fields Container The list of custom fields that match the query.
permission-id Allowed value The permission the current user has to access the custom field (see
permission-id for values).
object-type Allowed value The type of object the custom field describes (see permission-id
account-id Integer The ID of the account in which the custom field is defined.
display-seq Integer The sequence in which Adobe Connect Central or your application
displays the custom field, relative to other custom fields.
field-type Allowed value The type of data the custom field accepts. Allowed values are text,
textarea, and password.
is-primary Boolean Whether the custom field can be deleted (true if no, and false if
yes).
is-required Boolean Whether this custom field is required. true if a value must be
specified for this field in each object that uses it. Otherwise, false.
name String The name of the custom field as Adobe Connect Central or your
application displays it.
Sample request
https://example.com/api/xml?action=custom-fields&filter-like-name=name
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<custom-fields>
<field permission-id="manage" object-type="object-type-principal"
field-id="first-name" account-id="624520" display-seq="1"
field-type="text" is-primary="true" is-required="true">
<name>First Name</name>
</field>
<field permission-id="manage" object-type="object-type-principal"
field-id="last-name" account-id="624520" display-seq="2"
field-type="text" is-primary="true" is-required="true">
<name>Last Name</name>
</field>
</custom-fields>
</results>
See also
custom-field-update
custom-fields-delete
Availability
Breeze 4
Description
Deletes a custom field.
The value of is-primary for a custom field must be false before the field can be deleted. If is-primary is true and
you want to change its value, call custom-field-update.
Request URL
http://server_name/api/xml
?action=custom-fields-delete
&field-id=string
&object-type=allowedValue
&session=BreezeSessionCookieValue
Parameters
object-type String Y The type of SCO for which the field is defined (for values, see type).
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=custom-fields-delete&field-id=2006338719&object-
type=object-type-principal
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
custom-field-update
custom-field-update
Availability
Breeze 4
Description
Creates a new custom field or updates the value of an existing one.
You can define up to eight custom fields on a principal or SCO. To create a custom field, call custom-field-update
with at least the following fields: object-type, permission-id, name, field-type, is-required, and is-primary.
If custom-field-update is successful, it returns a field-id.
To update a custom field, specify the field-id, an object-type, and a name for each field that has a value you want
to change.
Be careful when defining custom fields, as retrieving those fields in a report (for example, by calling report-bulk-
users) can affect the performance of the server and the database.
Request URL
http://server_name/api/xml
?action=custom-field-update
&account-id=integer
&object-type=object-type-allowedValue
&permission-id=allowedValue
&name=string
&comments=string
&field-type=allowedValue
&is-required=boolean
&is-primary=boolean
&display-seq=integer
&field-id=integer
&session=BreezeSessionCookieValue
Parameters
object-type String Y The type of SCO this field applies to. Required to create and update fields.
Allowed values:
• object-type-principal
• object-type-meeting
• object-type-sco
• object-type-event
• object-type-read-only
Example:
object-type=object-type-principal
permission-id String Y The permission a principal needs on the object to set or view the field’s
value. The only allowed value is manage. Required to create a field.
name String Y The label for the field in the user interface. Required to create a field.
comments String N Any comments you define for the custom field, displayed as hint text in
your user interface. Can be up to 60 characters long.
field-type String Y The type of field. Allowed values are text, textarea, and password.
Required to create a field.
is-required Boolean Y Whether this custom field is required. Use true if a value must be
specified for this field in each object that uses it. Otherwise, use false.
Required to create a field.
is-primary Boolean Y Whether this custom field can be deleted through the user interface
(true if it cannot be deleted, and false if it can).
display-seq Integer N The sequence in which Adobe Connect Central or your application
displays the custom field, relative to other custom fields.
field-id Integer Y The name of a field that has a value you want to update. Required to
update a field.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<field field-id=integer display-seq=integer object-type=allowedValue
account-id=integer is-primary=boolean permission-id=allowedValue
is-required=boolean field-type=string>
<comments>string</comments>
<name>string</name>
</field>
</results>
Response values
code Allowed value A code indicating the response status (see status).
display-seq Integer The sequence in which Adobe Connect Central or your application
displays the field.
object-type Allowed value The type of object the field describes (see type for allowed values).
account-id Integer For customers on Adobe Connect hosted accounts, the ID of the account
in which the field is defined.
is-primary Boolean Whether this custom field can be deleted (true if no, false if yes).
permission-id Allowed value The permission needed to access the custom field (see permission-id
is-required Boolean Whether a value for this custom field is required (true if yes and false if
no).
field-type Allowed value The type of data the field accepts. Allowed values are text, textarea,
and password.
name String The name of the field entered in name in the request.
Sample request
https://example.com/api/xml?action=custom-field-update
&object-type=object-type-principal&permission-id=manage
&account-id=624520&name=jobtitle&comments=test&field-type=text
&is-required=true&is-primary=false&display-seq=1
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<field field-id="2006472106" object-type="object-type-principal"
display-seq="1" account-id="624520" is-primary="false"
permission-id="manage" is-required="true" field-type="text">
<comments>test</comments>
<name>jobtitle</name>
</field>
</results>
See also
report-bulk-users
expiry-settings-info
Availability
Acrobat Connect Pro Server 7
Description
Returns information about the current settings for account-expiration notifications (the warnings given to users
before an account expires). A user is notified x number of days before their account expires. This action simply returns
the value of x.
Request URL
https://example.com/api/xml
?action=expiry-settings-info
&account-id=Integer
&session=String
Parameters
account-id Integer N The ID of the account. If you don’t provide an account ID, the information for
the current account is returned.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<expiry-num-of-days>
<value>30</value>
</expiry-num-of-days>
</results>
Response values
code Allowed value A code indicating the response status (see status).
value Integer The user is notified this many days before their account expires. The
default value is 30. For example, if a user’s account expires on
December 31, the user is notified on December 1.
Sample request
https://example.com/api/xml?action=expiry-settings-info&account-id=7
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
<expiry-num-of-days>
<value>30</value>
</expiry-num-of-days>
</results>
See also
expiry-settings-update
expiry-settings-update
Availability
Acrobat Connect Pro Server 7
Description
Updates information about the settings for account-expiration notification (the notification given to users before an
account expires). A user is notified x number of days before their account expires. This action simply updates the value of x.
Request URL
https://example.com/api/xml
?action=expiry-settings-update
&account-id=Integer
&session=String
Parameters
account-id Integer N The ID of the account. If you don’t provide an account ID, the
information for the current account is updated.
expiry-num-of-days Integer Y A user is notified this many days before their account expires. The
default value is 30; possible values are 30, 60, and 90.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=expiry-settings-update&account-id=7&expiry-num-of-days=30
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
</results>
See also
account-expiry-info, expiry-settings-info
group-membership-update
Availability
Breeze 4
Description
Adds one or more principals to a group, or removes one or more principals from a group.
To update multiple principals and groups, specify multiple trios of group-id, principal-id, and is-member
parameters.
You can obtain a group-id by calling principal-list and filtering the response with filter-type=group or
another filter value such as filter-type=admins. The built-in groups have distinctive types other than group (see
type for a list of values).
Request URL
http://server_name/api/xml
?action=group-membership-update
&group-id=integer
&principal-id=integer
&is-member=boolean
&session=BreezeSessionCookieValue
Parameters
group-id Integer Y The ID of the group in which you want to add or change members.
principal-id Integer Y The ID of the principal whose membership status you want to update.
Returned by principal-info.
is-member Boolean Y Whether the principal is added to (true) or deleted from (false) the
group.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=group-membership-update&group-id=632398
&principal-id=2006258745&is-member=true
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
learning-path-info
Availability
Breeze 5
Description
Returns a list of learning paths for a learning object that belongs to a curriculum.
A learning object is any SCO that has been added to a curriculum. A learning path is determined by rules that establish
whether a learner can proceed to the next learning object.
You can create a learning path by establishing prerequisite requirements, completion requirements, or preassessment
requirements. For example, a learning path might be the rule that the class Welcome to AcmeCo must be completed
before Managing Projects at AcmeCo.
A call to learning-path-info lists modules within a curriculum and their paths to each other. To see the complete
contents of a curriculum, including content, meetings, and so on, call sco-expanded-contents.
Request URL
http://server_name/api/xml
?action=learning-path-info
&curriculum-id=integer
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
curriculum-id Integer Y The ID of the curriculum the learning object belongs to.
sco-id Integer Y The ID of the curriculum module (course, presentation, or similar) for
which you want a learning path.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<learning-paths>
<learning-path curriculum-id=integer current-sco-id=integer target-sco-id=integer
path-type=allowedValue>
<name>string</name>
</learning-path>
</learning-paths>
</results>
Response values
code Allowed value A code indicating the response status (see status).
current-sco- Integer The learning object for which you want a path.
id
target-sco-id Integer The ID of the learning object that restricts access to the current
learning object (for example, a prerequisite learning object).
path-type Allowed value The type of path between the target and current learning objects
(for example, whether completion of the target is required as a
prerequisite). See path-type for allowed values.
Sample request
https://example.com/api/xml?action=learning-path-info&sco-id=2006334909
&curriculum-id=2006298444
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<learning-paths>
<learning-path curriculum-id="2006298444" current-sco-id="2006298444"
target-sco-id="2006298445" path-type="completion-required">
<name>Security at AcmeCo</name>
</learning-path>
</learning-paths>
</results>
See also
learning-path-update
learning-path-update
Availability
Breeze 5
Description
Updates the learning path for a single learning object in a curriculum. A learning object is any SCO that is added to a
curriculum.
Request URL
http://server_name/api/xml
?action=learning-path-update
&curriculum-id=integer
¤t-sco-id=integer
&target-sco-id=integer
&path-type=allowedValue
&session=BreezeSessionCookieValue
Parameters
curriculum-id Integer Y The ID of the curriculum to which this learning object belongs.
current-sco-id Integer N The ID of the learning object that has the access you want to update.
target-sco-id Integer N The ID of the learning object that restricts access to the current learning
object (for example, a prerequisite course).
path-type Allowed value Y The type of path between the target learning object and the current
learning object (see path-type for allowed values).
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=learning-path-update
&curriculum-id=2006298444¤t-sco-id=2007064258
&target-sco-id=2007035246&path-type=completion-required
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
</results>
See also
learning-path-info
limited-administrator-permissions info
Availability
Acrobat Connect Pro 7
Description
Returns a list of permissions that can be enabled or disabled for the Limited Administrators group and whether or not
that permission is currently enabled. For more information on Limited Administrators, see limited-
administrator-permissions-update.
Request URL
http://server_name/api/xml
?action=limited-administrator-permissions-info
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8"?>
<results>
<status code="ok"/>
<permissions>
<permission>
<enabled>Boolean</enabled>
<name>string</name>
</permission>
</permissions>
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=limited-administrator-permissions-info
&session=breeze6qdeheiso93efb5
Sample response
<?xml version="1.0" encoding="utf-8"?>
<results>
<status code="ok"/>
<permissions>
<permission>
<enabled>true</enabled>
<name>edit-account-info</name>
</permission>
<permission>
<enabled>false</enabled>
<name>view-disk-usage-and-reports</name>
</permission>
<permission>
<enabled>true</enabled>
<name>reset-password</name>
</permission>
<permission>
<enabled>true</enabled>
<name>view-user-data</name>
</permission>
<permission>
<enabled>true</enabled>
<name>add-users-groups-webui</name>
</permission>
<permission>
<enabled>false</enabled>
<name>add-users-groups-csv</name>
</permission>
<permission>
<enabled>true</enabled>
<name>set-content-meeting-permissions</name>
</permission>
<permission>
<enabled>true</enabled>
<name>user-profile-fields</name>
</permission>
<permission>
<enabled>true</enabled>
<name>change-login-pw-policy</name>
</permission>
<permission>
<enabled>false</enabled>
<name>delete-users-groups</name>
</permission>
<permission>
<enabled>true</enabled>
<name>modify-current-users-groups</name>
</permission>
<permission>
<enabled>false</enabled>
<name>customization</name>
</permission>
<permission>
<enabled>false</enabled>
<name>compliance</name>
</permission>
<permission>
<enabled>false</enabled>
<name>chargebacks</name>
</permission>
<permission>
<enabled>false</enabled>
<name>view-system-usage-reports</name>
</permission>
<permission>
<enabled>false</enabled>
<name>quota-threshold-notifications</name>
</permission>
</permissions>
</results>
limited-administrator-permissions-update
Availability
Acrobat Connect Pro 7
Description
Updates the permissions that can be enabled for Limited Administrators.
With Limited Administrators, your organization can have finer control over administrators and what types of things
they can access. Your organization can separate system administrators who control all aspects of the system from
Limited Administrators, who can access and control a subset of the system.
Each Adobe Connect installation has one Limited Administrators group. Users in the Administrators group can edit
the permissions of Limited Administrators.
Request URL
http://server_name/api/xml
?action=limited-administrator-permissions-update
&view-disk-usage-and-reports=boolean
&reset-password=boolean
&view-user-data=boolean
&add-users-groups-webui=boolean
&add-users-groups-csv=boolean
&user-profile-fields=boolean
&change-login-pw-policy=boolean
&delete-users-groups=boolean
&modify-current-users-groups=boolean
&customization=boolean
&edit-account-info=boolean
&set-content-meeting-permissions=boolean
&compliance=boolean
&chargebacks=boolean
&view-training-reports=boolean
&reset-to-default=value
Parameters
When you use this command, pass at least one parameter. The descriptions that follow indicate if the permission is set
to true by default.
view-disk-usage-and-reports Boolean N A value of true allows limited administrators to view disk usage and
reports. The default value is true.
reset-password Boolean N A value of true allows limited administrators to reset the password of
a user. Part of the view-user-data set. The default value is true.
view-user-data Boolean N Superset; a value of true allows limited administrators to view user
data. By setting this parameter to enable, you enable all parameters in
this set. (See all parameters that are part of the view-user-data set.) The
default value is true.
add-users-groups-webui Boolean N A value of true allows limited administrators to add users and groups
by using the management console. Part of the view-user-data set. The
default value is true.
add-users-groups-csv Boolean N A value of true allows limited administrators to add users or groups by
importing a CSV file. Part of the view-user-data set
user-profile-fields Boolean N A value of true allows limited administrators to modify user profile
fields.
change-login-pw-policy Boolean N A value of true allows limited administrators to change the login and
password policies.
delete-users-groups Boolean N A value of true allows limited administrators to delete users or groups.
Part of the view-user-data set
modify-current-users-groups Boolean N A value of true allows limited administrators to modify currents users
and groups. Part of the view-user-data set. The default value is true.
customization Boolean N A value of true allows limited administrators to customize the colors of
the account web pages, meetings, and the login page.
set-content-meeting-permissions Boolean N A value of true allows limited administrators to set the permissions for
content or meetings. The default value is true.
chargebacks Boolean N A value of true allows limited administrators to access the cost-center
settings for this account.
view-training-reports Boolean N A value of true allows limited administrators to view training reports.
reset-to-default Boolean N A value of true resets all permissions to the default permissions set by
Adobe.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
The example shows
https://admin.ibreeze.macromedia.com/api/xml?action=limited-administrator-permissions-update
&session=breezghd9nxdhh768vpob
&view-user-data=true
&view-user-data=false
&reset-password=true
&reset-password=false
&modify-current-users-groups=true
&modify-current-users-groups=false
&add-users-groups-webui=true
&add-users-groups-webui=false
&add-users-groups-csv=false
&delete-users-groups=false
&user-profile-fields=true
&user-profile-fields=false
&change-login-pw-policy=true
&change-login-pw-policy=false
&chargebacks=false
&edit-account-info=true
&edit-account-info=false
"a-threshold-notifications=false
&customization=false
&view-disk-usage-and-reports=false
&view-system-usage-reports=false
&compliance=false
&set-content-meeting-permissions=true
&set-content-meeting-permissions=false
Sample response
<?xml version="1.0" encoding="utf-8"?>
<results><status code="ok"/>
</results>
login
Availability
Breeze 4
Description
Logs a user in to Adobe Connect Server.
In a client application, after logging in a user, you must read and store the cookie called BREEZESESSION, which can
be found in the HTTP headers of the response from login. You must then include the value of that cookie in every
subsequent request that you make for that user.
If you cannot retrieve cookie values from HTTP response headers, you can call common-info to get the cookie value
before the user logs in. Then, pass the value to login using the session request parameter:
https://example.com/api/xml?action=login&login=loginId&password=password
&session=value
You can also use the session parameter on any API call you make after login. For example, to call principal-list
after logging in, you can enter:
https://example.com/api/xml?action=principal-list&session=value
The BREEZESESSION value is valid for only one login session. Your application must store a new cookie value each time
the user logs in.
When you call the login action, you are sending a login ID and password across a network, unless you use external
authentication. Use SSL or another appropriate security method to protect passwords in transit.
Request URL
http://server_name/api/xml
?action=login
&login=string
&password=string
&account-id=integer
&external-auth=use
&domain=string
Parameters
account-id Integer N The ID of your Adobe Connect hosted account. If your organization is
running a licensed Adobe Connect Server, do not use account-id.
external-auth Allowed value N A value indicating whether you send an external network login ID to
represent the user to Adobe Connect. If so, use external-
auth=use.
login String Y/N The user’s login name. Do not use if you use external or HTTP header
authentication.
password String Y/N The user’s password. Do not use if you use external or HTTP header
authentication.
domain String N The domain name of your Adobe Connect hosted account. If your
organization is running a licensed of Adobe Connect Server, do not use
domain.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
http://example.com/api/xml?action=login&[email protected]&password=happy
&session=breeztg8mz53r93vebwur
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
logout
logout
Availability
Breeze 4
Description
Ends a user’s login session, invalidating the cookie value associated with the user’s session.
After calling logout, set the BREEZESESSION cookie value to null. Do not reuse the cookie value after your user logs out.
Request URL
http://server_name/api/xml
?action=logout
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
http://example.com/api/xml?action=logout
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
login
meeting-disclaimer-info
Availability
Acrobat Connect Pro 7
Description
Provides information about the disclaimer text that is shown when a user enters a meeting. For more information
about the disclaimer, see meeting-disclaimer-update.
Request URL
https://servername/api/xml
?action=meeting-disclaimer-info
&account-id=integer
&session=string
Parameters
account-id Integer N The ID of the account for which the disclaimer text is retrieved. If not used, the account
that you are currently logged in to is updated.
Filters
Filters cannot be used with this action.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<disclaimer>
string
</disclaimer>
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=meeting-disclaimer-info&account-id=7
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<disclaimer>
This meeting may be recorded for compliance purpose. By clicking OK you agree to
the terms of meeting.
</disclaimer>
</results>
meeting-disclaimer-update
Availability
Acrobat Connect Pro 7
Description
Updates the disclaimer text that is shown when a user enters a meeting.
To comply with communications regulations or standards, you can set up a disclaimer notice to appear when a user
enters a meeting. The disclaimer notice typically displays boilerplate information for your organization. It advises
users of the status of the meeting and the terms of use for the meeting. For example, a disclaimer notice could advise
users that the meeting is being recorded, and that users cannot join the meeting unless they accept the notice.
If the disclaimer is activated, the notice is shown in all meetings. Activate the disclaimer either through the
management console or by using the meeting-feature-update action with the fid-meeting-disclaimer
parameter set to enabled.
Request URL
https://servername/api/xml
?action=meeting-disclaimer-update
&account-id=integer
&disclaimer=string
&session=string
Parameters
account-id Integer N The ID of the account for which the disclaimer text is updated. If not used, the
account that you are currently logged into is updated.
disclaimer String Y The disclaimer text that is shown when a user starts a meeting. The disclaimer
can, for example, notify users that a meeting is being recorded.
The limit is 1500 characters. The disclaimer text can contain XML-compliant HTML
tags. For example: <b>This meeting is being recorded.</b>
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=code />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=meeting-disclaimer-update&disclaimer=Please note that this
meeting is being recorded.
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
meeting-feature-update
Availability
Acrobat Connect Pro 7
Description
Enables or disables features in a meeting. This action is used to manage features such as recording of meetings and
control of pods. For more information on usage, see “Configure compliance settings” on page 44. You can append
multiple feature-id and enable pairs to the end of the request URL.
Request URL
http://server name/api/xml
?action=meeting-feature-update
&account-id=integer
&feature-id=value
&enable=value
Parameters
account-id Integer Y The ID of your Adobe Connect hosted account. For enterprise
installations, the ID is 7. For licensed installations, use common-info to
get the ID.
feature-id Integer Y The ID of the feature to enable or disable. For available IDs, see
feature-id.
enable Boolean Y Whether to enable the specified feature (true) or not (false).
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=code />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
The following sample disables the Chat pod.
https://example.com/api/xml?action=meeting-feature-update&account-id=7&feature-id=fid-
meeting-chat&enable=false
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
permissions-info
Availability
Breeze 4
Description
Returns the list of principals (users or groups) who have permissions to act on a SCO, principal, or account.
To call permissions-info, you must specify an acl-id, which is the ID of a SCO, principal, or account that can be
acted on. ACL stands for access control list, and means the list of entities who have permission.
With just an acl-id, permissions-info returns a list of all principals in the account, showing each principal’s
permission on the principal or SCO specified in the acl-id:
https://example.com/api/xml?action=permissions-info&acl-id=2006258745
To check the permissions a specific principal has on a principal or SCO within an account, call permissions-info
with an acl-id and a filter on principal-id:
http://example.com/api/xml?action=permissions-info&acl-id=7&filter-principal-id=10022
To check the permissions a principal has on an account, call permissions-info with both an acl-id (specifying an
account-id) and a principal-id:
https://example.com/api/xml?action=permissions-info&acl-id=624520&principal-id=624523
Request URL
http://server_name/api/xml
?action=permissions-info
&acl-id=integer
&principal-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
acl-id Integer Y The ID of a SCO, account, or principal that a principal has permission to
act on. The acl-id is a sco-id, principal-id, or account-id in
other calls.
principal-id Integer N The ID of a principal who has a permission (even if denied) to act on an
object.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<permissions>
<principal principal-id=integer is-primary=boolean type=allowedValue
has-children=boolean permission-id=integer training-group-id=integer>
<name>string</name>
<login>string</login>
</principal></permissions>
...
<permission acl-id=integer permission-id=allowedValue
principal-id=integer />
</results>
Response values
code Allowed value A code indicating the response status (see status).
permissions Container A list of principals showing their permission to access the SCO,
account, or principal.
principal Container Information about one principal showing the principal’s permission
level on the SCO, account, or principal.
is-primary Boolean A value indicating whether the principal is a primary group (same as a
built-in group).
type Allowed value The type of principal (see type for allowed values).
has-children Boolean A value indicating whether the principal has children. Groups have
children and users don’t, so if true, the principal is a group.
permission-id Allowed value The permission the principal has on the SCO, account, or principal (see
permission-id for values).
name String The name of the principal who has permission to access the SCO.
login String The login name of the principal who has permission to access the SCO.
permission Empty, with Information about the permission one principal has on a SCO,
attributes account, or principal. If empty, no permission is defined.
acl-id Integer The ID of the object on which the principal has permission.
permission-id Allowed value The permission the principal has to act on the object (see
permission-id for values).
principal-id Integer The ID of the principal who has permission to act on the object.
Sample request
https://example.com/api/xml?action=permissions-info&acl-id=2006334033
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<permissions>
<principal principal-id="2006258745" is-primary="false" type="user"
has-children="false" permission-id="host" training-group-id="2007842424">
<name>Joy Smith</name>
<login>[email protected]</login>
</principal>
...
</permissions>
</results>
See also
permissions-reset, permissions-update
permissions-reset
Availability
Breeze 4
Description
Resets all permissions any principals have on a SCO to the permissions of its parent SCO. If the parent has no
permissions set, the child SCO will also have no permissions.
Request URL
http://server_name/api/xml
?action=permissions-reset
&acl-id=integer
&session=BreezeSessionCookieValue
Parameters
acl-id Integer Y The ID of a SCO that has permissions you want to reset.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=code />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=permissions-reset&acl-id=2006334033
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
permissions-info-, permissions-update
permissions-update
Availability
Breeze 4
Description
Updates the permissions a principal has to access a SCO, using a trio of principal-id, acl-id, and permission-id.
To update permissions for multiple principals or objects, specify multiple trios. You can update more than 200
permissions in a single call to permissions-update.
Call permissions-update to give a user access to a Adobe Connect meeting, course, curriculum, or other SCO. For
example, you can use permissions-update to:
• Invite a user to a meeting as participant, presenter, or host (with a permission-id of view, mini-host, or host,
respectively)
• Remove a user’s participant, presenter, or host access to a meeting (with a permission-id of remove)
• Enroll users in courses (with a permission-id of view)
If you use multiple trios and any of them have invalid information (for example, an incorrect acl-id or principal-
id), permissions-update returns an ok status, the correct trios execute, and the invalid ones do not.
Request URL
http://server_name/api/xml
?action=permissions-update
&acl-id=integer
&principal-id=integer
&permission-id=allowedValue
&session=BreezeSessionCookieValue
Parameters
acl-id Integer Y The ID of a SCO (a sco-id) for which you want to update
permissions.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=code />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=permissions-update&acl-id=2006334033
&principal-id=2006258745&permission-id=host
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
permissions-info, permissions-reset
principal-info
Availability
Breeze 4
Description
Provides information about one principal, either a user or a group.
You must specify a principal-id. To find the principal-id, call principal-list, using a filter if necessary to limit
the response.
Request URL
http://server_name/api/xml
?action=principal-info
&principal-id=integer
&session=BreezeSessionCookieValue
Parameters
principal-id Integer Y The ID of a user or group you want information about. You can get the
ID by calling principal-list.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<contact>
<email>string</email>
<first-name>string</first-name>
<last-name>string</last-name>
</contact>
<manager account-id=integer disabled=boolean has-children=boolean
is-hidden=boolean is-primary=boolean principal-id=integer
type=allowedValue>
<ext-login>string</ext-login>
<login>string</login>
<name>string</name>
<email>string</email>
<first-name>string</first-name>
<last-name>string</last-name>
<x-customfield1>string</x-customfield1>
<x-customfield2>string</x-customfield2>
...
</manager>
<preferences acl-id=integer lang=allowedValue
time-zone-id=allowedValue />
<principal account-id=integer disabled=boolean has-children=boolean
is-hidden=boolean is-primary=boolean principal-id=integer
type=allowedValue>
<description>string</description>
<ext-login>string</ext-login>
<login>string</login>
<name>string</name>
<email>string</email>
<first-name>string</first-name>
<last-name>string</last-name>
<x-customfield1>string</x-customfield1>
<x-customfield2>string</x-customfield2>
...
</principal>
</results>
Response values
code Allowed value A code indicating the response status (see status).
contact Container Information about the contact person for a principal. If the
principal is a user, usually the same as information in principal.
disabled Datetime If the principal’s account is valid, a null value returned as "". If the
account is disabled, the date it was disabled.
has-children Boolean Whether the principal has children. Groups have children and users
don’t, so this attribute indicates whether the principal is a group.
is-hidden Boolean Whether the principal is hidden (true) or not (false) in Connect
Central or your application.
is-primary Boolean Whether the principal is a built-in group (true) or not (false).
type Allowed value The type of principal (see type for values).
ext-login String For a user, the login ID sent from an external network. By default,
the same value as login, so change it if you use external
authentication.
login String The principal’s login ID on Adobe Connect. Can be the same as an
e-mail address.
name String For a user, the full name, concatenated from first-name and
last-name.
lang Allowed value The language setting the principal has chosen for Adobe Connect
applications.
time-zone-id Allowed value The time zone setting the principal has chosen for Adobe Connect
applications.
Sample request
https://example.com/api/xml?action=principal-info&principal-id=2006258745
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<contact>
<email>[email protected]</email>
<first-name>Bob</first-name>
<last-name>Jones</last-name>
</contact>
<manager account-id="624520" disabled="" has-children="false"
is-hidden="false" is-primary="false" principal-id="2006282569"
type="user">
<ext-login>[email protected]</ext-login>
<login>[email protected]</login>
<name>jazz doe</name>
<email>[email protected]</email>
<first-name>Jazz</first-name>
<last-name>Doe</last-name>
<x-2007017651>San Francisco</x-2007017651>
</manager>
<preferences acl-id="2006258745" lang="en" time-zone-id="4" />
<principal account-id="624520" disabled="" has-children="false"
is-hidden="false" is-primary="false" principal-id="2006258745"
type="user">
<ext-login>[email protected]</ext-login>
<login>[email protected]</login>
<name>Joy Smith</name>
<email>[email protected]</email>
<first-name>Joy</first-name>
<last-name>Smith</last-name>
<x-2007017651>San Francisco</x-2007017651>
</principal>
</results>
See also
principal-list, principal-list-by-field, principal-update
principal-list
Availability
Breeze 4
Description
Provides a complete list of users and groups, including primary groups.
This call is useful for getting a principal-id when you don’t have one. However, be aware that it returns a list of all
principals on your Adobe Connect Server or Adobe Connect hosted account, unless you use a filter to limit the
response.
You can also use principal-list to get a list of groups in an account by filtering on the type and is-member fields:
https://example.com/api/xml?action=principal-list&filter-type=group
&filter-is-member=true
However, filter-type=group returns groups you have created, not built-in groups predefined on the server. Built-
in groups have type values other than group, such as admins and authors (see type for a list of the values).
You can filter the response with a filter-type parameter set to the type of group you want, then parse the response
for a principal-id, then pass the principal-id as a group-id on another request to principal-list.
Request URL
http://server_name/api/xml
?action=principal-list
&group-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
group-id Integer N The ID of a group. Same as the principal-id of a principal that has a
type value of group.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Note: Filtering on the login element is useful but slow, and reduced performance is unavoidable.
You can also filter on a special field name, manager-id, to return a list of principals who report to a given manager,
for example:
https://example.com/api/xml?action=principal-list
&filter-manager-id=2006282569
When you use filter-manager-id, each principal element in the response has a manager-id attribute:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<principal-list>
<principal principal-id="2006258745" account-id="624520" type="user"
has-children="false" is-primary="false" is-hidden="false"
manager-id="2006282569">
<name>Pat Lee</name>
<login>[email protected]</login>
<email>[email protected]</email>
</principal>
</principal-list>
</results>
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<principal-list>
<principal principal-id=integer account-id=integer type=allowedValue
has-children=boolean is-primary=boolean is-hidden=boolean
manager-id=integer training-group-id=integer>
<name>string</name>
<login>string</login>
<email>string</email>
</principal>
</principal-list>
</results>
Response values
code Allowed value A code indicating the response status (see status).
type Allowed value The type of principal (see type for values).
has-children Boolean Indicates whether the principal has children. Groups have
children and users do not, so when has-children is
true, the principal is a group.
principal-custom- Container The entire list of custom field values defined for the
field-values principal.
field Container Details about one custom field defined for the principal
(see field for contents).
Sample request
https://example.com/api/xml?action=principal-list
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<principal-list>
<principal principal-id="624526" account-id="624520" type="user"
has-children="false" is-primary="false" is-hidden="false" training-group-
id="">
<name>ned mack</name>
<login>[email protected]</login>
<email>[email protected]</email>
</principal>
<principal principal-id="624550" account-id="624520" type="user"
has-children="false" is-primary="false" is-hidden="false" training-group-
id="">
<name>amelie jones</name>
<login>[email protected]</login>
<email>[email protected]</email>
</principal>
...
</principal-list>
</results>
See also
principal-info, principal-update, principal-list-by-field
principal-list-by-field
Availability
Breeze 5
Description
Lists principals that have a specified value in a custom field. Use this action to query custom fields for principals. Use
principal-list to get a list of custom fields that are defined for the principal.
In the value parameter, enter the value of a custom database field. The name element returned by principal-list,
for example, is a full name concatenated from the first-name (bob) and last-name (jones) database fields. If you
search on bob jones, principal-list-by-field does not return a value, unless the full name is defined as a database
field (in this case, a custom field defined on principals).
The search is case insensitive, and the query string can contain spaces.
Wildcards are not allowed in the query string. For example, if you enter t*, principal-list-by-field searches for
the exact string t*.
The principal-list-by-field action searches in all custom database fields defined for the principal; it does not
search principal fields.
Request URL
http://server_name/api/xml
?action=principal-list-by-field
&value=string
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
value String Y The value for which you want to search all fields. You do not need to
enter a field name.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<principal-list>
<principal account-id=integer principal-id=integer type=allowedValue
has-children=boolean is-primary=boolean is-hidden=boolean>
<name>string</name>
<login>string</login>
</principal>
</principal-list>
</results>
Response values
code Allowed value A code indicating the response status (see status).
principal-list Container The entire list of principals that match the value in one or more
custom fields.
type Allowed value The type of principal (see type for values).
has-children Boolean Indicates whether the principal has children. Groups have
children and users don’t, so this attribute indicates whether the
principal is a group.
is-primary Boolean Whether the principal is a built-in group (true) or not (false).
is-hidden Boolean Whether the principal is hidden in the user interface (true) or not
(false).
name String The principal’s full name, concatenated from the first-name
and last-name fields.
Sample request
https://example.com/api/xml?action=principal-list-by-field&value=inactive
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<principal-list>
<principal account-id="624520" principal-id="2616099" type="user"
has-children="false" is-primary="false" is-hidden="false">
<name>Bob Jones</name>
<login>[email protected]</login>
</principal>
</principal-list>
</results>
See also
principal-info, principal-list, principal-update
principals-delete
Availability
Breeze 4
Description
Removes one or more principals, either users or groups. To delete principals, you must have Administrator privilege.
To delete multiple principals, specify multiple principal-id parameters. All of the principals you specify will be
deleted.
The principal-id can identify either a user or group. If you specify a user, the user is removed from any groups the
user belongs to. If you specify a group, the group is deleted, but the users who belong to it are not.
Request URL
http://server_name/api/xml
?action=principals-delete
&principal-id=integer
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=principals-delete
&principal-id=2006339311&principal-id=2006339323
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
principal-info, principal-list, principal-list-by-field, principal-update
principal-update
Availability
Breeze 4
Description
Creates a principal (a user or group) or updates a standard field for a principal. The principal is created or updated in
the same account as the user making the call.
To create a new principal, call principal-update without specifying a principal-id. To update, add the
principal-id. Before you update metadata about a principal, call principal-info to get the existing version.
If a principal has custom fields, use acl-field-update to update them, rather than principal-update.
Request URL
http://server_name/api/xml
?action=principal-update
&description=string
&email=string
&first-name=string
&has-children=boolean
&last-name=string
&login=string
&name=string
&password=string
&principal-id=integer
&send-email=boolean
&type=allowedValue
&session=BreezeSessionCookieValue
Parameters
description String N The new group’s description. Use only when creating a new group.
email String N The user’s e-mail address. Can be different from the login. Be sure to
specify a value if you use send-email=true.
first-name String Y/N The user’s new first name. Use only with users, not with groups. Required to
create a user.
has-children Boolean Y Whether the principal has children. If the principal is a group, use 1 or true.
If the principal is a user, use 0 or false.
last-name String Y/N The new last name to assign to the user. Required to create a user. Do not
use with groups.
login String Y/N The principal’s new login name, usually the principal’s e-mail address. Must
be unique on the server. Required to create or update a user. Do not use
with groups.
name String Y/N The new group’s name. Use only when creating a new group. Required to
create a group.
password String N The new user’s password. Use only when creating a new user.
principal-id String Y/N The ID of the principal that has information you want to update. Required
to update a user or group, but do not use to create either.
send-email Boolean N A flag indicating whether the server should send an e-mail to the principal
with account and login information.
type String Y/N The type of principal. Use only when creating a new principal (see type for
values).
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<principal principal-id=integer account-id=integer
has-children=integer type=integer>
<login>string</login>
<ext-login>string</ext-login>
<name>string</name>
</principal>
</results>
Response values
code Allowed value A code indicating the response status (see status).
account-id Integer The ID of the account the new user belongs to. Same as the account of the
current user.
has-children Boolean Whether the principal has children, which indicates whether the principal is
a user or group (1 if a group, or 0 if a user).
type Allowed value The type of principal (see type for values).
ext-login String The principal’s external authentication ID. By default, the value is the same
as login, unless you explicitly set the value to an authentication ID from your
network.
name String The principal’s name. If the principal is a user, concatenated from the
first-name and last-name parameters in the request.
Sample request
https://example.com/api/xml?action=principal-update&first-name=jake
&last-name=doe&has-children=0&[email protected]&type=user
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<principal principal-id="2006403978" account-id="624520" type="user"
has-children="0">
<login>[email protected]</login>
<ext-login>[email protected]</ext-login>
<name>jake doe</name>
</principal>
</results>
See also
principal-info, principal-list, principal-list-by-field, acl-field-update
report-meeting-session-users
Availability
Adobe Connect 8.1
Description
Provides information about all the user sessions for an Adobe Connect meeting session. A user session is created when
a participant enters a meeting session. As more participants join the meeting, they join the meeting session. The user
session ends when the user leaves the meeting session. When a new participant enters an empty meeting, a new
meeting session and new user session is started.
Request URL
http://server_name/api/xml
?action=report-meeting-session-users
&sco-id=integer
&asset-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
sco-id Integer Y The ID of a meeting for which you want user session information.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8"?>
<results>
<status code="ok"/>
<report-meeting-session-users>
<row principal-id=integer>
<principal-name>string</principal-name>
<date-created>datetime</date-created>
<date-end>datetime</date-end>
</row>
...
</report-meeting-session-users>
</results>
Response values
code Allowed value A code indicating the response status (see status).
date-created Datetime The date and time the user-session was created when the
participant entered the meeting session.
date-end Datetime The date and time the user-session ended when the
participant exited the meeting session.
Sample request
https://example.com/api/xml?action=report-meeting-session-users&sco-id=2006811328&asset-
id=446653455
Sample response
<?xml version="1.0" encoding="utf-8"?>
<results>
<status code="ok"/>
<report-meeting-session-users>
<row principal-id="52904333">
<principal-name>John Doe</principal-name>
<date-created>2011-08-30T15:46:46.190-04:00</date-
created>
<date-end>2011-08-30T16:51:30.950-04:00</date-end>
</row>
</report-meeting-session-users>
</results>
quota-threshold-info
Availability
Acrobat Connect Pro 7
Description
Provides the list of quotas for which capacity notifications are provided, along with their current threshold settings.
Each Adobe Connect account has system quotas that determine, for example, how many seats are available for Meeting
Hosts, Learners, and so on. Each quota has a threshold; when the threshold is crossed, the system notifies
administrators that the quota is in danger of being reached. The settings for the threshold and the notifications vary
depending on the quota.
Request URL
https://example.com/api/xml
?action=quota-threshold-info
&account-id=integer
&session=integer
Parameters
account-id Integer N The ID of the account for which you want quota threshold information. If
you don’t specify an ID, the current account to which the user is logged in
is used.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<Principals>
<Principal principal-id="integer" type="string"/>
</Principals>
<Quotas>
<Quota acl-id="integer" quota-id="string" threshold-pct="integer" login-
notif="boolean" email-notif="boolean" monthly-emails="boolean" limit="integer"
used="integer"/>
<Quota acl-id="integer" quota-id="string" threshold-pct="integer" login-
notif="boolean" email-notif="boolean" monthly-emails="boolean" limit="intger"
used="integer"/>
</Quotas>
<Trees>
<Tree tree-id="integer" type="string"/>
</Trees>
</results>
Response values
code Allowed value A code indicating the response status (see status).
Principals Container Lists the principals specifying the groups for which system capacity
notifications are provided.
Principal Container Information about the principal for which system capacity notification
is provided.
type String The group type. Depending on the license, this value can be one of
the following:
• authors
quota-id Integer The ID of the quota. For possible values, see quota-ID.
login-notif Boolean Whether administrators are notified upon logging in that a threshold
is exceeded (true) or not (false).
email-notif Boolean Whether administrators are notified through e-mail that a threshold is
exceeded (true) or not (false).
monthly-emails Boolean Whether administrators are sent monthly threshold reports through
e-mail (true) or not (false).
Trees Container Provides information about the tree type quotas (the quota for the
number of concurrent users per meeting).
type String The tree type, which is one of the following values:
• meetings
• user-meetings
Sample request
https://example.com/api/xml?action=quota-threshold-info&account-id=7
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
<Principals>
<Principal principal-id="20013" type="authors"/>
<Principal principal-id="10051" type="live-admins"/>
</Principals>
<Quotas>
<Quota acl-id="7" quota-id="training-user" threshold-pct="90" login-notif="true"
email-notif="true" monthly-emails="true" limit="10" used="0"/>
<Quota acl-id="20013" quota-id="num-of-members-quota" threshold-pct="10" login-
notif="true" email-notif="true" monthly-emails="true" limit="10" used="3"/>
</Quotas>
<Trees/>
</results>
quota-threshold-exceeded
Availability
Acrobat Connect Pro 7
Description
Returns information about system quota thresholds that have been exceeded.
Each Adobe Connect account has system quotas that determine, for example, how many seats are available for Meeting
Hosts, Learners, and so on. Each quota has a threshold; when the threshold is crossed, the system notifies
administrators that the quota is in danger of being reached. The threshold varies depending on the quota. For more
information about automatic notification, see Adobe Connect User Guide.
Request URL
https://example.com/api/xml
?action=quota-threshold-exceeded
&account-id=Integer
&acl-id=Integer
"a-id=String
&num-of-days=Integer
&session=String
Parameters
account-id Integer N The ID of the account. Specify either account-id or acl-id (not both). If you
do not specify either account-id or acl-id, results are returned for the
account which the current user is logged into.
If you specify account-ID, results are returned for all quota thresholds
that have been reached in the account.
acl-id Integer N The ID of the SCO, account, or principal for which you want threshold
information. Can be a valid sco-id, account-id, or principal-id. If
you do not specify a value for acl-id, the value for account-id is used.
The value to use for acl-id depends on the quota ID used; for more
information, see “quota-ID” on page 266
quota-id String N The ID of the system quota for which you want information. For available
values, see “quota-ID” on page 266.
num-of-days Integer N Number of days from the current day for which records are retrieved. If
you do not specify a value, all the previous records for the specified quotas
are retrieved.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<Records>
<Record acl-id="Integer" quota-id="String" peak-used="Integer" count="Integer"
threshold-pct="Integer" sco-id="Integer">
<record-date>Date</record-date>
</Record>
</Records>
</results>
Response values
code Allowed value A code indicating the response status (see status).
quota-id String The ID of the quota returned. For available values, see quota-ID.
peak-used Integer The peak value of quota used on the specified date. This attribute is
null for training and group quotas.
count Integer Number of times the threshold was crossed for the quota on the
specified date. This attribute is null for training and group quotas.
sco-id Integer The ID of the meeting for which the threshold was crossed. This
attribute is applicable only for the quota ID concurrent-users-
per-meeting; for other quotas, it is null.
Record-date Date Date when the threshold was crossed (UTC), in MM/DD/YYYY format.
Sample request
https://example.com/api/xml?action=quota-threshold-exceeded&acl-id=20013"a-id=num-of-
members-quota&num-of-days=30
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok"/>
<Records>
<Record acl-id="20013" quota-id="num-of-members-quota" peak-used="" count=""
threshold-pct="10" sco-id="">
<record-date>11/20/2007</record-date>
</Record>
</Records>
</results>
quota-threshold-update
Availability
Acrobat Connect Pro 7
Description
Updates the threshold settings of the specified quotas.
Each Adobe Connect account has system quotas that determine, for example, how many seats are available for meeting
hosts, trainers, training managers, and so on. Each quota has a threshold; when the threshold is crossed, the system
notifies administrators that the quota is in danger of being reached. The settings for the thresholds and notifications
vary depending on the quota, and you can configure the settings using this action.
Request URL
https://example.com/api/xml
?action=quota-threshold-update
&account-id=integer
&acl-id=integer
"a-id=string
&threshold-pct=integer
&login-notif=Boolean
&email-notif=Boolean
&monthly-emails=Boolean
Parameters
account-id Integer N The ID of the account for which quota settings are updated.
acl-id Integer Y The ID of the SCO, account, or principal for which you want threshold
information. Can be a valid sco-id, account-id, or principal-id. If
you do not specify a value for acl-id, the value for account-id is used.
The value to use for acl-id depends on the quota ID used; for more
information, see quota-ID.
quota-id String Y The ID of the quota whose settings are updated. For available values, see
quota-ID.
threshold-pct Integer Y The percent threshold for the quota. The lower the value, the more
frequently administrators are notified when the threshold is exceeded (if
notifications are enabled).
email-notif Boolean Y Specifies whether to notify administrators through e-mail that a threshold
is exceeded (true) or not (false).
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=quota-threshold-update&account-id=7&acl-id=7"a-
id=training-user&threshold-pct=90&login-notif=false&email-notif=true&monthly-emails=true
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
quota-threshold-info, quota-threshold-exceededquota-threshold-exceeded
report-active-meetings
Availability
Breeze 4
Description
Returns a list of Adobe® Connect™ meetings that are currently in progress, including the number of minutes the
meeting has been active.
For report-active-meetings to return results, at least one user must be present in at least one meeting room. If
meetings are scheduled at present, but no users are attending those meetings, report-active-meetings returns an
empty response.
Request URL
http://server_name/api/xml
?action=report-active-meetings
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<results>
<status code=allowedValue />
<report-active-meetings>
<sco sco-id=integer active-participants=integer
length-minutes=integer>
<name>string</name>
<url-path>string</url-path>
<date-begi>datetime</date-begin>
</sco>
</report-active-meetings>
</results>
Response values
url-path String The part of the meeting URL that comes after the
domain and is unique to this meeting.
Sample request
https://example.com/api/xml?action=report-active-meetings
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-active-meetings>
<sco sco-id="2006778715" active-participants="" length-minutes="1">
<name>Designing Online Courses</name>
<url-path>/online/</url-path>
<date-begin>2006-06-28T14:35:21.307-07:00</date-begin>
</sco>
</report-active-meetings>
</results>
report-bulk-consolidated-transactions
Availability
Breeze 5
Description
Returns information about principal-to-SCO transactions on your Adobe Connect server or in your Adobe Connect
hosted account.
A transaction is an instance of one principal visiting one SCO. The SCO can be a Adobe Connect meeting, course,
document, or any content on the server.
These are all examples of transactions:
• If a principal attends a meeting twice, two transactions exist: one for each time the principal attended the meeting.
• If five people attend a meeting, five transactions exist: one for each user who attended the meeting.
• If a principal takes two courses three times each and passes each only on the third try, six transactions exist: one for
each attempt on each course.
This call returns all transactions, so consider using a filter to reduce the volume of the response. For example, if you
use filter-type=meeting, the call returns all meeting transactions:
https://example.com/api/xml?action=report-bulk-consolidated-transactions
&filter-type=meeting
From the response, you can calculate Adobe Connect meeting usage by comparing times in date-created and date-
closed (see “ “Calculate meeting usage” on page 40”). However, this call to report-bulk-consolidated-
transactions, with filter-type=meeting, returns only users who logged in to the meeting as participants, not
users who entered the meeting as guests.
Request URL
http://server_name/api/xml
?action=report-bulk-consolidated-transactions
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-bulk-consolidated-transactions>
<row transaction-id=integer sco-id=integer type=allowedValue
principal-id=integer score=integer>
<name>string</name>
<url>relativeUrl</url>
<login>string</login>
<user-name>string</user-name>
<status>allowedValue</status>
<date-created>datetime</date-created>
<date-closed>datetime</date-closed>
</row>
...
</report-bulk-consolidated-transactions>
</results>
Response values
type Allowed value The type of the SCO (see type for allowed
values).
Sample request
https://example.com/api/xml?action=report-bulk-consolidated-transactions
&filter-type=meeting
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-bulk-consolidated-transactions>
<row transaction-id="2006905086" sco-id="2006905049" type="meeting"
principal-id="2006258745" score="0">
<name>Celebrate End of June Meeting</name>
<url>/endjune/</url>
<login>[email protected]</login>
<user-name>Joy Smith</user-name>
<status>completed</status>
<date-created>2006-06-30T11:10:37.003-07:00</date-created>
<date-closed>2006-06-30T11:45:21.397-07:00</date-closed>
</row>
<row transaction-id="2006905795" sco-id="2006905049" type="meeting"
principal-id="2006258745" score="0">
<name>Celebrate End of June Meeting</name>
<url>/endjune/</url>
<login>[email protected]</login>
<user-name>Joy Smith</user-name>
<status>completed</status>
<date-created>2006-06-30T17:58:29.060-07:00</date-created>
<date-closed>2006-06-30T17:59:09.970-07:00</date-closed>
</row>
...
</report-bulk-consolidated-transactions>
</results>
See also
report-bulk-objects, report-bulk-questions, report-bulk-slide-views, report-bulk-users
report-bulk-objects
Availability
Breeze 5
Description
Returns information about all objects (SCOs) on a licensed Adobe Connect Server or in a Adobe Connect hosted
account. The object types returned include archive, attachment, authorware, captivate, course, curriculum,
external-event, flv, image, meeting, presentation, and swf.
Because the response is likely to be large, use filters to limit it. For example, to return a list of all meetings on the server,
filter on the type field:
http://example.com/api/xml?action=report-bulk-objects&filter-type=meeting
Request URL
http://server_name/api/xml
?action=report-bulk-objects
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-bulk-objects>
<row sco-id=integer type=allowedValue>
<url>string</url>
<name>string</name>
<date-created>datetime</date-created>
<date-end>datetime</date-end>
<date-modified>datetime</date-modified>
<description>datetime</description>
</row>
...
</report-bulk-objects>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-bulk-objects Container The entire list of SCOs on the server; or, if a filter is used, the entire
list of SCOs that matches the filter.
url String The unique identifier of the training SCO, placed in the URL after
the domain name.
date-created Datetime The date the SCO was created. For a meeting, the date and time
the meeting starts.
Sample request
http://example.com/api/xml?action=report-bulk-objects&filter-type=meeting
&filter-gt-date-created=2006-06-01
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-bulk-objects>
<row sco-id="2006778715" type="meeting">
<url>/online/</url>
<name>Designing Online Courses</name>
<date-created>2006-06-28T14:15:00.000-07:00</date-created>
<date-end>2006-06-28T14:30:00.000-07:00</date-end>
<date-modified>2006-07-13T14:57:54.150-07:00</date-modified>
</row>
...
</report-bulk-objects>
</results>
See also
report-bulk-consolidated-transactions, report-bulk-questions, report-bulk-slide-views, report-
bulk-users
report-bulk-questions
Availability
Breeze 5
Description
Returns information about every quiz question in the account you are logged in to.
The response includes a combination of the quiz question, the answer, the ID of the user who answered, and the ID of
the transaction.
This action returns all question-and-answer combinations in the account, unless you use a filter to limit the size of the
response.
Request URL
http://server_name/api/xml
?action=report-bulk-questions
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-bulk-questions>
<row transaction-id=integer score=integer principal-id=integer>
<question>string</question>
<response>string</response>
<date-created>datetime</date-created>
</row>
...
</report-bulk-questions>
</results>
Response values
code Allowed value A code indicating the response status (see status).
principal-id Integer The ID of the user who answered or viewed the question.
date-created Datetime The date and time the user answered the question.
Sample request
https://example.com/api/xml?action=report-bulk-questions
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-bulk-questions>
<row transaction-id="2006335803" score="10" principal-id="2006258745">
<question>The capital of California is<1></question>
<response>Sacramento</response>
<date-created>2006-05-11T15:50:23.643-07:00</date-created>
</row>
<row transaction-id="2006335827" score="0" principal-id="2006258745">
<question>The capital of California is<1></question>
<response>san francisco</response>
<date-created>2006-05-11T17:32:53.970-07:00</date-created>
</row>
</report-bulk-questions>
</results>
See also
report-bulk-objects, report-bulk-consolidated-transactions, report-bulk-slide-views, report-
bulk-users
report-bulk-slide-views
Availability
Breeze 5
Description
Returns information about each occasion on which a principal views a slide. The slide can be in any presentation in
the account the current user belongs to.
Each slide view is a transaction. A transaction is an interaction between a user and any SCO on Adobe Connect. In this
case, the transaction is between a user and a slide.
This action returns all occurrences of principals viewing slides in the account, unless you filter the response.
Request URL
http://server_name/api/xml
?action=report-bulk-slide-views
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-bulk-slide-views>
<row transaction-id=integer principal-id=integer>
<page>integer</page>
<date-created>datetime</date-created>
</row>
...
</report-bulk-slide-views>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-bulk-slide-views Container The entire list of slide views that match the request.
transaction- Integer The ID of the interaction between the user and the slide.
id
date-created Datetime The date and time the user viewed the slide.
Sample request
https://example.com/api/xml?action=report-bulk-slide-views
&filter-principal-id=123456
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-bulk-slide-views>
<row transaction-id="2006334916" principal-id="123456">
<page>0</page>
<date-created>2006-05-11T12:02:01.470-07:00</date-created>
</row>
<row transaction-id="2006334916" principal-id="123456">
<page>0</page>
<date-created>2006-05-11T12:02:01.487-07:00</date-created>
</row>
...
</report-bulk-slide-views>
</results>
See also
report-bulk-objects, report-bulk-questions, report-bulk-consolidated-transactions, report-bulk-
users
report-bulk-users
Availability
Breeze 5
Description
Returns information about all users in an account. The difference between this call and principal-list is that
principal-list returns both users and groups, while report-bulk-users returns only users.
The response from report-bulk-users can be quite large, especially if you use custom fields, so remember that you
can filter and sort it. For example, the following call returns a list of all users who have the letters Jo in their name, in
ascending order by name:
http://myserver.com/api/xml?action=report-bulk-users&sort-name=asc
&filter-like-name=Jo
If you pass custom-fields=true, by default report-bulk-users returns up to eight custom fields defined for users.
If you have defined more than eight custom fields for users, report-bulk-users returns the first eight in the list in
the Customize User Profile screen in Connect Central (at Administration > Users and Groups > Customize User
Profile).
If you use Adobe Connect Server, you can set a value for REPORT_MAX_CUSTOM_FIELDS in the custom.ini file to have
report-bulk-users return more than eight custom fields. You can use any value, but higher values risk a greater
impact to database performance. You cannot change this setting on a Adobe Connect hosted account.
Request URL
http://server_name/api/xml
?action=report-bulk-users
&custom-fields=boolean
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
You can use filter-type with report-bulk-users to filter the type of users returned (user or guest).
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-bulk-users>
<row principal-id=integer type="string">
<login>string</login>
<name>string</name>
<email>string</email>
<manager>string</manager>
.. any custom fields ..
</row>
...
</report-bulk-users>
</results>
Response values
code Allowed value A code indicating the response status (see status).
name String The full name of the user, concatenated from the user’s first name
and last name.
manager String The user’s manager, also a registered user. Returned if a manager
has been set for the user. Not returned if custom-fields is true
in the request.
Sample request
https://example.com/api/xml?action=report-bulk-users&filter-like-name=john
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-bulk-users>
<row principal-id="5417288" type="guest">
<login>[email protected]</login>
<name>John Owens</name>
<email>[email protected]</email>
</row>
<row principal-id="5417255" type="user">
<login>[email protected]</login>
<name>John Smith</name>
<email>[email protected]</email>
</row>
...
</report-bulk-users>
</results>
See also
report-bulk-objects, report-bulk-questions, report-bulk-slide-views, report-bulk-consolidated-
transactions
report-course-status
Availability
Breeze 4
Description
Returns summary information about a course, including the number of users who have passed, failed, and completed
the course, as well as the current number of enrollees. The request requires the sco-id of a course.
Connect Central uses this call to display Course Status in the Summary report. This report is available at Training >
Shared Training > [course name] > Reports > Summary.
Request URL
http://server_name/api/xml
?action=report-course-status
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
sco-id Integer Y The unique ID of the course for which you want summary
information.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-course-status total-course-completions=integer
total-unique-course-completions=integer num-passed=integer
num-failed=integer num-enrollees=integer />
<date-last-taken>datetime</date-last-taken>
</report-course-status>
</results>
Response values
Sample request
https://example.com/api/xml?action=report-course-status&sco-id=123456
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-course-status total-course-completions="1"
total-unique-course-completions="1" num-completed="0"
num-passed="1" num-failed="0" num-enrollees="4">
<date-last-taken>2006-10-10T13:55:24.480-07:00</date-last-taken>
</report-course-status>
</results>
report-curriculum-taker
Availability
Connect Enterprise 6
Description
Returns information about a user’s progress in a curriculum.
The response includes a row element for each course in the curriculum, which has information such as access to the
course, whether credit was granted, the user’s score, the unique url-path to the course, and so on.
Request URL
http://server_name/api/xml
?action=report-curriculum-taker
&user-id=integer
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
user-id Integer Y The ID of the user whose scores you want to check.
sco-id Integer Y The unique ID of the curriculum for which you want a summary.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-curriculum-taker>
<sco transcript-id=integer path-type=allowedValue asset-id=integer
sco-id=integer depth=integer folder-id=integer
type=integer icon=allowedValue lang=allowedValue
max-retries=integer source-sco-id=integer
source-sco-type=allowedValue status=allowedValue score=integer
certificate=integer max-score=integer attempts=integer>
<access>allowedValue</access>
<credit-granted>boolean</credit-granted>
<name>string</name>
<url-path>string</url-path>
<date-modified>datetime</date-modified>
<override>boolean</override>
</sco>
</report-curriculum-taker>
</results>
Response values
path-type Allowed value The learning path a user must take before
attempting this course or curriculum (see
path-type for allowed values).
icon Allowed value The type of icon that identifies the course or
curriculum in Connect Central (see icon for
values).
status Allowed value The status of the user’s attempt to use the
course or curriculum.
access Allowed value The level of access the user has to the course or
curriculum (see access for allowed values).
url-path String The part of the URL after the domain name
that uniquely identifies the object on the
server.
date-modified Datetime The date and time the SCO was last modified,
in ISO 8601 format.
Sample request
https://example.com/api/xml?action=report-curriculum-taker
&user-id=2006258748&sco-id=2006298444
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-curriculum-taker>
<sco transcript-id="2006905613" path-type="prereq-none"
asset-id="2006334911" sco-id="2006334909" depth="0"
folder-id="2006258747" type="content" icon="producer"
lang="en" max-retries="" source-sco-id="" source-sco-type=""
status="user-failed" score="0" certificate="" max-score="0"
attempts="5">
<access>access-open</access>
<credit-granted>false</credit-granted>
<name>Test Quiz</name>
<url-path>/quiz/</url-path>
<date-created>2006-06-30T15:24:34.897-07:00</date-created>
<date-modified>2006-05-16T15:22:25.703-07:00</date-modified>
<date-taken>2006-06-30T15:24:34.897-07:00</date-taken>
<override>false</override>
</sco>
</report-curriculum-taker>
</results>
report-meeting-attendance
Availability
Breeze 4
Description
Returns a list of users who attended a Adobe Connect meeting. The data is returned in row elements, one for each
person who attended. If the meeting hasn’t started or had no attendees, the response contains no rows.The response
does not include meeting hosts or users who were invited but did not attend.
To call report-meeting-attendance, you must have publish, mini-host, or host permission on the meeting (see
permission-id for details).
Request URL
http://server_name/api/xml
?action=report-meeting-attendance
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-meeting-attendance>
<row transcript-id=integer sco-id=integer principal-id=integer
answered-survey=boolean>
<login>string</login>
<session-name>string</session-name>
<sco-name>string</sco-name>
<date-created>datetime</date-created>
<date-end>datetime</date-end>
<participant-name>string</participant-name>
</row>
...
</report-meeting-attendance>
</results>
Response values
session-name String The name of the user who entered the meeting
room, creating a session.
Sample request
https://example.com/api/xml?action=report-meeting-attendance
&sco-id=2006778715
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-meeting-attendance>
<row transcript-id="2006778723" sco-id="2006778715"
principal-id="2006258745" answered-survey="0">
<login>[email protected]</login>
<session-name>Joy Smith</session-name>
<sco-name>Designing Online Courses</sco-name>
<date-created>2006-06-28T14:35:21.307-07:00</date-created>
<date-end>2006-06-28T15:09:05.447-07:00</date-end>
<participant-name>Joy Smith</participant-name>
</row>
</report-meeting-attendance>
</results>
report-meeting-concurrent-users
Availability
Breeze 4
Description
Returns the maximum number of users in Adobe Connect meetings concurrently in the last 30 days, and the number
of times the maximum has been reached. The maximum is the peak number of users in any meetings at a single
moment, whether one meeting, multiple concurrent meetings, or multiple overlapping meetings.
You can change the time period to a period greater than 30 days by adding a length parameter, for example,
length=120.
The maximum number of users (max-users) is determined by the account license and applies to the server overall,
not to a specific meeting. This action also returns the number of times in the current month the maximum has been
reached (max-participants-freq).
Request URL
http://server_name/api/xml
?action=report-meeting-concurrent-users
&length=integer
&session=BreezeSessionCookieValue
Parameters
length Integer N The number of days in the time period to check for concurrent
meeting usage. Use a value greater than 30. The default value
is 30.
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<results>
<status code=allowedValue />
<report-meeting-concurrent-users max-users=integer
max-participants-freq=integer />
</results>
Response values
Sample request
https://example.com/api/xml?action=report-meeting-concurrent-users
Sample response
<results>
<status code="ok" />
<report-meeting-concurrent-users max-users="400"
max-participants-freq="1" />
</results>
report-meeting-sessions
Availability
Breeze 4
Description
Provides information about all the sessions of a Adobe Connect meeting. A session is created when a participant enters
an empty meeting. As more participants join the meeting, they join the session. The session ends when all attendees
leave the meeting. When a new participant enters the now-empty meeting, a new session starts. For example, a
recurring weekly meeting has a session each week when the meeting is held.
You can call report-meeting-sessions on past meetings, active meetings, or future meetings, but future meetings
are not likely to have sessions.
Request URL
http://server_name/api/xml
?action=report-meeting-sessions
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
sco-id Integer Y The ID of a meeting for which you want session information.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-meeting-sessions>
<row sco-id=integer asset-id=integer version=integer
num-participants=integer>
<date-created>datetime</date-created>
<date-end>datetime</date-end>
</row>
...
</report-meeting-sessions>
</results>
Response values
code Allowed value A code indicating the response status (see status).
date-created Datetime The date and time the session was created, when the
participant entered the meeting room.
date-end Datetime The date and time the session ended, when the
participant left the meeting room.
Sample request
https://example.com/api/xml?action=report-meeting-sessions
&sco-id=2006811328
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-meeting-sessions>
<row sco-id="2006811328" asset-id="2006811333" version="1"
num-participants="1">
<date-created>2006-06-29T11:46:52.210-07:00</date-created>
<date-end>2006-06-29T13:34:43.410-07:00</date-end>
</row>
</report-meeting-sessions>
</results>
report-meeting-summary
Availability
Breeze 4
Description
Returns summary information about a specific Adobe Connect meeting. The results indicate how many users were
invited, how many invited participants and guests attended, and other information about the meeting.
To use report-meeting-summary, you need publish, host, or mini-host permission on the meeting. With one of
these permissions, you can run report-meeting-summary on a current, completed, or future meeting. The results are
most useful for a completed meeting.
A meeting might be recurring (for example, a weekly staff meeting) and have an occurrence each time the meeting is
held. If the meeting is recurring, the statistics returned by report-meeting-summary are cumulative, applying to all
occurrences of the meeting, not just the latest one.
Request URL
http://server_name/api/xml
?action=report-meeting-summary
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
sco-id Integer Y The unique ID of a meeting for which you have publish or host
permission.
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-meeting-summary num-unique-meetings=integer peak-users=integer
num-invitees=integer num-invitees-attended=integer ispublic=boolean
num-guests-attended=integer />
</results>
Sample request
https://example.com/api/xml?action=report-meeting-summary&sco-id=2006334033
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-meeting-summary num-unique-meetings="1" peak-users="1"
num-invitees="1" num-invitees-attended="1" ispublic="1"
num-guests-attended="0">
<most-recent-session>
2006-06-28T15:11:15.133-07:00
</most-recent-session>
</report-meeting-summary>
</results>
report-my-courses
Availability
Breeze 4
Description
Provides information about each course the current user is or was enrolled in.
The returned courses include future courses, past courses, and courses the user is presently taking. The list of courses
can be quite large, so remember to use a filter to reduce the response.
Each course has a permission-id that shows the level of access the user has to the course. For example, the access
might be view, publish, or manage.
Request URL
http://server_name/api/xml
?action=report-my-courses
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<my-courses>
<course sco-id=integer type="content" icon="course"
permission-id=allowedValue>
<name>string</name>
<description>string</description>
<url>string</url>
<date-created>datetime</date-created>
<date-modified>datetime</date-modified>
<date-begin>datetime</date-begin>
<url-path>string</url-path>
<expired>boolean</expired>
<completed>boolean</completed>
</course>
...
</my-courses>
</results>
Response values
code Allowed value A code indicating the response status (see status).
my-courses Container Information about all courses the user is enrolled in.
course Container Information about one course the user is enrolled in.
type Allowed value The type of the course (for allowed values, see type).
icon Allowed value The type of icon that identifies the course in the user interface. For a
course, always course.
permission-id Allowed value The level of permission the user has on the course (see permission-
id for values).
url String The URL at which a user can reach the course on the server. Includes
the domain name and the course identifier.
date-created Datetime The date and time the course was created.
date-modified Datetime The date and time the course was last modified.
date-begin Datetime The date and time the course is available for users to start.
url-path String The part of the course URL that is the course identifier, after the
domain name.
expired Boolean Whether the course has expired (true if it has, false if it has not).
completed Boolean Whether the user has completed the course (true if yes, false if no).
Sample request
https://example.com/api/xml?action=report-my-courses
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<my-courses>
<course sco-id="2006298431" type="content" icon="course"
permission-id="view">
<name>Test Course</name>
<url>example.com/test/</url>
<date-created>2006-05-03T10:21:46.810-07:00</date-created>
<date-modified>2006-05-03T10:22:30.803-07:00</date-modified>
<date-begin>2006-05-03T10:15:00.000-07:00</date-begin>
<url-path>/test/</url-path>
<expired>false</expired>
<completed>false</completed>
</course>
</my-courses>
</results>
report-my-events
Availability
Breeze 5
Description
Provides information about each event the current user has attended or is scheduled to attend. The user can be either
a host or a participant in the event. The events returned are those in the user’s my-events folder.
To obtain information about all events on your Adobe Connect Server or in your Adobe Connect hosted account, call
sco-shortcuts to get the sco-id of the events folder. Then, call sco-contents with the sco-id to list all events.
Request URL
http://server_name/api/xml
?action=report-my-events
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<my-events>
<event sco-id=integer type="event" icon="event"
permission-id=allowedValue>
<name>string</name>
<domain-name>string</domain-name>
<url-path>string</url-path>
<date-begin>datetime</date-begin>
<date-end>datetime</date-end>
<expired>boolean</expired>
<duration>datetime/duration>
</event>
...
</my-events>
</results>
Response values
code Allowed value A code indicating the response status (see status).
my-events Container The entire list of events the user is or has been registered for.
type Allowed value The type of the object. For an event, always event.
icon Allowed value An icon identifying the object. For an event, always event.
permission-id Allowed value The permission the user has for the event (see permission-id for
values).
domain-name String The domain name of the Adobe Connect server, which comes after
http:// (or https://) and before the unique event name in the
event URL.
url-path String The unique event name, which comes after the domain name in the
event URL.
date-begin Date The date the event begins, in ISO 8601 format.
date-end Date The date the event ends, in ISO 8601 format.
expired Boolean A value indicating whether the event has ended. If the event is
currently underway, the value is false.
duration Time The amount of time the event is scheduled to last. Uses the time
portion of an ISO 8601 date format.
Sample request
https://example.com/api/xml?action=report-my-events
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<my-events>
<event sco-id="2006334107" type="event" icon="event"
permission-id="host">
<name>Meet the Famous Author</name>
<domain-name>example.com</domain-name>
<url-path>/author/</url-path>
<date-begin>2006-05-12T18:00:00.000-07:00</date-begin>
<date-end>2006-05-12T20:00:00.000-07:00</date-end>
<expired>true</expired>
<duration>02:00:00.000</duration>
</event>
</my-events>
</results>
report-my-meetings
Availability
Breeze 4
Description
Provides information about all Adobe Connect meetings for which the user is a host, invited participant, or registered
guest. The meeting can be scheduled in the past, present, or future.
Request URL
http://server_name/api/xml
?action=report-my-meetings
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<my-meetings>
<meeting sco-id=integer type="meeting" icon="meeting"
permission-id=allowedValue active-participants=integer>
<name>string</name>
<description>string</description>
<domain-name>domain</domain-name>
<url-path>url</url-path>
<date-begin>date</date-begin>
<date-end>date</date-end>
<expired>boolean</expired>
<duration>time</duration>
</meeting>
...
</my-meetings>
</results>
Response values
code Allowed value A code indicating the response status (see status).
my-meetings Container Information about all meetings the user is, or has been,
invited to.
type Allowed value The type of the object returned (for this call, always
meeting).
icon Allowed value The icon that visually identifies the meeting in Connect
Central (for this call, always meeting).
permission-id Allowed value The level of permission the user has to the meeting (see
permission-id for values).
domain-name String The domain name portion of the URL to the meeting room.
url-path String The part of the meeting room URL that identifies the
meeting and comes after the domain name.
date-begin Datetime The date and time the meeting begins (or has begun).
date-end Datetime The date and time the meeting ends (or has ended).
expired Boolean Whether the meeting has ended (true if it has, false if it
has not).
duration Time The actual length of time of the meeting. This may be
longer or shorter than the time the meeting was scheduled
for.
Sample request
https://example.com/api/xml?action=report-my-meetings
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<my-meetings>
<meeting sco-id="2006334033" type="meeting" icon="meeting"
permission-id="host" active-participants="0">
<name>How to Write a Novel</name>
<domain-name>example.com</domain-name>
<url-path>/novel/</url-path>
<date-begin>2006-05-11T11:30:00.000-07:00</date-begin>
<date-end>2006-05-11T12:30:00.000-07:00</date-end>
<expired>true</expired>
<duration>01:00:00.000</duration>
</meeting>
<meeting sco-id="2006743452" type="meeting" icon="meeting"
permission-id="host" active-participants="0">
<name>Intro to Film</name>
<domain-name>example.com</domain-name>
<url-path>/film/</url-path>
<date-begin>2006-06-09T14:00:00.000-07:00</date-begin>
<date-end>2006-06-09T20:00:00.000-07:00</date-end>
<expired>true</expired>
<duration>06:00:00.000</duration>
</meeting>
</my-meetings>
</results>
report-my-training
Availability
Connect Enterprise 6
Description
Returns a list of all courses and curriculums a user or group is enrolled in. If you do not use a principal-id, the list
is for the current user. If you add a principal-id, the list is for the principal you specify.
The response contains a list of row elements. In the list, courses have the attributes type=content and icon=course,
while curriculums have type=curriculum and icon=curriculum.
Request URL
http://server_name/api/xml
?action=report-my-training
&principal-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
principal-id Integer N The unique ID of a user or group whose courses and curriculums
you want to list. If you do not specify a value, the response is for the
current user.
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-my-training>
<row sco-id=integer type=allowedValue icon=allowedValue max-retries=integer
permission-id=allowedValue transcript-id=integer attempts=integer>
<name>string</name>
<url>string</url>
<date-created>datetime</date-created>
<date-modified>datetime</date-modified>
<date-begin>datetime</date-begin>
<url-path>string</url-path>
<expired>boolean</expired>
<completed>boolean</completed>
</row>
...
</report-my-training>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-my-training Container The entire list of courses and curriculums the user is enrolled
in.
type Allowed value The type of the object (see type for allowed values).
icon Allowed value The icon that identifies the object in Connect Central (see
icon for allowed values). If type is content, the icon value
describes the content.
max-retries Integer The allowed number of attempts that the course can be
retaken.
permission-id Allowed value The permission the principal has on the object (see
permission-id for allowed values).
attempts Integer The number of times the user has tried to complete the
course.
url String The part of the URL to the course or curriculum that includes
the domain name and unique name, without http:// or
https://.
date-created Datetime The date and time the course or curriculum was created.
date-modified Datetime The date and time the course or curriculum was last
modified.
date-begin Datetime The start date and time of the course or curriculum, either
past or future.
date-end Datetime The end date or time of the course or curriculum, either past
or future.
url-path String The unique name of the course or curriculum in its URL.
expired Boolean A value indicating whether the end date of the course or
curriculum has passed (true if it has, false if not).
completed Boolean A value indicating whether the user or group has completed
the course.
tr-status String Whether the user has attempted to take the course
(attempted)or not (not-attempted).
Sample request
https://example.com/api/xml?action=report-my-training
&principal-id=2006258745
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-my-training>
<row sco-id="2006298431" type="content" icon="course" max-retries=""
permission-id="view" transcript-id="" attempts="0">
<name>Intro to Psychology</name>
<url>example.com/psychology/</url>
<date-created>2006-05-03T10:21:46.810-07:00</date-created>
<date-modified>2006-05-03T10:22:30.803-07:00</date-modified>
<date-begin>2006-05-03T10:15:00.000-07:00</date-begin>
<url-path>/psychology/</url-path>
<expired>false</expired>
<completed>true</completed>
</row>
<row sco-id="2006745669" type="curriculum" icon="curriculum"
permission-id="view">
<name>A Day in the Life</name>
<url>example.com/day/</url>
<date-created>2006-06-12T14:47:59.903-07:00</date-created>
<date-modified>2006-06-12T14:47:59.903-07:00</date-modified>
<date-begin>2006-06-12T14:45:00.000-07:00</date-begin>
<url-path>/day/</url-path>
<expired>false</expired>
<completed>false</completed>
<tr-status>not-attempted</tr-status>
</row>
</report-my-training>
</results>
report-quiz-interactions
Availability
Breeze 4
Description
Provides information about all the interactions users have had with a certain quiz. An interaction identifies all answers
one user makes to one quiz question. If a user answers the same question more than once, all answers are part of the
same interaction and have the same interaction-id.
This report provides information about every answer that any user has ever given to questions on a quiz. You can filter
the response to make it more meaningful, using any allowed filters. For example, you can request all answers a certain
user has given:
https://example.com/api/xml?action=report-quiz-interactions
&sco-id=2006334909&filter-like-name=Joy%20Smith
Or, you can request only a certain user’s answers to a specific question:
https://example.com/api/xml?action=report-quiz-interactions
&sco-id=2006334909&filter-name=Joy%20Smith
&filter-like-description=What is the capital of California
Request URL
http://server_name/api/xml
?action=report-quiz-interactions
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<results>
<status code=allowedValue />
<report-quiz-interactions>
<row display-seq=integer transcript-id=integer interaction-id=integer
sco-id=integer score=integer>
<name>string</name>
<sco-name>string</sco-name>
<date-created>datetime</date-created>
<description>string</description>
<response>integer</response>
</row>
...
</report-quiz-interactions>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-quiz-interactions Container Information about all interactions all users have had with
the quiz.
row Container Information about one user, one quiz question, and one
answer. Multiple row elements can be part of the same
interaction.
transcript-id Integer The ID of one user’s attempt to take a quiz, with one user,
one attempt at a quiz, and multiple questions and answers.
Each time the user takes the quiz, the transcript-id
changes.
interaction-id Integer The ID of all answers one user makes to one quiz question.
sco-name Integer The name of the presentation or course that contains the
quiz.
Sample request
https://example.com/api/xml?action=report-quiz-interactions
&sco-id=2006334909&filter-name=Joy Smith
&filter-like-description=governor
Sample request
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-quiz-interactions>
<row display-seq="2" transcript-id="2006335803"
interaction-id="2006334914" sco-id="2006334909" score="10">
<name>Joy Smith</name>
<sco-name>California Quiz</sco-name>
<date-created>2006-05-11T15:50:23.643-07:00</date-created>
<description>
The governor of California is a former actor.
</description>
<response>true</response>
</row>
<row display-seq="2" transcript-id="2006335827"
interaction-id="2006334914" sco-id="2006334909" score="0">
<name>Joy Smith</name>
<sco-name>California Quiz</sco-name>
<date-created>2006-05-11T17:32:53.970-07:00</date-created>
<description>
The governor of California is a former actor.
</description>
<response>false</response>
</row>
<row display-seq="2" transcript-id="2006335954"
interaction-id="2006334914" sco-id="2006334909" score="10">
<name>Joy Smith</name>
<sco-name>California Quiz/sco-name>
<date-created>2006-05-12T11:55:24.940-07:00</date-created>
<description>
The governor of California is a former actor.
</description>
<response>true</response>
</row>
</report-quiz-interactions>
</results>
report-quiz-question-answer-distribution
Availability
Breeze 4
Description
Returns information about the number of users who chose a specific answer to a quiz question. The combination of
one quiz question and all of one user’s answers to it is called an interaction. If the user answers the question more than
once, all answers are part of the same interaction and have the same interaction-id.
Call report-quiz-interactions to determine an interaction-id to specify in the request. The interaction-id
does not correspond to the question number in the quiz (for example, question 1, question 2, and so on).
Request URL
http://server_name/api/xml
?action=report-quiz-question-answer-distribution
&interaction-id=integer
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
interaction-id Integer N The ID that describes all of one user’s responses to one quiz question.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-quiz-question-answer-distribution>
<row display-seq=integer interaction-id=integer score=integer
asset-id=integer num-selected=integer>
<response>string</response>
</row>
...
</report-quiz-question-answer-distribution>
</results>
Response values
Sample request
https://example.com/api/xml
?action=report-quiz-question-answer-distribution&sco-id=2006334909
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-quiz-question-answer-distribution>
<row display-seq="1" interaction-id="2006334913" score="0"
asset-id="2006334911" num-selected="1">
<response>san francisco</response>
</row>
<row display-seq="1" interaction-id="2006334913" score="10"
asset-id="2006334911" num-selected="2">
<response>Sacramento</response>
</row>
<row display-seq="2" interaction-id="2006334914" score="0"
asset-id="2006334911" num-selected="1">
<response>false</response>
</row>
...
</report-quiz-question-answer-distribution>
</results>
report-quiz-question-distribution
Availability
Breeze 4
Description
Returns information about the number of correct and incorrect answers to the questions on a quiz. This call can help
you determine how a group responded to a quiz question overall.
Because this call returns information about all the questions on a quiz, you may want to filter the results for a specific
question or group of questions.
Request URL
http://server_name/api/xml
?action=report-quiz-question-distribution
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-quiz-question-distribution>
<row display-seq=integer interaction-id=integer num-correct=integer
num-incorrect=integer total-responses=integer
percentage-correct=integer score=integer>
<name>string</name>
<description>string</description>
</row>
...
</report-quiz-question-distribution>
</results>
Response values
Sample request
https://example.com/api/xml?action=report-quiz-question-distribution
&sco-id=2006334909&filter-like-description=The capital of California
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-quiz-question-distribution>
<row display-seq="1" interaction-id="2006334913" num-correct="2"
num-incorrect="1" total-responses="3" percentage-correct="66"
score="10">
<name>The capital of California is<1></name>
<description>The capital of California is<1></description>
</row>
</report-quiz-question-distribution>
</results>
report-quiz-question-response
Availability
Breeze 4
Description
Provides a list of answers that users have given to questions on a quiz.
Without filtering, this action returns all answers from any user to any question on the quiz. However, you can filter
the response for a specific user, interaction, or answer (see the filter syntax at filter-definition).
An interaction is a combination of one user and one question. If the user answers the same question more than once,
all answers are part of the same interaction and have the same interaction-id.
Request URL
http://server_name/api/xml
?action=report-quiz-question-response
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-quiz-question-response>
<row principal-id=integer interaction-id=string>
<user-name>string</user-name>
<response>string</response>
<date-created>datetime</date-created>
</row>
</report-quiz-question-response>
</results>
Response values
Sample request
https://example.com/api/xml?action=report-quiz-question-response
&sco-id=2006334909&filter-interaction-id=2006334913
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-quiz-question-response>
<row principal-id="2006258745" interaction-id="2006334913">
<user-name>Joy Smith</user-name>
<response>Sacramento</response>
<date-created>2006-05-11T15:50:23.643-07:00</date-created>
</row>
<row principal-id="2006258745" interaction-id="2006334913">
<user-name>Joy Smith</user-name>
<response>san francisco</response>
<date-created>2006-05-11T17:32:53.970-07:00</date-created>
</row>
<row principal-id="2006258745" interaction-id="2006334913">
<response>Sacramento</response>
<date-created>2006-05-12T11:55:24.940-07:00</date-created>
</row>
</report-quiz-question-response>
</results>
report-quiz-summary
Availability
Breeze 4
Description
Provides a summary of data about a quiz, including the number of times the quiz has been taken; average, high, and
low scores; and other information.
Request URL
http://server_name/api/xml
?action=report-quiz-summary
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-quiz-summary>
<row num-questions=integer average-score=integer low-score=integer
high-score=integer numtaken=integer numdistincttaken=integer
maxpossiblescore=integer asset-id=integer />
</report-quiz-summary>
</results>
Response values
code Allowed value A code indicating the response status (see status).
row Empty, with Summary information about the quiz. Can return more than one
attributes row element if the maxpossiblescore is different for different
transcripts.
average-score Integer The average score, across all users who have taken the quiz.
low-score Integer The lowest score a user has received on the quiz.
high-score Integer The highest score a user has received on the quiz.
numtaken Integer The total number of times the quiz has been taken.
numdistincttaken Integer The number of times the quiz has been taken by distinct
principals. If a principal takes the quiz more than once, only one
time is counted.
asset-id Integer The ID of the latest version of the SCO uploaded to the server.
Sample request
https://server.com/api/xml?action=report-quiz-summary&sco-id=2006123456
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-quiz-summary>
<row num-questions="2" average-score="0" low-score="0" high-score="0"
numtaken="1" numdistincttaken="1" maxpossiblescore="0"
asset-id="2006334911" />
<row num-questions="2" average-score="13" low-score="0" high-score="20"
numtaken="3" numdistincttaken="3" maxpossiblescore="20"
asset-id="2006334911" />
</report-quiz-summary>
</results>
report-quiz-takers
Availability
Breeze 4
Description
Provides information about all users who have taken a quiz in a training. Use a sco-id to identify the quiz.
To reduce the volume of the response, use any allowed filter or pass a type parameter to return information about just
one type of SCO (courses, presentations, or meetings).
Request URL
http://server_name/api/xml
?action=report-quiz-takers
&sco-id=integer
&principal-id=integer
&type=allowedValue
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
principal-id Integer N The ID of a principal for whom you want quiz results.
type Allowed value N The type of content for which you want results. Allowed values are
course, presentation, and meeting.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-quiz-takers>
<row transcript-id=integer sco-id=integer principal-id=integer
status=allowedValue score=integer asset-id=integer
permission-id=allowedValue attempts=integer time-taken=integer
certificate=integer answered-survey=boolean version=integer>
<name>string</name>
<login>string</login>
<date-created>datetime</date-created>
<principal-name>string</principal-name>
<override>boolean</override>
</row>
</report-quiz-takers>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-quiz-takers Container Information about all users who have taken the quiz.
row Container Information about one user who has taken the quiz.
transcript-id Integer The ID of the transcript on which the user’s quiz score is recorded.
sco-id Integer The unique ID of the presentation, course, or meeting that has the
quiz.
status Allowed value Whether the user passed or failed the most recent attempt at the quiz.
Allowed values are user-passed and user-failed.
score Integer The user’s score on the most recent attempt at the quiz.
asset-id Integer The ID of the version of the quiz the user attempted.
permission-id Allowed value The level of permission the user has to access the quiz (see
permission-id for values).
attempts Integer The number of times the user has taken the quiz.
time-taken Integer The amount of time the user spent taking the quiz, in milliseconds.
answered- Boolean Whether the learner completed a quiz. If 0 or false, the training does
survey not have a quiz or the learner did not complete it. If 1 or true, the
learner completed the quiz.
date-created Datetime The date and time of the user’s most recent quiz attempt.
principal-name String The full name of the user taking the quiz.
override Boolean A setting indicating whether a training manager can change the
user’s score on the quiz.
Sample request
https://example.com/api/xml?action=report-quiz-takers&sco-id=2006334909
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-quiz-takers>
<row transcript-id="2006337854" sco-id="2006334909"
principal-id="2006258745" status="incomplete" score="0"
max-score="20" asset-id="2006334911" permission-id=""
attempts="4" time-taken="12593" certificate="" answered-survey="1"
version="1">
<name>California State Quiz</name>
<login>[email protected]</login>
<date-created>2006-05-16T11:14:47.000-07:00</date-created>
<principal-name>Joy Smith</principal-name>
<override>false</override>
</row>
</report-quiz-takers>
</results>
report-quotas
Availability
Breeze 4
Description
Returns information about the quotas that apply to your Adobe Connect license or Adobe Connect hosted account.
Adobe Connect enforces various quotas, for example, the number of concurrent users in training, the number of
downloads, the number of authors, and so on.
Although your server license determines certain quotas, you can scale your license beyond your limit. In the response
from report-quotas, the soft-limit is the number defined by your license. The soft-limit is the same as the
limit, unless you purchase a Burst Pack for meetings, which allows additional participants to join past the limit, on
an overage basis.
Request URL
http://server_name/api/xml
?action=report-quotas
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-quotas>
<quota acl-id=integer quota-id=string used=integer
limit=allowedValue soft-limit=integer>
<date-begin>datetime</date-begin>
<date-end>datetime</date-end>
</quota>
</report-quotas>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-quotas Container Information about all of the quotas set for the account.
quota-id Allowed value The name of the quota defined by the server, ending in -quota.
used Integer The number of uses that count toward this quota.
limit Integer The limit at which the server does not allow access. Has the same
value as soft-limit, unless you have purchased a Burst Pack to allow
for overage. The value is either an integer or unlimited.
date-begin Datetime The date and time the quota was effective on the server.
Sample request
https://example.com/api/xml?action=report-quotas
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-quotas>
<quota acl-id="624520" quota-id="download-quota"
used="1" limit="unlimited" soft-limit="1000000000">
<date-begin>2004-03-09T09:45:41.047-08:00</date-begin>
<date-end>3000-01-01T00:00:00.000-08:00</date-end>
</quota>
<quota acl-id="624520" quota-id="bandwidth-quota" used="12802"
limit="unlimited" soft-limit="1000000000">
<date-begin>2006-05-31T17:00:00.943-07:00</date-begin>
<date-end>2006-06-30T17:00:00.943-07:00</date-end>
</quota>
...
</report-quotas>
</results>
report-sco-slides
Availability
Breeze 4
Description
Returns information about the slides in a presentation. The information includes how many times, and how recently,
each slide has been viewed.
Request URL
http://server_name/api/xml
?action=report-sco-slides
&sco-id=integer
&asset-id=integer
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-sco-slides>
<row slide=integer name=integer asset-id=integer views=integer>
<date-created>datetime</date-created>
</row>
...
</report-sco-slides>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-sco-slides Container Information about all of the slides in a presentation, indicating how many
times and how recently a slide has been viewed.
asset-id Integer The version number of the presentation. Each time a presentation is
published, it has a new asset-id.
views Integer The number of times the slide has been viewed.
date-created Datetime The date and time the slide was last viewed.
Sample request
https://example.com/api/xml?action=report-sco-slides&sco-id=2006334909
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-sco-slides>
<row slide="1" name="1" views="4">
<date-created>2006-05-16T11:14:54.453-07:00</date-created>
</row>
<row slide="2" name="2" views="4">
<date-created>2006-05-16T11:14:59.593-07:00</date-created>
</row>
<row slide="3" name="3" views="3">
<date-created>2006-05-12T11:55:52.330-07:00</date-created>
</row>
<row slide="4" name="4" views="3">
<date-created>2006-05-12T11:55:55.487-07:00</date-created>
</row>
<row slide="5" name="5" views="3">
<date-created>2006-05-12T11:56:00.233-07:00</date-created>
</row>
</report-sco-slides>
</results>
See also
report-sco-views
report-sco-views
Availability
Breeze 4
Description
Indicates how many times, and how recently, a SCO was viewed.
Request URL
http://server_name/api/xml
?action=report-sco-views
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-sco-views sco-id=integer type=allowedValue is-folder=boolean
views=integer>
<name>string</name>
<last-viewed-date>string</last-viewed-date>
</report-sco-views>
</results>
Response values
code Allowed value A code indicating the response status (see status).
report-sco-views Container Information about how many times, and how recently, the
presentation was viewed.
type Allowed value The type of content object (SCO). Allowed values are content,
curriculum, event, folder, link, meeting, and tree.
is-folder Boolean A value indicating whether the SCO is a folder (if 1) or another type
of object (if 0).
views Integer The number of times users have viewed the SCO.
last-viewed-date Datetime The date and time the SCO was last viewed.
Sample request
https://server.com/api/xml?action=report-sco-views&sco-id=2006334909
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-sco-views sco-id="2006334909" type="content" is-folder="0"
views="3">
<name>Quiz on California</name>
<last-viewed-date>2006-05-12T11:55:24.940-07:00</last-viewed-date>
</report-sco-views>
</results>
report-user-trainings-taken
Availability
Connect Enterprise 6
Description
Returns a list of all courses and curriculums a user has taken, whether or not the user has completed the training. Each
course or curriculum is returned in a separate row element and has the most recent transcript of the user’s scores.
Request URL
http://server_name/api/xml
?action=report-user-trainings-taken
&principal-id=integer
&session=BreezeSessionCookieValue
Parameters
principal-id Integer Y The ID of a user for whom you want a list of trainings.
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-user-trainings-taken>
<row transcript-id=integer max-retries=integer sco-id=integer
type=allowedValue icon=allowedValue status=allowedValue
certificate=integer score=integer permission-id=allowedValue
attempts=allowedValue>
<name>string</name>
<description>string</description>
<url-path>string</url-path>
<date-taken>datetime</date-taken>
<from-curriculum>boolean</from-curriculum>
</row>
...
</report-user-trainings-taken>
</results>
Response values
code Allowed value A code indicating the response status (see status).
type Allowed value The type of the SCO. Allowed values are user-
content, content, and my-content.
transcript-id Integer The ID of the record of the user’s most recent score on
this training.
max-retries Integer The maximum number of times the user can repeat the
training.
type Allowed value The type of the training SCO (see allowed values at
type).
icon Allowed value The type of icon that identifies the course or
curriculum in Connect Central. Provides information
about the course or curriculum in addition to its type
(see allowed values at icon).
status Allowed value The status of the user’s work with the SCO. Allowed
values for a course or presentation are user-passed,
user-failed, completed, incomplete, not-
attempted, and review. A curriculum or folder can
only be completed or incomplete.
certificate Integer The ID of the record that shows the user passed or
completed the training.
score Integer The score the user earned on the most recent attempt
at the training.
permission-id Allowed value The permission the user has been assigned to access
the course or curriculum (see permission-id for
allowed values).
attempts Integer The number of attempts the user has made at this
training.
url-path String The unique identifier of the SCO that appears in its URL
after the domain name.
date-taken Datetime The date the user interacted with the training SCO
(viewed a presentation, took a quiz, and so on).
Sample request
https://example.com/api/xml?action=report-user-trainings-taken
&principal-id=2006258745&principal-id=4797406
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-user-trainings-taken>
<row transcript-id="2006745722" max-retries="" sco-id="2006745673"
type="content" icon="course" status="user-passed"
certificate="2006745722" score="0" permission-id=""
attempts="1">
<name>All About Web Communities</name>
<description>test</description>
<url-path>/p33096345/</url-path>
<date-taken>2006-06-12T15:06:02.947-07:00</date-taken>
<from-curriculum>false</from-curriculum>
</row>
...
</report-user-trainings-taken>
</results>
report-user-training-transcripts
Availability
Connect Enterprise 6
Description
Returns a list of transcripts for trainings a user has taken. A transcript is the record of one score a user obtained from
one attempt at taking one training. A training can be a course, curriculum, meeting, or event.
The response can include more than one transcript for a training SCO, if the user has attempted the training more than
once. A user can fail a training the first time and then pass on the second attempt. Each attempt has its own transcript,
and both transcripts are included in the report.
Request URL
http://server_name/api/xml
?action=report-user-training-transcripts
&principal-id=integer
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
You can filter or sort the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<report-user-training-transcripts>
<row transcript-id=integer sco-id=integer
principal-id=integer status=allowedValue score=integer
max-score=integer certificate=integer type=allowedValue
icon=allowedValue>
<name>string</name>
<url-path>string</url-path>
<login>string</login>
<date-taken>datetime</date-taken>
<principal-name>string</principal-name>
<sco-tag>string</sco-tag>
</row>
...
</report-user-training-transcripts>
Response values
status Allowed value The status of the user’s work with the SCO (see
status attribute for allowed values).
score Integer The score the user earned on the SCO. If the SCO
does not have a score, as with a meeting, the
value of score is 0.
type Allowed value The type of the SCO. Allowed values are user-
content, content, and my-content.
icon Allowed value The name of the icon that identifies the course or
curriculum in Adobe Connect Central.
date-taken Datetime The date the user interacted with the course or
curriculum (viewed a presentation, took a quiz,
and so on).
principal-name String The name of the user interacting with the SCO.
Sample request
https://example.com/api/xml?action=report-user-training-transcripts
&principal-id=2006258745
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-user-training-transcripts>
<row transcript-id="2006905612" sco-id="2006298431"
principal-id="2006258745" status="review" score="0" max-score=""
certificate="" type="content" icon="course">
<name>Test Course</name>
<url-path>/test/</url-path>
<login>[email protected]</login>
<date-taken>2006-06-30T15:23:55.070-07:00</date-taken>
<principal-name>Joy Smith</principal-name>
</row>
<row transcript-id="2007016805" sco-id="2006298431"
principal-id="2006258745" status="review" score="0" max-score=""
certificate="" type="content" icon="course">
<name>Test Course</name>
<url-path>/test/</url-path>
<login>[email protected]</login>
<date-taken>2006-07-14T16:55:28.440-07:00</date-taken>
<principal-name>Joy Smith</principal-name>
</row>
</report-user-training-transcripts>
</results>
sco-by-url
Availability
Adobe Connect Pro 7
Description
Returns information about a SCO at a specified URL path. The URL path is the unique identifier after the domain
name in the URL to the SCO. For example, if you have a meeting with the custom URL
http://example.com/teammeeting, the URL path is /teammeeting. If you pass the full URL path, Connect returns
the status code "no data".
Request URL
http://server_name/api/xml
?action=sco-by-url
&url-path=url
Parameters
url-path Y The unique identifier after the domain name in the URL to the SCO.
Filters
You cannot filter or sort the response.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<owner-principal type="allowedValue" principal-id="number" account-id="number" has-
children="Boolean" is-hidden="Boolean" is-primary="Boolean">
<ext-login></ext-login>
<login></login>
<name></name>
<email></email>
</owner-principal>
- <sco sco-id="number" account-id="number" display-seq="number" folder-id="number"
icon="string" lang="string" max-retries="number" source-sco-id="number" type="allowedValue"
version="number">
<url-path></url-path>
<date-begin></date-begin>
<date-created></date-created>
<date-modified></date-modified>
<name></name>
</sco>
</results>
Response values
code Allowed value A code indicating the response status (see status).
type Allowed value The type of principal (see type for values).
has-children Boolean Whether the principal has children. Groups have children and users
don’t, so this attribute indicates whether the principal is a group.
is-hidden Boolean Whether the principal is hidden (true) or not (false) in Connect
Central or your application.
is-primary Boolean Whether the principal is a built-in group (true) or not (false).
ext-login String The login ID sent from an external network. By default, the same value
as login.
login String The login name of the user who is logged in to the server, often the
user’s e-mail address.
name String The name of the user who is logged in to the server.
e-mail String The e-mail address of the user who is logged in to the server.
display-seq Integer The sequence in which Adobe Connect Central or your application
displays the field.
icon Allowed value The name of the icon that visually identifies this object.
lang String The language in which information about the SCO is displayed (see
lang for values).
max-retries Integer The maximum number of times a user can retake the course or
curriculum. If a user can take the course 3 times, max-retries is 2.
type Allowed value The type of the object (see type for values).
url-path String The unique identifier after the domain name in the URL to the SCO.
date-begin Datetime The beginning date of a course or meeting (returned for a course or
meeting only).
date-created Datetime The date a course or meeting was created (returned for a course or
meeting only).
Sample request
http://example.com/api/xml?action=sco-by-url&url-path=/p18656190/
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<owner-principal type="content" principal-id="824622254" account-id="824592506" has-
children="false" is-hidden="false" is-primary="false">
<ext-login>[email protected]</ext-login>
<login>[email protected]</login>
<name>Jane Doe</name>
<email>[email protected]</email>
</owner-principal>
- <sco sco-id="825344405" account-id="824592506" display-seq="0" folder-id="824622258"
icon="curriculum" lang="en" max-retries="" source-sco-id="" type="curriculum" version="0">
<url-path>/p18656190/</url-path>
<date-begin>2009-09-15T13:30:00.000-07:00</date-begin>
<date-created>2009-09-15T13:32:45.683-07:00</date-created>
<date-modified>2009-09-15T13:32:45.683-07:00</date-modified>
<name>Test Curriculum</name>
</sco>
</results>
sco-contents
Availability
Breeze 4
Description
Returns a list of SCOs within another SCO. The enclosing SCO can be a folder, meeting, or curriculum.
In general, the contained SCOs can be of any type—meetings, courses, curriculums, content, events, folders, trees, or
links (see the list in type). However, the type of the contained SCO needs to be valid for the enclosing SCO. For
example, courses are contained within curriculums, and meeting content is contained within meetings.
Because folders are SCOs, the returned list includes SCOs and subfolders at the next hierarchical level, but not the
contents of the subfolders. To include the subfolder contents, call sco-expanded-contents.
Request URL
http://server_name/api/xml
?action=sco-contents
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=value
Parameters
sco-id Integer Y The unique ID of a folder for which you want to list contents. You can
get the sco-id by calling sco-shortcuts.
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
You can filter the response on any element or attribute, with these exceptions:
• You cannot filter on duration.
• If you use filter-date-begin, filter-date-end, or filter-date-modified, specify a time without a time
zone, for example:
filter-date-modified=2005-01-05T10:44:03
You can use filter-gt or filter-lt with a date field and a full date, including the time zone.
You can sort the response on any element or attribute.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<scos>
<sco sco-id=integer source-sco-id=integer folder-id=integer
type=allowedValue icon=allowedValue display-seq=integer
is-folder=boolean byte-count=integer ref-count=integer>
<name>string</name>
<url-path>string</url-path>
<description>string</description>
<date-begin>string</date-begin>
<date-modified>datetime</date-modified>
<date-end>string</date-end>
<sco-tag>string</sco-tag>
</sco>
</scos>
</results>
Response values
code Allowed value A code indicating the response status (see status).
type Allowed value The type of the object (see type for values). SCOs that represent
content have a type of content, rather than a more specific type, such
as presentation.
icon Allowed value The name of the icon that identifies the object. Provides more detail on
the type of object in type.
display-seq Integer The sequence in which Connect Central or your application displays
the object.
is-folder Boolean Integer A value indicating whether the object is a folder (1) or not (0).
byte-count Integer The size of the content. For folders, this value will be 0.
url-path String The unique identifier after the domain name in the URL to the SCO.
date-begin Datetime The beginning date of a course or meeting (returned for a course or
meeting only).
date-end Datetime The end date of a course or meeting (returned for a course or meeting
only).
domain-name String The domain name at which you can access a meeting or event
(returned for meetings and events only).
duration Datetime The length of time a course or meeting lasted (returned for a course or
meeting only).
Sample request
https://example.com/api/xml?action=sco-contents&sco-id=2006258748
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<scos>
<sco sco-id="2007035246" source-sco-id="2006334909"
folder-id="2006258748" type="content" icon="course"
display-seq="0" is-folder="0">
<name>Java 101</name>
<url-path>/java101/</url-path>
<date-begin>2006-07-20T17:15:00.000-07:00</date-begin>
<date-modified>2006-07-20T17:21:38.860-07:00</date-modified>
</sco>
</scos>
</results>
See also
sco-expanded-contents, sco-shortcuts
sco-delete
Availability
Breeze 4
Description
Deletes one or more objects (SCOs).
If the sco-id you specify is for a folder, all the contents of the specified folder are deleted. To delete multiple SCOs,
specify multiple sco-id parameters.
You can use a call such as sco-contents to check the ref-count of the SCO, which is the number of other SCOs that
reference this SCO. If the SCO has no references, you can safely remove it, and the server reclaims the space.
If the SCO has references, removing it can cause the SCOs that reference it to stop working, or the server not to reclaim
the space, or both. For example, if a course references a quiz presentation, removing the presentation might make the
course stop working.
As another example, if a meeting has used a content SCO (such as a presentation or video), there is a reference from
the meeting to the SCO. Deleting the content SCO does not free disk space, because the meeting still references it.
To delete a SCO, you need at least manage permission (see permission-id for details). Users who belong to the built-
in authors group have manage permission on their own content folder, so they can delete content within it.
Request URL
http://server_name/api/xml
?action=sco-delete
&sco-id=integer
&session=value
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if
you do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=sco-delete&sco-id=2007171127
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
sco-info, sco-move, sco-nav, sco-expanded-contents
sco-expanded-contents
Availability
Breeze 5
To list the contents of a curriculum in Connect Pro 7 and later, use curriculum-contents.
Description
Lists all of the SCOs in a folder, including the contents of subfolders, curriculums, and any type of enclosing SCO.
Note: If you call this command on a large folder—such as the root meeting folder for a large account—the amount of data
returned is very large.
If you do not use a filter, the list of SCOs is returned in the same order as it appears in Connect Central. If you use a
filter or a sort, the list is returned according to the filter or sort you use.
Request URL
http://server_name/api/xml
?action=sco-expanded-contents
&sco-id=integer
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter
if you do not use a client-side cookie management library.
Filters
You can filter the response on any element or attribute, with these exceptions:
• You cannot filter on duration.
• If you use filter-date-begin, filter-date-end, or filter-date-modified, specify a date in ISO 8601 format
but without a time zone, for example:
filter-date-modified=2005-01-05T10:44:03
However, you can use filter-gt-datefield or filter-lt-datefield with a full date that includes a time zone.
• Do not use partial match filters constructed with filter-like (such as filter-like-name), as they might affect
server performance.
You can sort the response on any element or attribute except date-begin, date-created, date-modified, and url-path.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<expanded-scos>
<sco depth=integer sco-id=integer folder-id=integer type=allowedValue
icon=allowedValue lang=allowedValue source-sco-id=integer
display-seq=integer source-sco-type=integer>
<name>string</name>
<url-path>string</url-path>
<date-created>datetime</date-created>
<date-modified>datetime</date-modified>
</sco>
... more sco elements ...
</expanded-scos>
</results>
Response values
code Allowed value A code indicating the response status (see status).
sco Container Details about one SCO in the folder. This SCO can be a folder or any
other type of object.
depth Integer The depth in the content tree at which this object appears, with top-
level objects at 1.
sco-id Integer The unique ID of the SCO. If the SCO is a folder, same as folder-id.
type Allowed value The type of this content object (see type).
icon Allowed value The name of the icon that visually identifies this object.
lang Allowed value The language in which information about the SCO is displayed (see
lang for values).
source-sco-id Integer The ID of a SCO from which this SCO was created, such as a meeting
template or course content.
display-seq Integer The sequence in which Connect Central (or your application, if you use
this value) displays a list of SCOs. Values are not necessarily unique, so
multiple SCOs can have the same display-seq value. In that case, the
application must define the display sequence. The default is 0.
source-sco- Integer An integer indicating the type of the SCO from which this SCO was
type created.
Sample request
https://example.com/api/xml?action=sco-expanded-contents&sco-id=624529
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<expanded-scos>
<sco depth="0" sco-id="624529" folder-id="624520" type="folder"
icon="folder" lang="en" source-sco-id="" display-seq="0"
source-sco-type="">
<name>Shared Meetings</name>
<url-path>/f624529/</url-path>
<date-created>2004-03-09T09:45:41.060-08:00</date-created>
<date-modified>2005-03-18T10:19:38.950-08:00</date-modified>
</sco>
<sco depth="1" sco-id="2598379" folder-id="624529" type="meeting"
icon="meeting" lang="en" source-sco-id="-8888" display-seq="0"
source-sco-type="3">
<name>Monday Night Football</name>
<url-path>/r68075204/</url-path>
<description>Monday Night Football</description>
<date-begin>2004-05-17T15:30:00.000-07:00</date-begin>
<date-end>2004-05-18T00:15:00.000-07:00</date-end>
<date-created>2004-05-17T15:50:39.733-07:00</date-created>
<date-modified>2006-08-16T00:34:52.930-07:00</date-modified>
</sco>
</expanded-scos>
</results>
sco-info
Availability
Breeze 4
Description
Provides information about a SCO on Adobe Connect. The object can have any valid SCO type. See type for a list of
the allowed SCO types.
The response includes the account the SCO belongs to, the dates it was created and last modified, the owner, the URL
that reaches it, and other data. For some types of SCOs, the response also includes information about a template from
which this SCO was created.
Request URL
http://server_name/api/xml
?action=sco-info
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you
do not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<sco account-id=integer disabled=datetime display-seq=integer
folder-id=integer icon=allowedValue lang=allowedValue
max-retries=integer sco-id=integer source-sco-id=integer
type=allowedValue version=integer>
<date-begin>datetime</date-begin>
<date-created>datetime</date-created>
<date-end>datetime</date-end>
<date-modified>datetime</date-modified>
<description>string</description>
<name>string</name>
<url-path>string</url-path>
<passing-score>integer</passing-score>
<duration>datetime</duration>
<section-count>integer</section-count>
</sco>
<source-sco>
<source-sco account-id=integer display-seq=integer folder-id=integer
icon=allowedValue lang=allowedValue max-retries=integer
sco-id=integer source-sco-id=integer type=allowedValue
version=integer>
<date-created>datetime</date-created>
<date-modified>datetime</date-modified>
<name>string</name>
<url-path>string</url-path>
</source-sco>
</source-sco>
</results>
Response values
code Allowed value A code indicating the response status (see status).
disabled Datetime An empty value if the SCO has not been disabled. If it has, the
date and time it was disabled.
display-seq Integer The sequence in which Connect Central (or your application,
if you use this value) displays a list of SCOs. Values are not
necessarily unique, so multiple SCOs can have the same
display-seq value. In that case, the application must
define the display sequence. The default is 0.
icon Allowed value The type of icon used as a visual identifier for the SCO (see
icon).
lang Allowed value An abbreviation for the new language (see type for values).
max-retries Integer The number of times the user is allowed to attempt to take
the SCO.
source-sco-id Integer The unique ID of a template from which the SCO is derived.
type Allowed value The content type of the SCO (see type for values). type is a
high-level category. icon provides more detail on the type
of content.
version Integer The version number of the SCO, incremented when the
object is modified or uploaded to the server.
date-begin Datetime If the SCO is a meeting, the date and time the meeting starts.
date-created Datetime The date and time the SCO was created (or, for content,
uploaded).
date-end Datetime If the SCO is a meeting, the date and time the meeting ends.
date-modified Datetime The date and time the SCO was last modified.
description String The description of the SCO entered when the SCO was
created.
passing-score Integer The minimum score that a user must have to pass a training
course.
duration Integer The length of time needed to view or play the SCO, in
milliseconds.
section-count Integer The number of sections in the course content, including the
number of slides, pages, chapters, interactions, or other
content divisions.
source-sco Container Information about any SCOs that are templates for, or
provide content to, the SCO you are interested in. The SCOs
that can have a source are meetings, courses, or events.
source-sco Container Details about one SCO that is a template for, or provides
source content to, the SCO you are interested in. Has
additional elements and attributes, the same as the sco
element.
Sample request
https://example.com/api/xml?action=sco-info&sco-id=2006320683
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<sco account-id="624520" disabled="" display-seq="0"
folder-id="2006258750" icon="meeting" lang="en" max-retries=""
sco-id="2006320683" source-sco-id="-1625529" type="meeting"
version="0">
<date-begin>2006-05-04T11:15:00.000-07:00</date-begin>
<date-created>2006-05-04T11:27:47.087-07:00</date-created>
<date-end>2006-05-04T12:15:00.000-07:00</date-end>
<date-modified>2006-05-04T11:27:47.087-07:00</date-modified>
<name>Technology and Law Review Meeting</name>
<url-path>/tlawreview/</url-path>
</sco>
<source-sco>
<source-sco account-id="624520" display-seq="0" folder-id="-625529"
icon="meeting" lang="en" max-retries="" sco-id="-1625529"
source-sco-id="-8888" type="meeting" version="0">
<date-created>2004-10-05T00:49:30.217-07:00</date-created>
<date-modified>2005-01-04T15:03:25.937-08:00</date-modified>
<name>Default Meeting Template</name>
<url-path>/defaultMeetingTemplate/</url-path>
</source-sco>
</source-sco>
</results>
sco-move
Availability
Breeze 4
Description
Moves a SCO from one folder to another.
To move a SCO to a folder, the current user must have permission to create content in the target folder. In general,
users have permission on their own folders (such as my-meetings, my-courses, my-events, my-content, and my-
meeting-templates) by default. To move SCOs to a shared folder such as content, courses, and meetings, a user
must have Manage permission or be an Administrator.
Request URL
http://server_name/api/xml
?action=sco-move
&folder-id=integer
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=sco-move&sco-id=2006744233
&folder-id=2006258748
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
sco-nav
sco-nav
Availability
Breeze 4
Description
Describes the folder hierarchy that contains a SCO.
The sco-nav call is useful for creating a navigation tree, breadcrumb trail, or any other type of user interface hierarchy.
The response contains a list of sco elements, one for the SCO you are querying and one for each of its enclosing folders
up to the top-level folder. The top-level folder is one of the list of folders returned by sco-shortcuts.
In each sco element, the depth attribute indicates how many hierarchical levels the SCO is from the SCO you specify
in the request. A depth of 0 indicates the SCO you are querying, a depth of 1 indicates the folder that contains the
SCO, and so on.
Request URL
http://server_name/api/xml
?action=sco-nav
&sco-id=integer
&session=BreezeSessionCookieValue
Parameters
sco-id Integer Y The unique ID of a SCO for which you want a folder hierarchy up to the
root level.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<sco-nav>
<sco sco-id=integer type=allowedValue icon=allowedValue depth=integer>
<name>string</name>
</sco>
...
</sco-nav>
</results>
Response values
code Allowed value A code indicating the response status (see status).
sco-nav Container The entire navigation tree from the top-level folder to the SCO.
type Allowed value The type of SCO (see type for values).
icon Allowed value The icon that visually represents the SCO (see icon for values).
depth Integer A number representing the level of a SCO in the folder hierarchy relative
to the SCO passed in the request (0 for the passed SCO, 1 for one level
above, and so on). Values increase as you move up the hierarchy toward
the top-level folder.
Sample request
https://example.com/api/xml?action=sco-nav&sco-id=2006334909
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<sco-nav>
<sco sco-id="624522" type="folder" icon="folder" depth="2">
<name>User Content</name>
</sco>
<sco sco-id="2006258747" type="folder" icon="folder" depth="1">
<name>[email protected]</name>
</sco>
<sco sco-id="2006334909" type="content" icon="producer" depth="0">
<name>Test Quiz</name>
</sco>
</sco-nav>
</results>
See also
sco-move
sco-search
Availability
Breeze 4
Description
Provides a list of all SCOs that have content matching the search text.
The sco-search action searches the content of some types of SCOs for the query string. The types of SCOs searched
include presentation archives, meeting archives, and the presentation components of a course or curriculum. A
presentation that is included in a course returns two sets of results, one for the actual presentation and one for the
course. The search does not include the SCO name or any metadata about the SCO stored in the database.
The query is not case-sensitive and allows wildcards at the end of a query string. The allowed wildcards are:
• An asterisk (*) to match any character or characters
• A question mark (?) to match any one character
For example, you can use the query strings quiz, qu*, or qui? . However, you cannot use a wildcard at the beginning or
within a query string.
You can also use the operators and and or to return multiple matches, with spaces separating the operator and the
search terms, like this:
https://example.com/api/xml?action=sco-search&query=quiz or test
If you search on quizortest, for example, the server interprets it as a literal string and returns only exact matches.
Request URL
http://server_name/api/xml
?action=sco-search
&query=querystring
&filter-definition=value
&sort-definition=value
&session=BreezeSessionCookieValue
Parameters
query Query string Y A string to search for. To use any of these special characters in the
query string, escape them with a backslash before the character:
+ - && || ! ( ) { } [ ] ^ " ~ *
? : \
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
You can filter the response on any element or attribute it contains.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<sco-search-info>
<sco sco-id=integer folder-id=integer type=allowedValue
icon=allowedValue byte-count=integer tree-type=integer>
<name>string</name>
<url-path>string</url-path>
<date-created>datetime</date-created>
<date-modified>datetime</date-modified>
<hit>integer</hit>
<hit-type>allowedValue</hit-type>
<thumbnail-path>string</thumbnail-path>
</sco>
</sco-search-info>
</results>
Response values
code Allowed value A code indicating the response status (see status).
sco-search-info Container The list of objects (SCOs) that match the search query.
sco Container Details about one object that matches the search.
type Allowed value The content type assigned to the SCO (see type for values).
icon Allowed value The icon that visually identifies the SCO in a user interface.
url-path String The unique identifier that comes after the domain name in the SCO
URL.
hit Integer The sequence number of this occurrence of the query string in the SCO.
hit-type Allowed value The type of content in which the search term was found. Allowed
values are metadata and slide.
hit-url String A relative URL to the position where the search term was found in the
content, for example, to a specific slide. Must be appended to the url-
path.
thumbnail-path String A relative URL to an image of the SCO that contains the search term.
Sample request
https://example.com/api/xml?action=sco-search&query=quiz
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<sco-search-info>
<sco sco-id="5677964" folder-id="2562850" type="content"
icon="producer" byte-count="5985" tree-type="13">
<name>Final Quiz</name>
<url-path>/p46125962/</url-path>
<date-created>2005-05-09T14:24:36.390-07:00</date-created>
<date-modified>2005-05-09T14:24:36.390-07:00</date-modified>
<hit>0</hit>
<hit-type>metadata</hit-type>
</sco>
<sco sco-id="5677964" folder-id="2562850" type="content"
icon="producer" byte-count="5985">
<name>Final Quiz</name>
<url-path>/p46125962/</url-path>
<date-created>2005-05-09T14:24:36.390-07:00</date-created>
<date-modified>2005-05-09T14:24:36.390-07:00</date-modified>
<hit>7</hit>
<hit-type>slide</hit-type>
<hit-url>slide=7</hit-url>
</sco>
...
</sco-search-info>
</results>
sco-search-by-field
Availability
Acrobat Connect Pro 7
Description
Provides a list of all SCOs matching the search text within the specified field. This action allows you to search for
objects in the database based on the SCO’s name, description, or author, or all three of those fields.
The sco-search-by-field action searches the content of some types of SCOs for the query string. The search
includes folders, training courses, curriculums, meetings, content, and archives.
To search for multi-word terms with spaces between the words, search only on the first word in the term and use a
wildcard at the end. For example, to search for Sales Presentation, use the following string:
query=sales*
Note: The sco-search-by-field command does not support the and/or operators.
Request URL
http://server_name/api/xml
?action=sco-search-by-field
&query=SearchTerm
&field=allowedValue
Parameters
query String Y The term to search for within the specified field. The query is case-
insensitive.
field String N The field to search. Accepts four possible values: name,
description, author, or allfields:
• author matches the full name field (not the first-name or last-
name fields) of the principal that created the SCOs.
Filters
Filters are supported on any field that can be returned. For example, you can use
&filter-gt-date-created=2007-09-12T08:00:00.000
if you want to show only results created after 8:00 AM on September 12, 2007.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<sco-search-info>
<sco sco-id=integer tree-id=integer folder-id=integer type=allowedValue
status=allowedValue sco-data-id=integer source-sco-id=integer host-id=integer author-contact-
id=integer learning-time=allowedValue lang=allowedValue seq-id=integer icon=allowedValue
display-seq=integer max-retries=integer version=integer account-id=integer tree-type=integer>
<name>string</name>
<url-path>string</url-path>
<date-created>datetime</date-created>
<date-modified>datetime</date-modified>
<principal-name>string</principal-name>
<folder-name>string</folder-name>
</sco>
</sco-search-info>
</results>
Response value
code Allowed value A code indicating the response status (see status).
sco-search-by-field-info Container The list of objects (SCOs) that match the search query.
sco Container Details about one object that matches the search.
type Allowed value The content type assigned to the SCO (see type for values).
icon Allowed value The icon that visually identifies the SCO in a user interface.
url-path String The unique identifier that comes after the domain name in
the SCO URL.
folder-name String The name of the folder in which the SCO is stored.
Sample request
https://example.com/api/xml?action=sco-search-by-field&query=Marketing*&field=description
Sample response
<results>
<status code="ok"/>
<sco-search-by-field-info>
<sco sco-id="2007775205" tree-id="" folder-id="2007470298" type="meeting" status="" sco-
data-id="" source-sco-id="2007470292" host-id="" author-contact-id="" learning-time=""
lang="en" seq-id="" icon="virtual-classroom" display-seq="0" max-retries="" version="0"
account-id="2007470268" tree-type="4">
<name>virt1</name>
<url-path>/r72655596/</url-path>
<date-created>2007-10-10T16:41:31.643-07:00</date-created>
<date-modified>2007-10-10T16:41:31.643-07:00</date-modified>
<principal-name>Piet Pompies</principal-name>
<folder-name>[email protected]</folder-name>
</sco>
<sco sco-id="2007775257" tree-id="" folder-id="2007775254" type="folder" status="" sco-
data-id="" source-sco-id="" host-id="" author-contact-id="" learning-time="" lang="en" seq-
id="" icon="folder" display-seq="0" max-retries="" version="0" account-id="2007470268">
<name>test1</name>
<url-path>/f13818712/</url-path>
<date-created>2007-10-10T18:00:31.083-07:00</date-created>
<date-modified>2007-10-10T18:00:31.083-07:00</date-modified>
<principal-name>trainer two</principal-name>
<folder-name>[email protected]</folder-name>
</sco>
</sco-search-by-field-info>
</results>
sco-shortcuts
Availability
Breeze 4
Description
Provides information about the folders relevant to the current user. These include a folder for the user’s current
meetings, a folder for the user’s content, as well as folders above them in the navigation hierarchy.
To determine the URL of a SCO, concatenate the url-path returned by sco-info, sco-contents, or sco-
expanded-contents with the domain-name returned by sco-shortcuts. For example, you can concatenate these
two strings:
• http://test.server.com (the domain-name returned by sco-shortcuts)
You can also call sco-contents with the sco-id of a folder returned by sco-shortcuts to see the contents of the
folder.
Request URL
http://server_name/api/xml
?action=sco-shortcuts
&session=BreezeSessionCookieValue
Parameters
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=code />
<shortcuts>
<sco tree-id=integer sco-id=integer type=allowedValue>
<domain-name>string</domain-name>
</sco>
...
</shortcuts>
</results>
Response values
code Allowed value A code indicating the response status (see status).
shortcuts Container Information about all of the folders that relate to the current user.
tree-id Integer The ID of the navigation tree that contains the folder. Several
folders might have the same tree-id.
type Allowed value The type of the folder. Allowed values are shown in the following
table.
The values that can be returned in the type attribute of the sco element (for this call only, sco-shortcuts) identify
Adobe Connect folders. Each folder type maps to a folder in Connect Central and requires certain permission levels
to access, described in the following table.
account-custom Customized content for an account, such as a customized login page, banner, and so on.
content The Shared Content folder. Requires Administrator privilege or Manage permission.
courses The Shared Training folder. Requires Administrator privilege or Manage permission.
events The Shared Events folder. Requires Administrator privilege or Manage permission.
meetings The Shared Meetings folder. Requires Administrator privilege or Manage permission.
my-courses The My Training folder. By default, the individual user has Manage permission.
my-content The My Content folder. By default, the individual user has Manage permission.
my-events The My Events folder. By default, the individual user has Manage permission.
my-meetings The My Meetings folder. By default, the individual user has Manage permission.
my-meeting-templates The My Templates folder. By default, the individual user has Manage permission.
seminars The Shared Seminars folder. Requires Administrator privilege or Manage permission.
shared-meeting-templates The Shared Templates folder. Inherits permissions from Shared Meetings.
Sample request
http://example.com/api/xml?action=sco-shortcuts
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<shortcuts>
<sco tree-id="4930295" sco-id="2006258748" type="my-courses">
<domain-name>http://example.com</domain-name>
</sco>
<sco tree-id="4930293" sco-id="2006258749" type="my-events">
<domain-name>http://example.com</domain-name>
</sco>
...
</shortcuts>
</results>
See also
sco-info, sco-expanded-contents
sco-update
Availability
Breeze 4
Description
Creates metadata for a SCO, or updates existing metadata describing a SCO.
Call sco-update to create metadata only for SCOs that represent content, including meetings. You also need to
upload content files with either sco-upload or Connect Central.
You must provide a folder-id or a sco-id, but not both. If you pass a folder-id, sco-update creates a new SCO
and returns a sco-id. If the SCO already exists and you pass a sco-id, sco-update updates the metadata describing
the SCO.
To create a course, pass type=content&icon=course, as in the following:
https://example.com/api/xml?action=sco-
update&name=AutomatedCourse&type=content&icon=course&folder-id=20002&source-sco-id=23510
After you create a new SCO with sco-update, call permissions-update to specify which users and groups can access
it.
Request URL
http://server_name/api/xml
?action=sco-update
&author-info-1=string
&author-info-2=string
&author-info-3=string
&date-begin=datetime
&date-end=datetime
&description=string
&email=string
&first-name=string
&folder-id=integer
&icon=allowedValue
&lang=allowedValue
&last-name=string
&name=string
&sco-id=integer
&sco-tag=string
&source-sco-id=integer
&type=allowedValue
&url-path=string
&session=BreezeSessionCookieValue
Parameters
author-info-1 String N Information about the author. Used only with presentations. Can be used
for the author’s name or any other information.
author-info-2 String N Additional information about the author. Used only with presentations.
Can be used for the author’s professional title or any other information.
author-info-3 String N Additional information about the author. Used only with presentations.
Can be used for the author’s company name or any other information.
date-begin Datetime N The scheduled beginning date and time, in ISO 8601 format. Used only for
meetings and courses.
date-end Datetime N The scheduled ending date and time, in ISO 8601 format. Used only for
meetings and courses.
email String N The e-mail address of the contact person for a presentation (used only
with presentation SCOs).
first-name String N The first name of the contact person for a presentation (used only with
presentation SCOs).
folder-id Integer Y/N The ID of the folder in which a new SCO will be stored. Required for a new
SCO, but do not use for an existing SCO.
lang Allowed value N An abbreviation for the language associated with the SCO (see lang for
values). If not specified, the default value for the folder in which the SCO
is created is used.
icon Allowed value N The visual symbol used to identify a SCO in Connect Central; also provides
information about the SCO in addition to its type.
last-name String N The last name of the contact person for a presentation (used only with
presentations).
name String Y/N The name of the SCO, with or without spaces. Required to create a SCO.
sco-id Integer Y/N The unique ID of a SCO to update. Use sco-id or folder-id, but not
both. Required to update an existing SCO.
sco-tag String N A label for any information you want to record about a course. Use only
with courses.
source-sco-id Integer N The unique ID of a template you can use to create a meeting or a piece of
content from which you can build a course.
type Allowed value N The type of the new SCO (for allowed values, see type). The default value
is content.
url-path String N The custom part of the URL to the meeting room that comes after the
domain name. The url-path must be unique within the folder. If not
specified, the server assigns a value.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do
not use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<sco folder-id=integer lang=allowedValue type=allowedValue
sco-id=integer version=integer account-id=integer icon=integer>
<url-path>string</url-path>
<description>string</description>
<name>string</name>
</sco>
</results>
Response values
code Allowed value A code indicating the response status (see status).
sco Container Information about a new SCO just created, including the sco-id.
Returned only if you create a SCO.
folder-id Integer The ID of the folder in which the new SCO is stored.
lang Allowed value A code for the language associated with the SCO (see lang for values).
type Allowed value The type of the new SCO (see type for values).
version Integer The version number of the new SCO. When the SCO is first created, the
version is 0.
account-id Integer The ID of the account in which the new SCO is created.
icon Integer The type of icon that identifies a new SCO in Connect Central (see icon
for values).
url-path String The part of the SCO URL that comes after the domain name and
uniquely identifies the SCO.
Sample request
https://example.com/api/xml?action=sco-update&folder-id=2006258747
&description=test&name=More About Web Communities&type=content
&lang=en
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<sco folder-id="2006258747" account-id="624520" type="content" lang="en"
icon="content" sco-id="2006752036" version="0">
<url-path>/p53884157/</url-path>
<description>test</description>
<name>More About Web Communities</name>
</sco>
</results>
See also
sco-upload
sco-upload
Availability
Breeze 4
Description
Uploads a file to the server and then builds the file, if necessary.
If you are adding a new file, call sco-update first and pass the sco-id returned to sco-upload. If you are updating
the content of a file that already exists on the server, you can call sco-upload directly.
You must call sco-upload within an HTML form element. The form element must have an encoding type of
multipart/form-data. The HTML form must also have an input element with name=file, as this example shows:
<FORM action="http://domain-name/api/xml?action=sco-upload&sco-id=xx&summary=xxx&title=xxx"
enctype="multipart/form-data" method="post">
<P>
What files are you sending?
<INPUT type="file" name="file">
<BR>
<INPUT type="submit" value="Send"> <INPUT type="reset">
</FORM>
This form uploads a single file. To upload multiple files (for example, a PPT and a PPC file), you must use additional
input elements with name=file, for example:
<FORM action="http://domain-name/api/xml?action=sco-upload&sco-
id=xxx&summary=xxx&title=xxxx" enctype="multipart/form-data" method="post">
<P>
PPT files you are sending <INPUT type="file" name="file"><BR>
PPC files you are sending <INPUT type="file" name="file"><BR>
<INPUT type="submit" value="Send"> <INPUT type="reset">
</FORM>
After the upload, call sco-info to get the status of the SCO. The status is initially in-progress, which means that the
content is being built. When the status becomes active, the content build is finished, and users can access the content.
Request URL
http://server_name/api/xml
?action=sco-upload
&file=formElementName
&sco-id=integer
&summary=string
&title=string
&session=BreezeSessionCookieValue
Parameters
file Form element Y The file to upload, sent from an input element with name=file in an
name HTML form. The HTML form must also have an encoding type of
multipart/form-data defined in the form element.
sco-id Integer Y The ID of the SCO you want to upload, returned by sco-update.
summary String N A brief description of the SCO that Adobe Connect Central or your
application displays.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<files>
<file>
<path>string</path>
</file>
</files>
</results>
Response values
code Allowed value A code indicating the response status (see status).
files Container Information about all of the uploaded files. Deprecated and may be
removed in a future release.
file Container Information about one file. Deprecated and may be removed in a
future release.
path String The path to the newly uploaded file. For Adobe internal use only.
Deprecated and may be removed in a future release.
Sample request
This request is created by uploading a file through an HTML form:
http://example.com/api/xml?action=sco-upload&sco-id=2006768386
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<files>
<file>
<path>624520/2006768386-10/input/WhatMakesAGreatFilm.ppt</path>
</file>
</files>
</results>
See also
sco-update
user-accounts
Availability
Breeze 4
Description
Provides a list of the accounts a user belongs to.
The user-accounts action is only used when a user belongs to more than one account on the server and uses the same
login ID and password for each. In that case, a user’s login is likely to fail with a status message of too-much-data.
This action is useful when you want to retrieve a list of a user’s accounts and give the user a choice of which account
to log in to.
Request URL
http://server_name/api/xml
?action=user-accounts
&login=string
&password=string
&session=BreezeSessionCookieValue
Parameters
login String Y The user’s login name, which may be the user’s e-mail address.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted. The default sort is by account-name.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
<users>
<user user-id=integer account-id=integer>
<name>string</name>
<date-expired>datetime</date-expired>
</user>
...
</users>
</results>
Response values
code Allowed value A code indicating the response status (see status).
users Container Information about the accounts the user belongs to.
name String The name of the account the user belongs to.
date-expired Datetime The date and time the user’s login expires.
Sample request
https://sample.com/api/xml?action=user-accounts&[email protected]
&password=bigdog
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<users>
<user user-id="2006258745" account-id="624520">
<name>Test Account</name>
<date-expired>2999-12-31T16:00:00.000-08:00</date-expired>
</user>
</users>
</results>
user-transcript-update
Availability
Breeze 5
Description
Overrides the score on an item within a curriculum.
For example, you can use user-transcript-update to give a user a score for an external training. This action works
only for items within a curriculum, and you need manage permission for the curriculum.
Request URL
http://server_name/api/xml
?action=user-transcript-update
&curriculum-id=integer
&sco-id=integer
&status=allowedValue
&score=integer
&principal-id=integer
&session=BreezeSessionCookieValue
Parameters
sco-id Integer Y The unique ID of a SCO with a score you want to override.
status Allowed value Y A value showing the status of the user’s attempt to use this SCO. Allowed
values are completed, incomplete, user-passed, user-failed, and
not-attempted.
score Integer Y An integer value that represents the score the user has attained on this
SCO.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
https://example.com/api/xml?action=user-transcript-update
&curriculum-id=2006298444&sco-id=2006298445&status=user-passed
&principal-id=2006258745&score=100
Sample response
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
See also
learning-path-info, learning-path-update
user-update-pwd
Availability
Breeze 4
Description
Changes a user’s password. A password can be changed in either of these cases:
• By an Administrator logged in to the account, with or without the user’s old password
• By any Adobe Connect Server user, with the user’s principal-id number, login name, and old password
An Administrator can create rules for valid passwords on the server. These rules might include, for example, the
number and types of characters a password must contain. If a user submits a new password that does not adhere to the
rules, Adobe Connect would throw an error showing that the new password is invalid.
When you call user-update-pwd, the password is sent over HTTP or HTTPS in hashed form.
Request URL
http://server_name/api/xml
?action=user-update-pwd
&user-id=integer
&password-old=string
&password=string
&password-verify=string
&session=BreezeSessionCookieValue
Parameters
password-old String Y/N The user’s current password. Required for regular users, but not for
Administrator users.
session String N The value of the BREEZESESSION cookie. Use this parameter if you do not
use a client-side cookie management library.
Filters
Results cannot be filtered or sorted.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue />
</results>
Response values
code Allowed value A code indicating the response status (see status).
Sample request
This request can be used by an Administrator to change a user’s password without knowing the old password:
https://example.com/api/xml?action=user-update-pwd&user-id=12345&password=newone&password-
verify=newone
Sample response
This response shows that the change was successful:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
filter-definition
Description
A filter is a special type of parameter that reduces the volume of the response. When you see filter-definition in a
request URL syntax, substitute a filter definition.
To create a filter definition, start with the keyword filter, add an modifier (if desired), then a field name (if allowed),
and then a value, using this syntax:
filter-modifier-field=value
The modifiers you can add are listed in the following table.
Filter Description
filter-field=value Returns all items for which the data in field exactly matches value.
filter-like-field=value Returns all items with the string value within field, even if field is not an exact
match.
filter-gt-datefield=value Selects all items with a date after value. Works only with date fields. The value must
be a date in ISO 8601 format.
filter-lt-datefield=value Selects all items with a date earlier than value. Works only with date fields. The value
must be a date in ISO 8601 format.
filter-gte-datefield=value Selects all items with a value infield greater than or equal to value. Works only
with date fields. The value must be a date in ISO 8601 format.
filter-lte-datefield=value Selects all items with a value in field less than or equal to value. Works only with
dates. The date uses ISO 8601 format.
filter-ismember=value Selects all principals that are members of a group, specified in a separate parameter.
Takes a Boolean value of true or false.
The value is case insensitive. For example, either of these filters matches a meeting with the name August All Hands
Meeting:
&filter-name=August All Hands Meeting
&filter-name=august all hands meeting
Some modifiers require a field name on which to filter results, for example, name. Other filters do not take a field name.
For those filters that accept field names, the allowed fields vary for different actions. Check a specific action in “Action
reference” on page 58 to learn which field names you can use in filters.
Matches items with Goals Review (or any mixed case pattern of the same string) in the name.
Matches any item that includes Goals (or any mixed case pattern of the same string) in the name, including Goals
Review and Quarterly Goals.
Excludes all items with Status (or any mixed case pattern of the same string) in the name.
Matches any item with Goals (or any mixed case pattern of the same string) in the name that is no longer active.
Matches any item with a start date of May 1, 2005, sorting the items in ascending order by name.
Returns all items with a start date after May 1, 2005 and before May 31, 2005.
See also
sort-definition
sort-definition
When you see sort-definition in a request URL in this reference, create a sort filter with a field name and a value
describing how you want the results sorted, in this syntax:
sort-field=value
Replace sort with any of these exact values: sort (for a single sort), sort1 (for the primary sort of two), or sort2 (for
a secondary sort on the results returned by sort1).
The field variable defines the field you are sorting on. The fields you can use vary by call, so check the API reference
for the call you are making.
The value is always asc (for ascending) or desc (for descending), defining the sequence of the results. Putting this all
together, the parts of a sort filter are shown in the following table:
sort Vary by call. asc or desc Sort results by the specified field, in either ascending or descending
order.
sort1 Vary by call. asc or desc Sort results by a field, either ascending or descending, and then pass the
results to the next sort.
sort2 Vary by call. asc or desc When results returned by the primary sort are equal, such as same name
or group, do a secondary sort by the specified field in either ascending
or descending order.
Simple examples of sort-field=value, with one level of sort, look like this:
sort-name=asc
sort-date=desc
The following table gives you more detail on how the sort values asc and desc work:
Value Description
asc Ascending order. For alphabetical lists, begin with A and end with Z. For lists ordered by number or date, start with lowest
number or earliest date.
desc Descending order. For alphabetical lists, begin with Z and end with A. For lists ordered by number or date, start with
highest number or most recent date.
Your results may call for using both primary and secondary sorts with sort1 and sort2. For example, when calling
principal-list to list principals, you can do a primary sort on the type field, and then a secondary sort on the name
field (this way, all principals of a specific type are grouped together and then sorted by name in each group).
You would specify two levels of sort like this:
sort1-type=asc&sort2-name=desc
See also
filter-definition
Name Description
telephony-profile-delete Deletes the specified profile and removes it from any meetings with which it is associated.
telephony-profile-list Retrieves the profiles associated with the specified user’s principal ID.
telephony-provider-conf- For the specified provider, creates conference numbers that can be used for dialing in to an audio
number-update conferences.
telephony-provider-delete Deletes a telephony provider and all information associated with that provider.
telephony-profile-delete
Deletes the specified profile and removes it from any meetings with which it is associated. To determine profile names,
see “telephony-profile-list” on page 245.
Syntax
http://<connect_server_name>/api/xml?action=telephony-profile-delete&profile-id=integer
Parameters
profile-id Y Integer that specifies the ID of the profile you want to delete.
Permission
You must have permission to modify the profile you want to delete.
Example
Request:
http://example.com/api/xml?action=telephony-profile-delete&profile-id=11066
Response:
<results>
<status code="ok"/
>
</results>
telephony-profile-info
Retrieves the settings for a specified profile.
Syntax
http://server_name/api/xml?action=telephony-profile-info&profile-id=integer
Parameters
account-id N Integer that specifies the ID of the account to which the profile belongs. If not specified, the
logged in user's account is used.
profile-id Y Integer that specifies the ID of the profile you want to view.
Permission
You must have permission to view the profile.
Example
Request:
http://example.com/api/xml?action=telephony-profile-info&profile-id=11422
Response:
<results>
<status code="ok"/>
-
<telephony-profile profile-id="11422" provider-id="11319" profile-status="enabled"
provider-type="integrated">
<adaptor-id>premiere-adaptor</adaptor-id>
<provider-name>premiere-adaptor</provider-name>
-
<class-name>
com.macromedia.breeze_ext.premiere.gateway.PTekGateway
</class-name>
<profile-name>PNA1-1</profile-name>
<provider-status>enabled</provider-status>
</telephony-profile>
-
<telephony-profile-fields disabled="" principal-id="11202" profile-id="11422" profile-
status="enabled" provider-id="11319">
<profile-name>PNA1-1</profile-name>
<x-tel-premiere-conference-id>5074202</x-tel-premiere-conference-id>
<x-tel-premiere-conference-number>1-888-208-8183</x-tel-premiere-conference-number>
<x-tel-premiere-uv-conference-number>1-888-208-8183</x-tel-premiere-uv-conference-
number>
<x-tel-premiere-participant-code>726988</x-tel-premiere-participant-code>
<x-tel-premiere-user-id>7003155</x-tel-premiere-user-id>
<x-tel-premiere-password>#C$F%P@E!i4/XRiuxhMAZLnQPpS4f0w==</x-tel-premiere-password>
<x-tel-premiere-moderator-code>7269889</x-tel-premiere-moderator-code>
</telephony-profile-fields>
</results>
telephony-profile-list
Retrieves the profiles associated with the specified user’s principal ID.
Syntax
http://server_name/api/xml?action=telephony-profile-list&principal-id=integer
Parameters
principal-id N Integer that specifies the principal ID of the user for whom profiles are retrieved. If you don’t
specify a value, the logged-in user’s principal ID is used.
Permission
You must have view permissions on the principal-id, if provided.
Example
Request:
http://example.com/api/xml?action=telephony-profile-list&principal-id=11032
Response:
<results>
<status code="ok"/>
-
<telephony-profiles>
-
<profile profile-id="11091" provider-id="11049" profile-status="enabled">
<adaptor-id>premiere-emea-adaptor</adaptor-id>
<name>Premiere EMEA</name>
<profile-name>PE1</profile-name>
</profile>
-
<profile profile-id="11232" provider-id="11035" profile-status="enabled">
<adaptor-id>premiere-adaptor</adaptor-id>
<name>Premiere NA</name>
<profile-name>P2</profile-name>
</profile>
</telephony-profiles>
</results>
telephony-profile-update
Creates a new telephony profile or updates an existing profile.
Syntax
http://server_name/api/xml?action=telephony-profile-update&principal-id=integer&profile-
name=profile-name&profile-status=profile-status&field-id=field-id&value=value&provider-
id=integer
Parameters
conf-number N String that specifies the conference number associated with this profile. If you provide a value,
any existing conference numbers for this profile are deleted.
field-id N String that specifies the field whose value needs to be updated. If this value is specified, you must
also specify a value for provider-id.
location Y if you specify a String specifying the country code (for example, UK) of the location to be updated.
value for conf-
number;
otherwise N
principal-id N Integer that specifies the user for which the profile is created or updated. If not specified, the
principal ID of the user who is currently logged in is used.
profile-id Y if you are Integer that specifies the profile to be updated. If not specified, a new profile is created.
updating a profile
profile-name Y if you are The name of the profile being created or updated.
creating a profile
profile-status Y if you are String that specifies the status of the profile. Acceptable values are enabled and disabled. If
updating a profile you disable a profile, all of its associations with meetings are removed. If you are creating a new
profile, the default value is enabled.
provider-id Y if you are String that specifies the telephony provider for the profile being created or updated
creating a profile
Permission
If you are creating a new profile, you must have modify permissions on the principal-id. If you are updating a profile,
you must have modify permissions on the profile.
Example
Request (to update a profile):
http://example.com/api/xml?action=telephony-profile-update&principal-id=11032&profile-
id=11091&profile-status=disabled
Response:
<results>
<status code="ok"/>
</results>
Response:
<results>
<status code="ok"/>
-
<profile profile-status="enabled" provider-id="11050" principal-id="11032" profile-
id="11900">
<profile-name>PE3</profile-name>
</profile>
</results>
telephony-provider-conf-number-update
For the specified provider, creates conference numbers that can be used for dialing in to an audio conferences.
Note: This API deletes any existing conference numbers.
Syntax
http://server_name/api/xml?action=telephony-provider-conf-number-update&provider-
id=integer&conf-number=integer&location=location
Parameters
provider-id Y Integer specifying the provider ID for which the conference number is to be updated.
location Y String specifying the country code (for example, UK) of the location to be updated.
Permission
You must have permission to modify the provider whose conference number is being updated.
Example
Request:
http://example.com/api/xml?action=telephony-provider-conf-number-update&provider-
id=11712&conf-number=4567&location=USA
Response:
<results>
<status code="ok"/>
</results>
telephony-provider-delete
Deletes a telephony provider and all information associated with that provider.
Syntax
http://server_name/api/xml?action=telephony-provider-delete&provider-id=integer
Parameters
provider-id Y Integer specifying the provider ID for the provider you want to delete.
Permission
You must have permission to modify the provider which is being deleted.
Example
Request:
http://example.com/api/xml?action=telephony-provider-delete&provider-id=11049
Response:
<results>
<status code="ok"/>
</results>
telephony-provider-dial-in-info-update
Creates or updates the dial-in-sequence for a provider.
Note: This API deletes any existing dial-in sequences.
Syntax
http://server_name/api/xml?action=telephony-provider-dial-in-info-udpate&step-type=step-
type&name=name&provider-id=integer&field-id=integer&value=value
Parameters
step-type Y String that specifies the type of step that is being updated or added. Acceptable values are conf-
num, dtmf, and delay.
field-id N Integer that specifies the field whose value needs to be updated.
name N String that specifies the name of the dial-in step being created.
provider-id Y Integer that specifies the ID of the provider whose dial-in step being created.
Permission
You must have modify permission on the provider whose dial-in-sequence is being update or created.
Example
Request:
http://example.com/api/xml?action=telephony-provider-dial-in-info-udpate&step-type=conf-
num&name=xyz&provider-id=11814&field-id=11058&value=1000
Response:
<results>
<status code="ok"/>
</results>
telephony-provider-field-delete
Deletes a provider field. For a list of available fields, see “telephony-provider-field-list” on page 250.
Syntax
http://server_name/api/xml?action=telephony-provider-field-delete&provider-id=integer&xml-
name=xml-name&field-id=integer
Parameters
xml-name N if field-id is String that specifies the XML name of the field to be deleted. If you also specify a value for field-
specified, id, this value is ignored.
otherwise Y
Permission
You must have modify permission on the provider whose field is being deleted
Example
Request:
http://example.com/api/xml?action=telephony-provider-field-delete&provider-id=11814&xml-
name=x-tel-premiere-emea-uv-conference-number
Response:
<results>
<status code="ok"/>
</results>
telephony-provider-field-list
Displays a list of the fields of a provider.
Syntax
http://server_name/api/xml?action=telephony-provider-field-list&provider-id=integer
Parameters
Permission
You must have view permissions on the provider.
Example
Request:
http://example.com/api/xml?action=telephony-provider-field-list&provider-id=11718
Response:
<results>
<status code="ok"/>
-
<telephony-provider-fields>
-
<field provider-id="11718" field="11038" field-id="x-premiere-direct-phone" display-
in-meeting="none" required="false" user-specified="true" input-type="text" is-hidden="true">
<name>Phone Number</name>
</field>
-
<field provider-id="11718" field="11039" field-id="x-premiere-direct-phone-key"
display-in-meeting="none" required="false" user-specified="false" input-type="text" is-
hidden="true">
<name>{x-premiere-direct-phone-key}</name>
</field>
-
<field provider-id="11718" field="11046" field-id="x-tel-premiere-sign-up-text"
display-in-meeting="none" required="false" user-specified="false" input-type="text" is-
hidden="false">
-
<name>
To learn more about Premiere Global or to sign up for a new account, please go
to
<u><a target="_blank"
href="http://www.premiereglobal.com/adobeconnect/">http://www.premiereglobal.com/adobeconnec
t</a></u>.
</name>
</field>
-
<field provider-id="11718" field="11051" field-id="x-tel-premiere-emea-conference-
number-part2" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part2}</name>
</field>
-
<field provider-id="11718" field="11052" field-id="x-tel-premiere-emea-conference-
number-part3" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part3}</name>
</field>
-
<field provider-id="11718" field="11053" field-id="x-tel-premiere-emea-conference-
number-part4" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part4}</name>
</field>
-
<field provider-id="11718" field="11054" field-id="x-tel-premiere-emea-conference-
number-part5" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part5}</name>
</field>
-
<field provider-id="11718" field="11055" field-id="x-tel-premiere-emea-conference-
number-part6" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part6}</name>
</field>
-
<field provider-id="11718" field="11056" field-id="x-tel-premiere-emea-conference-id"
display-in-meeting="none" required="false" user-specified="false" input-type="text" is-
hidden="true">
<name>{x-tel-premiere-emea-conference-id}</name>
</field>
-
<field provider-id="11718" field="11057" field-id="x-tel-premiere-emea-conference-
number" display-in-meeting="participants" required="false" user-specified="false" input-
type="textarea" is-hidden="false">
<name>Conference Number(s)</name>
</field>
-
<field provider-id="11718" field="11058" field-id="x-tel-premiere-emea-uv-conference-
number" display-in-meeting="none" required="false" user-specified="false" input-type="text"
is-hidden="true">
<name>{x-tel-premiere-emea-uv-conference-number}</name>
</field>
-
<field provider-id="11718" field="11059" field-id="x-tel-premiere-emea-participant-
code" display-in-meeting="participants" required="false" user-specified="false" input-
type="text" is-hidden="false">
<name>Participant Code</name>
</field>
-
<field provider-id="11718" field="11060" field-id="x-tel-premiere-emea-user-id"
display-in-meeting="none" required="true" user-specified="true" input-type="text" is-
hidden="false">
<name>Client ID</name>
</field>
-
<field provider-id="11718" field="11061" field-id="x-tel-premiere-emea-password"
display-in-meeting="none" required="true" user-specified="true" input-type="password" is-
hidden="false">
<name>Premiere Password</name>
</field>
-
<field provider-id="11718" field="11062" field-id="x-tel-premiere-emea-moderator-
code" display-in-meeting="hosts" required="true" user-specified="true" input-type="text" is-
hidden="false">
<name>Moderator Code</name>
</field>
</telephony-provider-fields>
</results>
telephony-provider-field-update
Creates or updates a provider field. If updating a field might result in profiles for this provider to be invalid, all profiles
are disassociated from meetings.
For example, if you change a field from optional to mandatory, some existing profiles might not meet the new criteria.
Therefore, Adobe Connect disassociates all this provider’s profiles from meetings. After updating the field or fields,
you need to update profiles as needed and then re-associate them with meetings.
Syntax
http://server_name/api/xml?action=telephony-provider-field-update&provider-id=integer&input-
type=input-type&display-in-meeting=display-in-meeting&required=boolean&user-
specified=boolean&is-hidden=boolean
Parameters
provider-id Y Integer that specifies the provider whose fields need to be updated or created.
field-id Y if you don’t Integer that specifies the ID of the field to be updated or created.
specify a value
for xml-name;
otherwise N
xml-name Y if you don’t String that specifies the XML name of the field to be updated or created. If a value is also specified
specify a value for field-id, xml-name is ignored.
for field-id;
otherwise N
input-type Y Input type of this field. Acceptable values are text, password, textarea, and url.
display-in-meeting N String that specifies which participants can see this field in the Adobe Connect meeting room.
Acceptable values are none and participants.
user-specified N Boolean value that specifies whether this is a field that the user specifies, such as password.
is-hidden N Boolean value that specifies whether this field can be displayed through a user interface.
Permission
You must have permission to modify the provider whose field you are creating or updating.
Example
Request (to create a provider field):
http://example.com/api/xml?action=telephony-provider-field-update&provider-id=11718&input-
type=text&display-in-meeting=participants&required=true&user-specified=true&is-hidden=false
Response:
<results>
<status code="ok"/>
-
<telephony-provider provider-status="enabled" provider-type="user-conf" provider-
id="12000">
<name>my-provider</name>
<adaptor-id>12000-adaptor</adaptor-id>
</telephony-provider>
</results>
Response:
<results>
<status code="ok"/>
</results>
telephony-provider-info
Displays information on a telephony provider, including dial-in sequence, provider fields, and associated conference
numbers.
Syntax
http://server_name/api/xml?action=telephony-provider-info&is-meeting-host=boolean&provider-
id=integer&account-id=integer&principal-id=integer
Parameters
provider-id Y Integer that specifies the provider ID for which information is to be retrieved.
principal-id N Integer which, if specified, represents the principal ID of the user who created the provider. If not
specified, this value is the principal ID of the currently logged-in user.
account-id N If provider-id represents an account-level provider (that is, a provider that was not created by a
user), this value is a string that specifies the ID of the account to which the provider belongs. If not
specified, this value is the ID of the account of the logged-in user.
is-meeting-host N A Boolean value that specifies whether provider-id is a user-configured provider. If this value is
true, information is returned based on the value provided for principal-id.
Permission
For a user-configured provider, you must have view permissions on the provider. For account-level providers, you
must have view permission on the account.
Example
Request:
http://example.com/api/xml?action=telephony-provider-info&is-meeting-host=false&provider-
id=11718&account-id=7
Response:
<results>
<status code="ok"/>
-
<telephony-provider provider-id="11718" provider-type="integrated" token-length="0">
-
<class-name>
com.macromedia.breeze_ext.premiere.gateway.EMEA.PTekGateway
</class-name>
<adaptor-id>premiere-emea-adaptor</adaptor-id>
<name>Premiere EMEA</name>
<token-prefix>#4</token-prefix>
<token-postfix>#</token-postfix>
<provider-status>enabled</provider-status>
</telephony-provider>
-
<telephony-provider-dial-in-info>
<step provider-id="11718" sequence-number="1" field="11058" step-type="conf-num"/>
-
<step provider-id="11718" sequence-number="2" field="" step-type="delay">
<value>6000</value>
</step>
<step provider-id="11718" sequence-number="3" field="11059" step-type="dtmf"/>
-
<step provider-id="11718" sequence-number="4" field="" step-type="dtmf">
<value>#</value>
</step>
-
<step provider-id="11718" sequence-number="5" field="" step-type="delay">
<value>5000</value>
</step>
</telephony-provider-dial-in-info>
-
<telephony-provider-fields>
-
<field provider-id="11718" field="11038" field-id="x-premiere-direct-phone" display-
in-meeting="none" required="false" user-specified="true" input-type="text" is-hidden="true">
<name>Phone Number</name>
</field>
-
<field provider-id="11718" field="11039" field-id="x-premiere-direct-phone-key"
display-in-meeting="none" required="false" user-specified="false" input-type="text" is-
hidden="true">
<name>{x-premiere-direct-phone-key}</name>
</field>
-
<field provider-id="11718" field="11046" field-id="x-tel-premiere-sign-up-text"
display-in-meeting="none" required="false" user-specified="false" input-type="text" is-
hidden="false">
-
<name>
To learn more about Premiere Global or to sign up for a new account, please go
to
<u><a target="_blank"
href="http://www.premiereglobal.com/adobeconnect/">http://www.premiereglobal.com/adobeconnec
t</a></u>.
</name>
</field>
-
<field provider-id="11718" field="11051" field-id="x-tel-premiere-emea-conference-
number-part2" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part2}</name>
</field>
-
<field provider-id="11718" field="11052" field-id="x-tel-premiere-emea-conference-
number-part3" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part3}</name>
</field>
-
<field provider-id="11718" field="11053" field-id="x-tel-premiere-emea-conference-
number-part4" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part4}</name>
</field>
-
<field provider-id="11718" field="11054" field-id="x-tel-premiere-emea-conference-
number-part5" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part5}</name>
</field>
-
<field provider-id="11718" field="11055" field-id="x-tel-premiere-emea-conference-
number-part6" display-in-meeting="participants" required="false" user-specified="false"
input-type="textarea" is-hidden="false">
<name>{x-tel-premiere-emea-conference-number-part6}</name>
</field>
-
<field provider-id="11718" field="11056" field-id="x-tel-premiere-emea-conference-id"
display-in-meeting="none" required="false" user-specified="false" input-type="text" is-
hidden="true">
<name>{x-tel-premiere-emea-conference-id}</name>
</field>
-
<field provider-id="11718" field="11057" field-id="x-tel-premiere-emea-conference-
number" display-in-meeting="participants" required="false" user-specified="false" input-
type="textarea" is-hidden="false">
<name>Conference Number(s)</name>
</field>
-
<field provider-id="11718" field="11058" field-id="x-tel-premiere-emea-uv-conference-
number" display-in-meeting="none" required="false" user-specified="false" input-type="text"
is-hidden="true">
<name>{x-tel-premiere-emea-uv-conference-number}</name>
</field>
-
<field provider-id="11718" field="11059" field-id="x-tel-premiere-emea-participant-
code" display-in-meeting="participants" required="false" user-specified="false" input-
type="text" is-hidden="false">
<name>Participant Code</name>
</field>
-
<field provider-id="11718" field="11060" field-id="x-tel-premiere-emea-user-id"
display-in-meeting="none" required="true" user-specified="true" input-type="text" is-
hidden="false">
<name>Client ID</name>
</field>
-
<field provider-id="11718" field="11061" field-id="x-tel-premiere-emea-password"
display-in-meeting="none" required="true" user-specified="true" input-type="password" is-
hidden="false">
<name>Premiere Password</name>
</field>
-
<field provider-id="11718" field="11062" field-id="x-tel-premiere-emea-moderator-
code" display-in-meeting="hosts" required="true" user-specified="true" input-type="text" is-
hidden="false">
<name>Moderator Code</name>
</field>
</telephony-provider-fields>
</results>
telephony-provider-list
Returns a list of telephony providers.
• To return a list of user-configured providers for a particular user, pass the user’s principal ID to principal-id and
pass a value of true for is-meeting-host.
• To return a list of account-level providers for a specified account, pass the account’s ID to account-id and pass a
value of false for is-meeting-host.
• To return a list of account-level providers for the account of the currently logged-in user, pass a value of false for
is-meeting-host.
Syntax
http://server_name/api/xml?action=telephony-provider-list&is-meeting-host=boolean&account-
id=integer&principal-id=integer
Parameters
principal-id Y if the value of is- Integer that represents the principal ID of the user who created the user-configured providers. If
meeting-host is not specified, the principal ID of the logged-in user is used.
true; otherwise
N
account-id N Integer that specifies the ID of the account to which the account-level providers belong. If not
specified, the account ID of the logged-in user is used.
is-meeting-host N Boolean value that, if true, indicates that the providers are user-configured and returns a list of
providers based on the value of principal-id. The default value is false.
Permission
For a user-configured provider, you must have view permissions on the provider. For account-level providers, you
must have view permission on the account.
Example
Request:
http://example.com/api/xml?action=telephony-provider-list&is-meeting-host=true&principal-
id=11032
Response:
<results>
<status code="ok"/>
-
<providers-user>
-
<provider provider-id="11722" acl-id="11032" provider-type="user-conf">
<adaptor-id>11722-adaptor</adaptor-id>
<name>Test</name>
<provider-status>enabled</provider-status>
</provider>
</providers-user>
</results>
telephony-provider-update
Creates a new provider or updates an existing provider. Only users who are administrators or meeting hosts can create
a provider.
• To create or update a user-configured provider for the currently logged-in user, pass a value of true for is-meeting-host.
• To create or update a user-configured provider for a particular user, pass the user’s principal ID to principal-id and
pass a value of true for is-meeting-host.
• To update an account-level provider for a specified account, pass the account’s ID to account-id and pass a value
of false for is-meeting-host.
Syntax
http://server_name/api/xml?action=telephony-provider-update&is-meeting-
host=boolean&principal-id=integer&name=name
Parameters
provider-id Y if you are Integer that specifies the ID of the provider to be updated. If not specified, a new provider is
updating a created.
provider;
otherwise N
account-id N The ID of the account to which this provider belongs. If not specified, the ID of the logged- in
account is used.
is-meeting-host N Boolean value that, if true, indicates that the provider is user-configured and creates or updates
the provider based on the value of principal-id.
principal-id N Integer that specified the principal ID of the user for whom a provider needs to be created or
updated. If not specified, the logged-in user's principal ID is used.
provider-status N Boolean value that specifies the status of the provider that is being updated or created.
Acceptable values are enabled and disabled. If you are creating a new provider, the default
value is enabled.
name Y if you are String that specifies the name of the provider being created or updated.
creating a new
provider;
otherwise N
Permission
If you are creating an account-level provider, you must have modify permission on the account. If you are creating a
user-configured provider, you must be a member of the meeting hosts or administrators group. If you are updating a
provider, you must have modify permission on the provider.
Example
Request (for creating a provider):
http://example.com/api/xml?action=telephony-provider-update&is-meeting-host=true&principal-
id=11032&name=my-provider2
Response:
<results>
<status code="ok"/>
-
<telephony-provider provider-status="enabled" provider-type="user-conf" provider-
id="12125">
<name>my-provider2</name>
<adaptor-id>12125-adaptor</adaptor-id>
</telephony-provider>
</results>
Response:
<results>
<status code="ok"/>
</results>
access
Description
An attribute describing the level of access a user has to a course or curriculum.
Values
Value Description
access-blocked The course or curriculum is restricted and users cannot take it.
access-hidden The course or curriculum is restricted, users cannot take it, and it is hidden in Adobe Connect Central (or the user
interface of a custom application, if you use this value).
access-open The course or curriculum is open and users can take it.
access-pass The user has already taken the course or curriculum and passed it.
feature-id
Description
An attribute describing a feature that either users can use or things that can occur during a meeting. Use feature-id
with the meeting-feature-update action.
For more information on the pods that can be enabled or disabled, see the Adobe Connect 9 Using Guide.
Values
fid-archive Lets a host start and stop the recording of a meeting. Disabling this setting means that recording
settings are not controllable by the host.
To set Adobe Connect to automatically record all meetings, you must both disable fid-archive
and enable fid-archive-force.
fid-archive-force Sets all meetings to be recorded upon the start of the meeting. Recorded meetings appear in
Adobe Connect Central.
fid-archive-publish-link When meetings are set to be automatically recorded (by enabling fid-archive-force), lets host
create a link to the recording in the meeting folder.
fid-chat-transcripts Creates a transcript file (one per meeting session) of all text messages exchanged in Chat, Q&A, and
IM Pods.
fid-meeting-app-sharing Lets host request control of attendee's input device (mouse or keyboard) when attendee is sharing
their screen, desktop, or application.
fid-meeting-auto-promote Lets hosts enable the option to automatically promote participants to presenters.
fid-meeting-chat-clear Automatically clears Chat pod history when a new session of an existing meeting is started.
fid-meeting-desktop-sharing Lets users share their screen (both the complete desktop and individual applications).
fid-meeting-disclaimer Shows a disclaimer (for example, explaining that the meeting is being recorded) when a user starts
or attends any meeting in this account. To proceed with the meeting, the host or attendees must
first accept the disclaimer. If a user does not accept, the disclaimer user is returned to the Adobe
Connect home page.
fid-meeting-flv Lets users use FLV files and mp3 files in the meeting.
fid-meeting-full-screen- Enables "Presenter Changes affect everyone" for full-screen mode. Note: this feature does not
affects-all enable or disable users’ ability to enter full-screen mode.
fid-meeting-im Enables the Instant Messages pod. This feature is part of the Adobe Connect integration with
supported Microsoft real-time communication servers.
Disable this feature when you want to show the Invitee List pod (fid-meeting-invitee-
presence=true) but hide the associated Instant Messages pod.
fid-meeting-invitee- Enables the Invitee List pod and the associated Instant Messages pod. This feature is part of the
presence Adobe Connect integration with supported Microsoft real-time communication servers.
fid-meeting-manage-link Enables the "Manage Room with Web Manager" link in the meeting menu.
fid-meeting-notes-clear Automatically clears Notes pod history when a new session of an existing meeting is started.
fid-meeting-passcode- Meeting hosts can assign passcodes to meetings in Adobe Connect Central. However, by default,
notallowed this feature is disabled. Account Administrators can enable the feature in Adobe Connect Central
or you can pass this feature ID and set enable=false.
fid-meeting-pause-annotate Lets users pause during screen sharing and annotate on an overlay white board.
fid-meeting-pr-mode Enables Preparing Mode, which lets hosts change the meeting layout without affecting other users’
layouts. When the layout is ready, disable this mode to show the layout to all users.
fid-meeting-qa-clear Automatically clears Q & A pod history when a new session of an existing meeting is started.
fid-meeting-room-bg Lets a host change a meeting room background. Backgrounds are typically set in the meeting
template.
fid-meeting-shared-library Lets users select documents from the Content Library while in the Share pod. (This setting doesn't
affect the File Share pod.)
fid-meeting-shared-upload Lets users upload documents to the Content Library while in the Share pod. (This setting doesn't
affect the File Share pod.)
fid-meeting-show-talker Lets hosts enable or disable the "Who’s Speaking" area in a meeting.
fid-meeting-voip Enables voice controls within the meeting user interface, such as the ability to broadcast audio
using VoIP.
fid-start-meeting-button Lets a user start the meeting again after the host ends the meeting.
fid-training-openenroll Enables open enrollment, which lets users enroll themselves in a course without approval from the
Training Manager.
Disabling this feature for an account means that a training manager cannot change the settings of
a course in Adobe Connect Central to let learners enroll without approval.
field
Description
An element containing information about a custom field defined for an object or principal.
Attributes
permission-id Allowed value The permission needed to access the custom field. See permission-id for valid
values.
object-type Allowed value A definition for a valid object on the server (see type for values).
field-id String A piece of text that identifies the custom field. Adobe Connect Central does not
display the field-id, but various actions return it.
account-id Integer An ID for the user who is presently logged in, assigned by the server.
display-seq Integer The order in which the custom field is displayed in the user interface or returned by
the action.
field-type String The type of data the field accepts. Allowed values are text, textarea, and
password.
is-primary Boolean Whether the custom field can be deleted. true means the field cannot be deleted.
false means it can.
is-required Boolean Whether the custom field is required. true means a value must be specified for this
field in each principal or SCO that uses it. false means values for this field are not
required.
custom-seq Integer The sequence number assigned to the custom field in UI display.
type String The type of custom field (see type for values).
principal-id Integer The ID of the principal for whom the custom field is defined.
icon
Description
The symbol used to identify a SCO in Adobe Connect Central.
Values
Value Description
authorware A piece of multimedia content created with Macromedia® Authorware® from Adobe.
curriculum A curriculum.
image An image.
Value Description
lang
Description
A two-letter or three-letter code describing a language according to the ISO 639 specifications. ISO 639-1 describes
two-letter codes, and ISO 639-2 describes three-letter codes. The language code affects a Adobe Connect application
display, for example, a meeting room or a Adobe Connect Central display.
Values
en eng English
ja jpn Japanese
ko kor Korean
object-type
Description
An attribute describing the type of a Adobe Connect object.
Values
Value Meaning
Value Meaning
object-type-hidden A SCO that is not visible in Adobe Connect Central (or in your application, if you use this value).
object-type-readonly A setting indicating that Adobe Connect Central displays some data, but a user cannot set the data in
Adobe Connect Central.
object-type-sco A SCO representing a meeting, course, curriculum, piece of content, folder, or any other object on the
server.
path-type
Description
The path-type attribute describes a type of learning path between two objects in a curriculum, for example, whether
one must be completed as a prerequisite to the next.
Values
Value Meaning
completion-none The current SCO is not a completion requirement for the curriculum.
prereq-hidden The target learning object is required as a prerequisite. The current learning object is hidden until the target
learning object is completed.
prereq-suggested The current SCO has a prerequisite that is recommended, not required.
preass-blocked The current SCO has a test-out. If the enrollee passes, this item is locked. If the enrollee fails, this item is
available.
preass-hidden The current SCO has a test-out. If the user passes, the current SCO can be hidden from the user. If the user
fails, the current SCO is visible and the user can enroll.
preass-optional The current SCO has a test-out. If the user passes, the current SCO is no longer required to complete the
curriculum.
permission-id
Description
The permission-id parameter (or attribute) defines a permission. Depending on the context of the action or
response, the permission might be one a principal has on a SCO, or a permission that is needed in order to execute an
action.
Values
Permission Description
view The principal can view, but cannot modify, the SCO. The principal can take a course, attend a meeting as participant,
or view a folder’s content.
host Available for meetings only. The principal is host of a meeting and can create the meeting or act as presenter, even
without view permission on the meeting’s parent folder.
mini-host Available for meetings only. The principal is presenter of a meeting and can present content, share a screen, send
text messages, moderate questions, create text notes, broadcast audio and video, and push content from web links.
remove Available for meetings only. The principal does not have participant, presenter or host permission to attend the
meeting. If a user is already attending a live meeting, the user is not removed from the meeting until the session times
out.
publish Available for SCOs other than meetings. The principal can publish or update the SCO. The publish permission
includes view and allows the principal to view reports related to the SCO. On a folder, publish does not allow the
principal to create new subfolders or set permissions.
manage Available for SCOs other than meetings or courses. The principal can view, delete, move, edit, or set permissions
on the SCO. On a folder, the principal can create subfolders or view reports on folder content.
denied Available for SCOs other than meetings. The principal cannot view, access, or manage the SCO.
Special permissions
The server defines a special principal, public-access, which combines with values of permission-id to create
special access permissions to meetings:
• principal-id=public-access and permission-id=view-hidden means the Adobe Connect meeting is public,
and anyone who has the URL for the meeting can enter the room.
• principal-id=public-access and permission-id=remove means the meeting is protected, and only
registered users and accepted guests can enter the room.
• principal-id=public-access and permission-id=denied means the meeting is private, and only registered
users and participants can enter the room.
quota-ID
Description
The quota-ID parameter defines a quota in the system. The quota type you specify determines the value of acl-id to use.
Values
concurrent-user-per-meeting- The number of concurrent users in one The tree-id of the user-meetings tree or
quota meeting. meetings tree.
training-user The number of concurrent Learners for one The account-id of the account.
account.
num-of-members-quota The number of Authors or Meeting Hosts. The principal-id for either the Authors group
or the Meeting Hosts (live-admins),
depending on which quota you want to
specify.
status
Description
A status code returned by Adobe Connect in the response to all actions in the Web Services XML API.
Response structure
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue >
</results>
or
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code=allowedValue>
<invalid field=string type=allowedValue subcode=allowedValue />
</status>
</results>
Attributes
code The status of the response.
Value Description
invalid Indicates that a call is invalid in some way. The invalid element provides more detail.
no-access Indicates that you don’t have permission to call the action. The subcode attribute provides more details.
no-data Indicates that there is no data available (in response to an action that would normally result in returning
data). Usually indicates that there is no item with the ID you specified. To resolve the error, change the
specified ID to that of an item that exists.
too-much-data Indicates that the action should have returned a single result but is actually returning multiple results. For
example, if there are multiple users with the same user name and password, and you call the login
action using that user name and password as parameters, the system cannot determine which user to log
you in as, so it returns a too-much-data error.
subcode If present, provides more detail describing the status of the response. For example, subcode values are used
to differentiate between different situations in which code is set to noaccess-.
Value Description
denied Based on the supplied credentials, you don’t have permission to call the action.
no-login The user is not logged in. To resolve the error, log in (using the login action) before you make the call.
For more information, see login.
illegalparent The specified acl-id is not a seminar or an unknown issue occured while retrieving the quota for that
seminar.
Value Description
valuelessthanorequal Value is not a valid integer or is greater than the allowed license quota for that seminar.
invalid Empty, with Information about why the call was invalid.
attributes
field String The name of the request parameter that was incorrect or missing.
subcode Allowed value A code explaining why the request was invalid (see the following
table for values).
The following table shows the allowed values for subcode when code is invalid.
Value Description
duplicate The call attempted to add a duplicate item in a context where uniqueness is required.
illegal-operation The requested operation violates integrity rules (for example, moving a folder into itself).
Returned by
All actions in the Adobe Connect Web Services XML API.
Samples
This is a successful response:
<status code="ok" />
status attribute
Description
An attribute that describes a user’s progress with a course or curriculum SCO. It is returned by actions that provide
training reports.
A curriculum or folder can only have a status of completed or incomplete.
The following table shows the allowed values for status when returned in a row element describing a course.
Value Description
user-passed The SCO has scored interactions the user has passed.
user-failed The SCO has scored interactions. The user has answered them, but failed.
completed The user has viewed all of the SCO’s content, but the content has no scored interactions.
incomplete The user has not viewed all of the SCO’s content.
not-attempted The user has not started viewing all of the SCO’s content.
review The user has passed or completed the course or used all available retries.
Sample
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<report-user-training-transcripts>
<row transcript-id="2006905612" sco-id="2006298431"
principal-id="2006258745" status="review" score="0" max-score=""
certificate="" type="content" icon="course">
<name>Test Course</name>
<url-path>/test/</url-path>
<login>[email protected]</login>
<date-taken>2006-06-30T15:23:55.070-07:00</date-taken>
<principal-name>Joy Smith</principal-name>
</row>
</report-user-training-transcripts>
</results
time-zone-id
Description
Settings that describe time zones that you can use with time-zone-id.
Values
(GMT-10:00) Hawaii 2
(GMT-09:00) Alaska 3
(GMT-07:00) Arizona 15
(GMT-06:00) Saskatchewan 25
(GMT-04:00) Santiago 56
(GMT-03:30) Newfoundland 60
(GMT-03:00) Brasilia 65
(GMT-03:00) Greenland 73
(GMT-02:00) Mid-Atlantic 75
(GMT-01:00) Azores 80
type
Description
A return element or attribute defining the type of a SCO or principal on the server. The allowed values for type are
different for SCOs and principals.
SCO types
A SCO can be content, a meeting, an event, a curriculum, a folder or tree, or other object on Adobe Connect. Most
SCOs can have any of the following values for type:
Value Description
content A viewable file uploaded to the server, for example, an FLV file, an HTML file, an image, a pod, and so on.
curriculum A curriculum.
event A event.
link A reference to another SCO. These links are used by curriculums to link to other SCOs. When content is added
to a curriculum, a link is created from the curriculum to the content.
tree The root of a folder hierarchy. A tree’s root is treated as an independent hierarchy; you can’t determine the
parent folder of a tree from inside the tree.
Content objects returned by some actions (for example, report-bulk-objects) have the type values shown in the
following table:
Value Description
authorware A piece of multimedia content created with Macromedia Authorware from Adobe.
Value Description
presentation A presentation.
Principal types
For principals, the allowed values for type are shown in the following table:
Value Description
admins The built-in group Administrators, for Adobe Connect server Administrators.
event-admins The built-in group Event Managers, for anyone who can create an Adobe Connect meeting.
learners The built-in group learners, for users who take courses.
live-admins The built-in group Meeting Hosts, for Adobe Connect meeting hosts.
Value Description
The second constructor takes a user’s login ID and password, as well as a BREEZESESSION cookie value:
public XMLApiAdapter(String baseUrl, String login, String password,
String breezesession) throws XMLApiException {
this(baseUrl, breezesession);
this.setLogin(login);
this.setPassword(password);
}
You can get the BREEZESESSION cookie value before the user logs in by calling common-info.
<%
...
breeze = new XMLApiAdapter(breezeBase, login, password, breezesession);
breeze.getBreezesession();
session.setAttribute("breezesession", breeze);
...
%>
You might also need to add session, account-id, or domain parameters to the login action (see Log in from an
application for more ways to call login).
A successful login returns this response, with a status code of ok:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
</results>
The method also adds an action name and query string that you pass to it. This is the full method:
protected URL breezeUrl(String action, String queryString)
throws MalformedURLException {
return new URL(getBaseUrl() + "/api/xml?" + "action=" + action
+ (queryString != null ? ('&' + queryString) : ""));
}
if (st.countTokens() > 1)
sessionName = st.nextToken();
if (sessionName != null&&
sessionName.equals("BREEZESESSION")) {
String breezesessionNext = st.nextToken();
int semiIndex = breezesessionNext.indexOf(';');
breezesession = breezesessionNext.substring(0, semiIndex);
}
Extract values
The getShortcuts method calls sco-shortcuts and parses the response using XPath. This is an example of how to
extract a list of sco elements and the sco-id of each:
public List getShortcuts() throws XMLApiException {
try {
Element e = request("sco-shortcuts", null);
List scosXml = XPath.selectNodes(e, "//sco");
List scos = new ArrayList();
XPath id = XPath.newInstance("./@sco-id");
for (Iterator i = scosXml.iterator(); i.hasNext();) {
Element s = (Element) i.next();
SCO sco = getSco(id.valueOf(s));
if(null != sco)
scos.add(sco);
}
return scos;
} catch (JDOMException jde) {
throw new XMLApiException(PARSE_ERROR, jde);
}
}
These lines in the createXPaths method parse for the values of code and subcode:
codePath = XPath.newInstance("//status/@code");
subcodePath = XPath.newInstance("//status/@subcode");
In the sample, the createXPaths method is called when you create an instance of XMLApiAdapter. The getStatus
method then uses codePath and subcodePath to return the code and subcode values, separated by a hyphen:
The response has a user element with information you can display or store in variables to use later:
<user user-id="2006258745" type="user">
<name>Joy Smith</name>
<login>[email protected]</login>
</user>
If you call common-info before the user logs in, the response does not have a user element.
return user;
To list a user’s meetings using the XML API, call report-my-meetings with or without a filter. Without a filter,
report-my-meetings returns all of a user’s meetings:
https://example.com/api/xml?action=report-my-meetings
You can add filter-expired=false to return only meetings that are currently in progress and scheduled in the
future:
https://example.com/api/xml?action=report-my-meetings&filter-expired=false
Even with a filter, the response is likely to have multiple meeting elements that you need to iterate through and extract
data from. A meeting element looks like this:
<meeting sco-id="2007063179" type="meeting" icon="meeting"
permission-id="host" active-participants="0">
<name>September All Hands Meeting</name>
<description>For all company employees</description>
<domain-name>example.com</domain-name>
<url-path>/sept15/</url-path>
<date-begin>2006-09-15T09:00:00.000-07:00</date-begin>
<date-end>2006-09-15T18:00:00.000-07:00</date-end>
<expired>false</expired>
<duration>09:00:00.000</duration>
</meeting>
The SCO object encapsulates data about the SCO so you can easily retrieve it from a web page (for example, HTML or
JSP) in your application.
The response returns the sco-id of the meeting, which you can extract and store:
Create a meeting
In an application, you first need to collect from the user the information needed to create or update the meeting, such
as the meeting name, date, time, and so on. With that information, use a method such as updateSco that calls the sco-
update action.
In sco-update, be sure to set the type of the SCO to meeting. As an option, you can also set a language code for the
meeting room, such as lang=en, for example:
https://example.com/api/xml?action=sco-update&folder-id=2006258750
&description=nov&name=Nov%20All%20Hands%20Meeting&type=meeting&lang=en
&date-begin=2006-11-11T09:00&date-end=2006-11-11T17:00
The updateSCO method shows how to implement the sco-update call in Java, once you collect information about the
meeting from the user:
if (CREATE.equals(action))
sb.append("folder-id=" + sco.getFolderId());
else
sb.append("sco-id=" + sco.getId());
Iterator iter = data.keySet().iterator();
while (iter.hasNext()) {
String key = (String) iter.next();
if (key.indexOf("sco-id") != -1)
continue;
if (key.indexOf("folder-id") != -1)
continue;
String value = (String) data.get(key);
sb.append("&" + key + "=" + value);
}
if (null == data.get("type"))
throw new XMLApiException("SCO type not defined");
Element e = request("sco-update", sb.toString());
XPath scoId = XPath.newInstance("//results/sco/@sco-id");
if (scoId.valueOf(e) == null)
return null;
else
return scoId.valueOf(e);
} catch (JDOMException jde) {
throw new XMLApiException(PARSE_ERROR, jde);
} catch (ParseException pe) {
throw new XMLApiException(PARSE_ERROR, pe);
}
}
https://example.com/api/xml?action=permissions-update&acl-id=2006334033
&principal-id=public-access&permission-id=view-hidden
Once a user chooses these values, the setPermissions method calls permissions-update to set the meeting access:
public void setPermissions(String aclId, String principalId,
String permissionId) throws XMLApiException {
request("permissions-update", "acl-id=" + aclId + "&principal-id="
+ principalId + "&permission-id=" + permissionId);
}
Most of the information you want to display about a meeting comes from sco-info:
https://example.com/api/xml?action=sco-info&sco-id=2006334909
The response has many values that you can display, for example:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<sco account-id="624520" disabled="" display-seq="0"
folder-id="2006258747" icon="producer" lang="en" max-retries=""
sco-id="2006334909" source-sco-id="" type="content" version="1">
<date-created>2006-05-11T12:00:02.000-07:00</date-created>
<date-modified>2006-05-16T15:22:25.703-07:00</date-modified>
<name>Test Quiz</name>
<url-path>/quiz/</url-path>
<passing-score>10</passing-score>
<duration>15100.0</duration>
<section-count>6</section-count>
</sco>
</results>
https://example.com/api/xml?action=sco-info&sco-id=2006258750
https://example.com/api/xml?action=sco-shortcuts
Extract the url-path from the sco-info response. Then, extract the domain-name from the sco-shortcuts
response and concatenate the two values:
<?xml version="1.0" encoding="utf-8" ?>
<results>
<status code="ok" />
<shortcuts>
<sco tree-id="4930295" sco-id="2006258748" type="my-courses">
<domain-name>http://example.com</domain-name>
</sco>
..
You can also use a single call to report-my-meetings if the user is logged in and the meeting is in the user’s my-
meetings folder:
https://example.com/api/xml?action=report-my-meetings
In this case, extract both the domain-name and url-path from the report-my-meetings response.
The scoUrl Java method constructs the URL by calling sco-info to retrieve the url-path and then sco-shortcuts
to retrieve the domain-name. In this case, two calls are used so that you do not need to make the assumption that the
meeting is in the current user’s my-meetings folder:
public String scoUrl(String scoId) throws XMLApiException {
try {
Element e = request("sco-info", "sco-id=" + scoId);
if(!(codePath.valueOf(e).equalsIgnoreCase("ok")))
return "";
XPath xpath = XPath.newInstance("//url-path/text()");
String path = ((Text) xpath.selectSingleNode(e)).getText();
e = request("sco-shortcuts", null);
xpath = XPath.newInstance("//domain-name/text()");
String url = ((Text) xpath.selectSingleNode(e)).getText();