Open Forum

We have an email verification app that enforces people to verify and confirm their email addresses before proceeding with event registrations on the CVENT site.

The user receives the code via provided email address and then passes in the verification page. Once this is confirmed, the app uses secure HTTP POST CVENT feature to send user's data to CVENT.

This works fine. However, now we want to implement different verification links for different registration types.

Here are examples of the flow:

• An exhibitor receives a link A to the verification app. After the verification they are redirected to full CVENT registration page of the "exhibitor" registration type
• A sponsor receives a link B to the verification app. After the verification they are redirected to full CVENT registration page of the "sponsor" registration type
• Everyone else receives a generic link C to the verification app. After the verification they are redirected to full CVENT registration page of the "industry" registration type.

We've tried experimenting with different HTTP POST fields according to https://developers.cvent.com/docs/http-post/reference/fields but none of them solve this problem.

We've also tried to use REST API to create contact record in CVENT, create/update attendee for the specific event with the appropriate "registrationPath", and then submit HTTP POST. Some tries it worked until the HTTP POST was send and the user was redirected. After that, this information was cleared from the record. Other times even API requests with correct registration path or type didn't populate these fields.

Does anyone have any idea how to ensure that attendees end up having a specific registration type in CVENT after our email validation process finishes?

#Registration

------------------------------
Dawid Czarnecki
Cybersecurity Specialist
Zigrin Security
------------------------------

Hi Dawid!

Is your event public or private? If private, you should be able to utilize the reg path Privacy Settings for who can register for the event to 'only those on certain invitation lists'. This should automatically redirect attendees to the correct path. Paired with the 'assign registration type to list members who register' feature in the invitation list settings, this would achieve the goal. If I am using this method, I typically set the first page of registration as only the identity confirmation information universally needed so that when the click next and the system recognizes them, they don't have to then go back and fill in additional information on the page before clicking next again.

If public, have you tried assigning registration types via custom logic? This is found under Advanced Settings in the registration path settings. Similarly to the above, you'd want to place your identifying criteria on the first page of registration.

------------------------------
Kristen Braswell
Event Technology Manager
Global Business Services
------------------------------

Hi Kristen,

Thank you for your reply. The event is public. I didn't know about the custom logic in Advanced Settings of registration path settings.

However, we managed to find a different solution. It turns out, the "reg_code" field of the HTTP POST can be provided with the registration type and this will automatically assign the person to the right registration type and direct to the registration path associated with this registration type.

Thank you once again for the support!

------------------------------
Dawid Czarnecki
Cybersecurity Specialist
Zigrin Security
------------------------------

Original Message:
Sent: 11-05-2025 10:33
From: Kristen Braswell
Subject: HTTP POST for different registration types

Hi Dawid!

Is your event public or private? If private, you should be able to utilize the reg path Privacy Settings for who can register for the event to 'only those on certain invitation lists'. This should automatically redirect attendees to the correct path. Paired with the 'assign registration type to list members who register' feature in the invitation list settings, this would achieve the goal. If I am using this method, I typically set the first page of registration as only the identity confirmation information universally needed so that when the click next and the system recognizes them, they don't have to then go back and fill in additional information on the page before clicking next again.

If public, have you tried assigning registration types via custom logic? This is found under Advanced Settings in the registration path settings. Similarly to the above, you'd want to place your identifying criteria on the first page of registration.

------------------------------
Kristen Braswell
Event Technology Manager
Global Business Services
------------------------------