UDF API

Notified provides a portal to virtual event integration feature that enables partners and show hosts to launch the Virtual Trade Show (VTS) platform on-demand using single sign-on and password controls through their controlled sites and systems. For visitors, they only need to log in once at the host site. Their login information is then automatically sent to the virtual event.

Several different VTS modules may be launched, including the Show module, the Remote Profile Update, the Booth Builder, and the Show Data Portal. This allows partners to fully integrate the VTS platform as a module of their site systems.

The Notified Virtual Trade Show External API also provides third-party partners the ability to programmatically automate the creation and synchronization of shared users and user attributes between their systems and the VTS database. This automation is controlled and orchestrated by the caller. The VTS platform does not currently push calls to third-party systems.

Calling the API

The API is called via a secure HTTPS request. This HTTPS request may be a GET or POST operation. Each request must supply the authentication credentials assigned to the caller by Notified. Only requests with valid credentials will be processed. These credentials identify the caller and provide access only to a specific customer area.

The format of the call is: 

https://api.onlinexperiences.com/scripts/Server.nxp?LASCmd=AI:4;F:APIUTILS!50566
&APIUserAuthCode={YourAuthCode}
&APIUserCredentials={YourCredentials}
&ShowKey={ShowKey}
&FromDateTime={FromDate in YYYY-MM-DD HH:MM:SS format}
&ToDateTime={ToDate in YYYY-MM-DD HH:MM:SS format}
&ActivityTypeFilter={filter code list, in |OPTION|OPTION| format…}
&FilterUserType={0|1|-1 where 0 = attendees, 1 = exhibitors, -1 = both}

Note: The format of the APAC Data Center is: https://api.apac.onlinexperiences.com.

Specific parameter ordering is unimportant, with the only restriction being that the first parameter MUST BE LASCmd=AI:4;F:APIUTILS!50507. All other parameters may appear in any sequence.

OpCodes

API operations to be performed are specified in the OpCode parameter. More than one opcode may be specified, allowing the caller to perform multiple steps for each UDF. Opcodes are evaluated in order from left to right. Each opcode requires a different set of parameters to be supplied. Parameter values may be shared among multiple opcodes. Following is a list of valid opcodes supported by the API:

For each opcode, the specific parameters accepted and return output are documented individually, including potential errors that may occur specific to each opcode.

Example API Call

The following example call retrieves the list of UDF information with a Source of 1 in XML format:

https://api.onlinexperiences.com/scripts/Server.nxp?LASCmd=AI:4;F:APIUTILS!50507&APIUserAuthCode=JX11452B&APIUserCredentials=DEMO01&OpCodeList=UDL&OutputFormat=X&Source=1

Before the API begins processing opcodes, certain credential and parameter validations are made. If any of these top-level validations fail, none of the opcodes will be processed. Below is a listing of potential top-level validation errors:

Potential Error Codes

Retrieving Results From The API

The API can return results in several formats, allowing the developer to choose what is most easily consumed. The formats are text-based, HTTP URL-encoded, XML, and JSON. Results contain a header, indicating the overall success of the call, including textual diagnostic, the number of opcodes successfully processed, and the number of opcodes that resulted in an error. Each opcode then outputs a recap section of its execution, indicating the opcode, processing result, and textual diagnostic. Error codes of 0 indicate success (no error).

In addition to the opcode recap, data elements are output for each opcode indicating the return values of the operation. The format of the results depends on the result format requested. For URL-encoded, these are listed as a string of HTTP parameter names and values. They are listed as a header line for text, followed by a values line, each field separated by commas. For XML and JSON, they are listed as child nodes of the opcode response. Example output is included for each opcode in the respective opcode’s documentation.