POST contact_information/accept_consent
Available from CRM.COM R14.1.0
This method is used so that Contacts can accept Consent, providing an attachment on the Contact (optionally) representing the Consent Form. This Web API method requires a multipart/form-data post, as defined in RFC 1867. There are many libraries available that can be used in order to submit multipart/form-data posts (for example MultipartEntity in Java). A single attachment can be added through each call
Resource URL
Parameters
Name | Type | Description | |||||||||||||||||||||
token | String | The token retrieved from the login method | |||||||||||||||||||||
contact_information_identifier (mandatory) | Contact Information Identifier | The identifier of the contact information that should be updated. The allowed contact information identifier fields are the following:
| |||||||||||||||||||||
attachment_id (optional) | String | The ID of the attachment that should be added as the consent form on the Contact (applicable if a file is not provided). The attachment should already exist in the system's Attachments Library
| |||||||||||||||||||||
file (optional) | File | The file that should be added as an attachment (applicable if attachment_id was not provided) | |||||||||||||||||||||
fields_set | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
Restrictions
- It is mandatory to specify one of the semi-optional parameters. Only one of those parameters is allowed to be specified.
Response Data
Examples