Start Sessions with External Keys (TicketID)
The external key is a text string sent to the Bomgar Appliance to be logged as a property of a particular support session. This key typically originates from software separate from the Bomgar software. It does not need to be a unique value but usually is. The external key can be specified in one of two ways.
The support representative who has ownership of a Bomgar session can manually assign a key value from within the representative console. The summary pane of a session displays that session’s external key. Click the Edit External Key button to modify this value.
The second, more useful way of designating an external key is from within the URL sent to the Bomgar Appliance by the customer client. The external key can be specified with any of the session start methods documented above, as well as with the generate_session_key command detailed below.
The issue submission survey generates an HTTP request similar in format to the following example:
Note: The external_key parameter has been deprecated as of 14.2 and has been replaced with session.custom.external_key. However it is still available for backward compatibility.
The API allows creation of a custom web site or application that can be used instead of the public site to establish a support session. Code within this custom software must generate HTTP requests in the format displayed in the example above to initiate the session and pre-populate the external key within the representative console.
Using the External Key
Once a support session has an external key associated with it, you can use the reporting API to generate XML session data containing the external key. This provides the means for middleware to be developed to provide a relationship between the reporting data used by Bomgar and the correlating ticketing system’s ticket numbers.