Below you will see the values that will change after accessing the Cvent Passkey environment. These values should always remain configurable within the third party application:

• PartnerID: This is a unique number assigned to each third party organization with a certified Event Connector OpenAPI integration and identifies the system to Cvent Passkey. Upon successful certification, a production Partner ID is provided. Example: 136260
• username: This is the test API username utilized for all testing and certification within the Cvent Passkey testing environment. Example: reglinkapi
  Note

  This user account cannot be used to access the application. Upon successful certification, a production username and password is provided associated with the Partner ID noted above.

• OP: This is the operation of the message or call. This is the same for both the Cvent Passkey test and production environments and is based on the call being made. Example: CreateBridgeHTTP
• Service: This item is used in the Web Service/XML messaging. Refer to the samples provided for detailed requirements. Example: ModifyBridge
• GUID: Unique ID for Request. This ID is provided by the third party system to uniquely identify the request being sent. This ID is maintained in the response for tracking purposes.
• Version: As feature sets are expanded and new enhancements released, updated message versions may be released. Supported message versions will be consistent between the test and production environments based on the call being made. Specific features are tied to a specific version number. Versions are backwards compatible unless otherwise noted. Example: 4.00.02

• Token: The token element should be an empty tag wherever it is noted. Applications, like XML Spy, will convert empty tags <Token> </Token> to <Token/>. Messages received by Cvent Passkey must contain the token element as: <Token> </Token>.

• Destination: This item must be used in each message as defined in the samples provided within this guide.
• Locale: Cvent Passkey currently supports the following locales/languages:

Alternatively, attendees may have the option to set his/her language preferences within Cvent Passkey during the booking process based upon the locales enabled by the event owner/organizer. As Cvent Passkey extends its language support, this feature will be expanded.