Hi Dave, Have updated that example URL provided in the previous PM. It now includes: 1. Link to a txt file of the JSON payload returned from CTCT with GET request. 2. Link to a text file of the JSON payload submitted back to CTCT with the PUT request for each Contact. 3. A display of the ColdFusion source code for the page - with extensive comments detailing each step. 4. Output of orginal Contact data and updated Contact data after PUT requests. As you will see, we only submit via PUT the following JSON elements for each Contact: - Status - Email_address - Lists - Custom_fields We don't submit any other Contact meta data JSON elements (address, city, state, etc.) with the PUT request and the API does not alter those values - contrary to the API documentation. The API is actually acting like a POST request for almost all data elements, it doesn't for the JSON Lists & Status values. If Lists are not submitted, it removes the Contact from all assigned Lists. If Status is not submitted, it changes to Contact from Active. This is all intended for the final goal of using the new CustomField naming feature in the new Contacts Management system. Specifically enabling us to create and use our own unique custom fields and not worry about conflicts with any existing data in the default CustomField(1-15) fields. Is there any status updates on the new customfield naming feature? Thanks, Brad
... View more
