OpCode T: Create a Login Ticket for the specified User

This opcode is used to create a login authorization ticket that is valid for one (1) minute. This ticket token can then be returned to the client browser with a specific redirect URL, allowing the client to launch the show without having to transmit the API credentials to their browser. The redirect should be temporary (HTTP 302) to the URL described below. Both attendees (default) and exhibitor users can be specified. The user must already exist. If LookupByExternalUserID is specified as one (1), then the user is located based on the ExternalUserID value. Otherwise, the user is located based on EMailAddress. Several conditions would prevent successful login ticket creation, such as the user’s account being inactive or the user not being registered for the show.

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!50500&APIUserAuthCode={YourAuthCode}&APIUserCredentials={YourCredentials}&OpCodeList={Opcode[OpCode[…]]}&OutputFormat={X|H|T(default)}&LookupByExternalUserID={0(default)|1}&{Additional, opcode-specific parameters in name=value format…}

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!50500. All other parameters may appear in any sequence.

Return Outputs

This API returns the status message OK upon successful completion, as well as the LoginTicketKey value to be used when constructing the redirect URL.

Text

### APICallResult=0 APICallDiagnostic=OK OpCodesProcessed=1 OpCodesInError=0

## OpCode=T Status=0 Message=OK

LoginTicketKey

12345

HTTP URL-encoded

APICallResult=0&APICallDiagnostic=OK&OpCodesProcessed=1&OpCodesInError=0&OpCode=I&Status=0&Message=OK&LoginTicketKey=12345

XML

<?xml version="1.0" encoding="utf-8" ?>

<APIResults APICallResult="0" APICallDiagnostic="OK" OpCodesProcessed="1" OpCodesInError=”0” >

<OpCodeResult OpCode="T" Status="0" Message="OK" >

 <ResultRow>

  <LoginTicketKey>2574F936-DD4B-4451-A8A5-F420C03E5306</LoginTicketKey>

  <RecipientKey>123456</RecipientKey>

 </ResultRow>

</OpCodeResult>

</APIResults>

After retrieving the LoginTicketKey value, the redirect URL can be constructed as follows:

https://onlinexperiences.com/scripts/Server.nxp?LASCmd=AI:4;F:APIUTILS!50505&LoginTicketKey={value}

The tag {value} is replaced with the LoginTicketKey value returned from the API call. Note the difference in domain name in the redirect link (onlinexperiences.com vs api.onlinexperiences.com).

Potential Error Codes