Integration Requirements List

We need the following information to submit an integration for development:

• Information from your third-party; see below
• Test accounts
  • Test Account Instructions
• For eventScribe Website and/or Mobile App - Registration/Access Grid
  • eventScribe - Registration & Access Grid Instructions

Please submit this information to integrationservices@gocadmium.com IN ITS ENTIRETY by the requirements deadline provided by your integration services project manager. An integration will not be submitted for development until ALL requirements have been received. Please DO NOT submit this information in pieces. 

If an integration has been grandfathered in for a vendor not listed below, request the requirements directly from your integration services project manager.

A2Z

We need the following for all integrations (repeat or new):

• A2z key 
• A2z install name 
• A2z event ID
• A2z username and password

ACGI - Association Anywhere

We need the following for all integrations (repeat or new):

• vendorEventID
• API Username and Password

If new, we also need:

• Customer Endpoint
• Authentication Endpoint
• Decrypt Endpoint

Aptify 

We need the following for all integrations (repeat or new):

• Meeting ID
• Endpoint URL

ATS Bridge

We need the following for all integrations (repeat or new):

• SSO URL

If new, we also need:

• API endpoint

CompuSystems (CSI)

We need the following for all integrations (repeat or new):

• EventCode 
• EventNumber

If new, we also need:

• API username and password

Conexsys

We need the following for all integrations (repeat or new):

• EndpointURL

If new, we also need:

• PublicAccessKey 
• AccessKey

Convention Data Services (CDS)

We need the following for all integrations (repeat or new):

• Authentication key

Fonteva

We need the following for all integrations (repeat or new):

• Client secret 
• Client ID 
• Token endpoint

If new, we also need:

• OAuth grantType

iMIS

We need the following for all integrations (repeat or new):

• Custom based on type of iMIS integration - ask your integration services project manager

If new, we also need:

• Client secret
• Client ID
• User Login Page URL

Map Your Show

We need the following for all integrations (repeat or new):

• Show code 
• List of booths to map (if applicable)

If new, we also need:

• Password

Maritz

We need the following for all integrations (repeat or new):

• EventShowCode 
• RTS access for Cadmium account (Ariyo’s account) 

NetForum (Enterprise Only)

We need the following for all integrations (repeat or new):

• API endpoint
• Event key

If new, we also need:

• API username and password 

Nimble

We need the following for all integrations (repeat or new):

• Client_ID 
• Client_Secret 
• Token endpoint 
• Authorization endpoint 
• User info endpoint 
• Nimble event key array

If new, we also need:

• Authentication key 
• User registration endpoint and payload

PARS

We need the following for all integrations (repeat or new):

• Credit Type (i.e. ABIM MOC, ABP MOC)
• Activity ID

If new, we also need:

• ParsSandboxUser
• ParsSandboxPassword
• ParsProductionUser
• ParsProductionPassword

Personify

We need the following for all integrations (repeat or new):

• PersonifySSOUrl 
• ServiceEndpointUrl 
• OdataServiceUrl
• RoleServiceUrl 
• EventCode 

If new, we also need:

• VendorUsername
• VendorPassword
• VendorID 
• VendorBlock 
• OdataUser 
• OdataPassword 

YourMembership

We need the following for all integrations (repeat or new):

• Session ID

If new, we also need:

• API key 
• API version