Usage

Use CreateMeetingRequest to add one meeting requests to your Cvent account. The CreateContact call is analogous to the INSERT statement in SQL.

Basic Steps

1. Create an instance of a single meeting request object, populating its fields with the data you want to add.
2. Construct a MeetingRequest array and populate that array with one meeting requests you want to create.
3. Optionally, specify the MessageId if you need to track the result of the record. Message IDs can represent unique identifiers from your system. These will be returned as Reference IDs in the result array for tracking purposes.
4. Call CreateMeetingRequest, passing in the MeetingRequest array.
5. Process the results in the CreateMeetingRequestResultArray object to verify whether the meeting request has been successfully created.

General Syntax

CreateMeetingRequestResultArray = cventapi.CreateMeetingRequest
(MeetingRequestArray)

Input

| Name | Type | Description | | ----------------------- | -------------- | ------------------------- ------------------------------------------------------------------ | | RequesterId | ID | ID of the user, used for applying visibility of the resulting meeting request form. | | MeetingRequestParameter | CvObject Array | Array of one meeting request to be created. Optional Message IDs, returned as Reference IDs. |

Output

| Name | Type | Description | | ----------- | ----------- | ---------------------------------------- ------------------------------- | | Id | ID Array | Request code of the meeting request that was created. If this field contains a value, then the action was successful. If the field is empty, then the meeting request was not created and instead returned an error. | | ReferenceId | ID | The Message ID value in the input CvObject. | | Success | Boolean | Indicates whether the Create call succeeded (True) or not (False) for this object. | | Errors | Error Array | If an error occurred during the Create call, an array of one or more Error objects providing the error code and description. |

Notes

• Timezone, state, and country codes are provided by the DescribeGlobal method. Use the corresponding codes returned in the “ID” attribute provided by the DescribeGlobal call.

Validations Rules

The following validation rules should be applied to the CreateMeetingRequest call:

| Validation Rule | Description | | --------------------- | --------------------------------------------

------------------ | | Format and Pattern | The ID field should be a valid GUID data type. | | Referential Integrity | The following relationships need to be valid to ensure database referential integrity: RequesterStateCode RequesterCountryCode EventStateCode EventCountryCode StakeholderStateCode StakeholderCountryCode | | Length | The application will truncate data which exceeds the maximum length of a field.| | Read-Only | The application will ignore the value in the read-only fields.|