Registration Integrations

This article explains the steps and Grip process for a Registration Integration Partner PUSHING data to Grip using the /thing/register endpoints that are part of the Grip Events API.

The following parties are involved within an Integration where the Integration Partner is expected to PUSH data to the Grip Matchmaking Solution.

Integration Partner: The company that holds the event data that need to be available within the Grip platform. This can, for example, be visitor data, exhibitor data or sessions that need to be displayed on the Event Program in the Grip Matchmaking Solution.
Grip Event Project Manager: The person responsible for the successful delivery of the Grip Matchmaking Solution for the Event Client.
Grip Integration Engineer: The internal engineer that will provide technical support to the Integration Partner and Grip Event Project Manager for any issues during the Integration.

The following steps are involved and should be taken one by one to achieve a successful, well-running integration between the Integration Partner and the Grip Matchmaking Solution.

Integration Partner shares a sample of the registration data is shared with Grip Event Project Manager for each data type that needs to be imported (Visitor, Exhibitor, Representative etc)
Grip Event Project Manager makes a mapping of what data needs to be imported as what field.
Grip Event Project Manager gives Integration Partner access to the Grip Dashboard.
1. The Integration Partner needs to specify who should receive access to the Grip Dashboard.
Integration Partner get its Token from the Grip Dashboard and posts a small sample (10-50 records of records) of the Registration Data.
Grip Event Project Manager reviews the Sample Data together with the Grip Integration Engineer and confirm the records have been imported correctly.
Integration Partner imports all records and switches to a live integration that automatically posts data.

Multi-Language Registration Data Example JSON

The Grip Matchmaking Solution supports a wide variety of languages that can be switched on and off for a particular application. As part of the initial configuration of an application, the Grip Event Project Manager will enable the correct languages. In the below example, the enabled languages are EN-GB and RU-RU for which multi-language and multi-value registration data is being imported.

{
   "type_id": 380,
   "default_container_id": 90001,
   "generate_relationships": 1,
   "new_event_join_type": "join_and_patch",
   "name": "Claudio Cadeddu",
   "first_name": "Claudio",
   "last_name": "Cadeddu",
   "job_title": "FOUNDER",
   "company_name": "Example.com Ltd",
   "headline": "Founder - Example.com Ltd",
   "summary": "Example.com Ltd is specialized in opera, music, cultural and sporting events in Italy and all over the world.- Example.com специализируется на опере, музыке, культурных и спортивных мероприятиях в Италии и во всем мире.",
   "email": "jou@example.com",
   "registration_id": "B23292",
   "location": "City, Country",
   "location_code": "en-GB",
   "metadata_raw": {
          "exhibitor_id": [{
                           "en-gb": "65322"
                           }
   ],
   "product_category_provided": 
	[{
		"en-gb": "Tour Operator",
		"ru-ru": "Туроператор"
	},{
		"en-gb": "Leisure",
		"ru-ru": "Многопрофильный"
	},{
		"en-gb": "Luxury travel",
		"ru-ru": "Эксклюзивный туризм"
	},{
		"en-gb": "Business & Incentive Travel",
		"ru-ru": "Деловой туризм"
	},{
		"en-gb": "Educational Tourism",
		"ru-ru": "Образование за рубежом"
	}
	]
 }
}

If you have access to the dashboard, make sure you take a look at the "Data & Language Management" page where you can see all the available fields as well as view logs of the recent registration data that has come in.

Note: Make sure not to use the word admin when creating Registration IDs. If we detect the word admin within any registration ID, we prevent any changes/updates to this profile.

Registration Integrations - API PUSH

Multi-Language Registration Data Example JSON