Update to SOAP API’s GetUpdated and Retrieve Calls (12/1/2022)

We’ve updated SOAP API‘s Get Updated and Retrieve calls.

What’s Changing?

Changes to some Cvent objects take, on average, under a minute before they are available in a Retrieve call. The following objects have a delay:

• Contact
• Event
• Registration

Changes to all Cvent objects take, on average, under a minute before they are available in a GetUpdated call.

Upcoming SOAP API Security Updates (3/4/2022)

On April 5, new security headers will be added to all HTTPS responses from Cvent’s SOAP API. No interruption is expected. However, customers are advised to review their applications to ensure that they are not rejecting responses with these headers.

The new headers are :

• Cache-Control: no-cache, no-store, must-revalidate
• Strict-Transport-Security: max-age=63072000; includeSubDomains; preload

Customers are advised to use HTTPS going forward, and future support for HTTP will be deprecated at the end of 2022.

More information about these changes can be found here: https://https.cio.gov/hsts/

Change to SOAP API Call Logging (3/2/2022)

On February 24th, 2022, SOAP API call logging changed.

What changed?

SOAP API call logging is no longer on by default in all Cvent accounts. Cvent will only log login calls and calls that encounter exceptions.

Accounts that have run the API History report in the last six months are exempt from this change and continue to log all calls.

How can I have call logging turned on?

If you’d like to enable call logging in your account to help with troubleshooting, contact your account team or reach out to Cvent support.

Upcoming Update to Cvent’s WSDL File (1/26/2022)

On February 8th, an update will be made to Cvent’s WSDL file which may require you to update your WSDL file to the newest version (which can be found at https://api.cvent.com/soap/V200611.ASMX?WSDL) on that date.

What is changing? And, why?

A new field is being introduced in the CopyEvent and CreateNoRegEvent call to add support for Hybrid and Virtual event creation. The new field is:

EventAttendanceFormat

The field has 3 possible values: In-Person Virtual Hybrid

What calls will be affected?

If your integration with Cvent makes use of the following API call, you may need to update your WSDL file to accommodate for this change:

CopyEvent CreateNoRegEvent DescribeCVObject

Upcoming Update to Cvent’s WSDL File [Postponed] (10/29/2021)

Update from November 18th – this release has been postponed until further notice

On November 20th, an update will be made to Cvent’s WSDL file which may require you to update your WSDL file to the newest version (which can be found at https://api.cvent.com/soap/V200611.ASMX?WSDL) on that date.

What is changing? And, why?

A new field is being introduced in the CopyEvent and CreateNoRegEvent call to add support for Hybrid and Virtual event creation. The new field is:

EventAttendanceFormat

The field has 3 possible values:

• 0 – In-Person
• 1 – Virtual
• 2 - Hybrid

What calls will be affected?

If your integration with Cvent makes use of the following API call, you may need to update your WSDL file to accommodate for this change:

CopyEvent CreateNoRegEvent

Upcoming Update to Cvent’s WSDL File (5/25/2021)

On Wednesday June 9th, an update will be made to Cvent’s WSDL file which may require you to update your WSDL file to the newest version on that date. If you are using a locally installed WSDL file, you may need to update it with the new one

The current version of the WSDL file can be found here: https://api.cvent.com/soap/V200611.ASMX?WSDL

What is changing? And, why?

This update will allow planners to retrieve the new Air Actual fields available in Flex events. The new fields are:

Journey Type – One Way or Round Trip

Journey Segment – Going to Event or Leaving Event

What calls will be affected?

If your integration with Cvent makes use of the following API call, you may need to update your WSDL file to accommodate for this change:

– Retrieve AirActuals

Please note that this update will not require any changes to your code, only an update to the WSDL file that you are utilizing.

Upcoming Update to Cvent’s WSDL File [Updated] (4/5/2021)

On April 19th, we’ll be making an update to Cvent’s WSDL file. This may require you to update your WSDL file to the newest version.

What’s changing and why?

This update will enable planner to submit and retrieve “Meeting Requests” in different supporting languages, Planner need to add a valid LocaleCode while Create and Update Meeting Requests in the different languages.

The DescribeGlobal API call will also return the list of Locale’s available.

What calls will be affected?

If your integration with Cvent uses any of the following API calls, you may need to update your WSDL file to accommodate this change:

Name of API call- CreateMeetingRequest

Object Type- MeetingRequest

Name of API call- UpdateMeetingRequest

Object Type- MeetingRequest

Name of API call- DescribeGlobal

Object Type- DescribeGlobalResult.LookUp

If you’re using this object, then this update may require changes to your code. For further questions about the impact of this change, please reach out to Client Services.

** The release date was previously incorrect (November 4) and has been updated to April 19th 2021

Upcoming Update to Cvent’s WSDL File (10/21/2019)

On November 4th at 3:00 AM EST, we’ll be making an update to Cvent’s WSDL file. This may require you to update your WSDL file to the newest version.

What’s changing and why?

This update will enhance the security of invitee responses to the “Handicap” field. Users must now have the “Secure Reporting Fields” permission in order to view this field.

Going forward, only account administrators and users who have access to the permission can view these responses via SOAP calls or in reports.

As part of this change, we’ll also change the data type of the “Handicap” field from Boolean to String.

What calls will be affected?

If your integration with Cvent uses any of the following API calls, you may need to update your WSDL file to accommodate this change:

Object: Travel

Call: Retrieve

If you’re using this object, then this update may require changes to your code. For further questions about the impact of this change, please reach out to Client Services.

SOAP API WSDL Update (7/13/2018)

On July 13, 2018, an update was made to Cvent’s SOAP API calls which may require you to download the newest version of the WSDL file. This update was made to comply with General Protection Data Regulation (GPDR) “right to be forgotten”. Cvent will perform obfuscation to anonymize a person’s record when a “right to be forgotten” request is submitted. When a request is received, Cvent will mask the contact’s information and flag them as obfuscated.

What is changing and why?

Contacts/invitees and guests can be obfuscated from Cvent’s Address Book. This update will add a new “isobfuscated” flag to the Contact and Guest objects and the field will be read-only and searchable.

What calls will be affected?

• Create Contact: No change. The value for “isobfuscated” field will not impact the contact creation. Any new contact created will be saved with this value as false.
• Update Contact/Upsert Contact: This will not let users update the contacts that have already been obfuscated. If a user tries, the output will return an error message, “Obfuscated contacts cannot be updated. New error code for this: CV40127.”
• UpdateGuestInfo: This will not let users update any guests that have already been obfuscated.
• Retrieve: This will return the value for contact fields based on whether the contact is obfuscated or not.
• Describecvobject: This will return the object with the field type for the “isobfuscated” field.
  Note

  Updates will require changes to Cvent’s WSDL file.

The “isobfuscated” flag will be “true” for any record that has been anonymized as a result of a “right to be forgotten” request and “false” for all other contacts/invitees and guests. As part of “right to be forgotten,” clients/planners can request Cvent to forget any of their invitees from Cvent.

Cvent SOAP API Updates (4/19/2018)

On May 4, 2018, an update will be made to Cvent’s SOAP API calls. However, it won’t require you to update your WSDL file on that date.

What is changing? And, why?

To ensure all our customers are GDPR compliant we are adding a new consent type custom field to Contact Custom Fields. However, since the new field type will have some additional properties we won’t be able to create or update these custom fields using the SOAP API calls.

What calls will be affected?

• Create Custom Field: No change – the consent type option won’t be available while creating new contact custom fields.
• Update Custom Field: The update call won’t make any changes to the Consent Custom Fields. If we try to update this field, the output will return an error message.
• Retrieve Custom Field: No change – The retrieve call will allow users to retrieve all custom fields including the consent field.