Response objects

The response objects are:

conf_settings response object

conf_repetition response object

conf_participant response object

occur_settings response object

conf_dial_info response object

location response object

user response object

breeze response object

line response object

integration response object

Response objects for managing conferences

conf_settings response object

The structure of the response object is identical to conf_settings request object .

conf_repetition response object

The structure of the response object is identical to conf_repetition request object .

conf_participant response object

The structure of the response object is identical to conf_participant request object.

occur_settings response object

The structure of the response object is identical to occur_settings request object .

conf_dial_info response object

{ 
"dial_starleaf": <string>,
"pstn_numbers": [<conf_pstn_number object>, 
	<conf_pstn_number object: optional>, 
	...], 
"access_code_pstn": <string>, 
"dial_info_url": <string>, 
"dial_standards": <string>, 
"breeze_link": <string>, 
"lync_link": <string>, 
"webrtc_link": <string> 
"sign_up_link": <string>
} 

Field	Description
dial_starleaf	The string to dial to join the conference using a StarLeaf endpoint.
pstn_numbers	An array of one or more conf_pstn_number objects, each of which provides a public switched telephone network (PSTN) number for a different geographic location. Any of these numbers may be dialed to join the conference. Participants dialing in using this method will be prompted to enter an access code.
access_code_pstn	The access code required by participants that dial in from the PSTN.
dial_info_url	A URL to a web page providing all the relevant dialing information in a user readable format.
dial_standards	The sequence to dial to join the conference using a standards based (H.323 or SIP) endpoint.
breeze_link	A link for use on devices that have the StarLeaf Breeze soft client installed.
lync_link	A link for use on devices that have Microsoft Skype-for-Business installed. Note that this value will be null if Skype-for-Business is not enabled for the client in the StarLeaf Cloud.
webrtc_link	A Click-to-Call link for joining the conference using a web browser. Note that this value will be null if WebRTC is not enabled for the client in the StarLeaf Cloud.
sign_up_link	A URL to a web page that allows someone to sign up to the StarLeaf Cloud service and download a software video client.

Response objects for managing customers

location response object

The structure of the response object is identical to location request object.

Response objects for managing users

user response object

{
  "user_id": <string>, 
  "firstname":<string>,
  "lastname":<string>,
  "email":<string>,
  "is_org_admin":<boolean>,
  "send_emails":<boolean>,
  "enable_vvm":<boolean>,
  "timezone":<string or null>,
  "locale":<string or null>,
  "phone_home":<string or null>,
  "phone_work":<string or null>,
  "phone_mobile":<string or null>, 
  "line": <line response object>,
  "breeze": <breeze response object>
}

Field	Description
user_id	The unique identifier for this user within the organization.
firstname	First name of the new user.
lastname	Last name of the new user.
email	Email address of the new user.
is_org_admin	Boolean to specify if whether this user has admin privileges.
send_emails	Boolean to specify whether to send account-settings emails.
enable_vvm	Boolean to turn off/on video voicemail for this user.
timezone	If the user is in a different timezone to the default timezone for the organization, this is the name of the user’s time zone, as per the IANA Time Zone Database.
locale	If the user uses a different language to the default language of the organization, this is the code for that language. The language will be used for emails to the user and for the user interface language for Breeze, desktop system and user Portal pages. The locale is also used to determine the format of any display of date and time. For a list of valid locale codes, refer to Locales.
phone_home	The user’s home telephone number.
phone_work	Another contact telephone number for the user.
phone_mobile	A mobile phone number for the user.
line	Settings for the line— refer to line response object.
breeze	Setting for the breeze software client—refer to breeze response object.

breeze response object

{
"enabled":<boolean: optional, default: true>,
 }

Field	Description
enabled	Boolean specifying if Breeze is enabled or not for this user.

line response object

line is an object that appears in the response to a create or modify user request.

{
    "alias":<string>,
    "alias_autocomplete": <boolean>,
    "number":<string>
}

Field	Description
alias	The first part of the user’s external video address. That is, the part before the @ sign. To create the full dialing URI for a user, use the format: <alias>@<organization_subdomain>.call.sl
alias_autocomplete	Whether or not this user’s external video address was automatically created by the Cloud. If false, this external video address has been created or edited through the StarLeaf Portal. If true and you edit an existing user’s email address, the Cloud might auto-update the user’s alias. If false and you edit an existing user’s email address, the Cloud will not auto-update the user’s alias.
number	The directory number of this user.

Response objects for managing integrations

integration response object

{ 
  "label": <string>,
  "type": <string>,
  "id"; <string>,
  "token_header_name": <string>,
  "access_token": <string>,
  "is_org_admin": <boolean> 
} 	

Field	Description
label	The name given to the integration.
type	The type of integration. Currently, the only supported type is “custom”.
id	A unique identifier for this integration.
token_header_name	The name of the HTTP header that the integration client must use for authentication.
access_token	The value of the HTTP header that the integration client must use for authentication. This is a unique token for this integration. Note, it is worth remembering that this access token provides login access to the organization. Therefore, keep it secret. If you do want to regenerate the access token for an integration, you can do so using a PATCH request for the integration. For more information, refer to the relevant section of Org admin requests or Reseller requests.
is_org_admin	Whether or not the integration has administrator access to this organization.