Cloud Elements Version 2.172-2.176
We added the POST /contacts/{contactId}/merge
endpoint so you can merge two or more known lead records into a single lead record. Merging does not overwrite existing information, but adds information where none already exists. The "merge to" record identified in the path becomes the single record for the contact (lead), while Marketo deletes the "merge from" record.
Pass the leadID
of the contact to merge information into as part of the request, for example POST /contacts/350/merge
. Include the leadID
of the contact to merge information from in the body of the request. You can include a single lead record ("leadId": "355"
) or multiple records in a comma-separated list ("leadIds": "355,466"
).
Your body should include either a singe leadId
or a comma-separated list of leadIds
. Optionaly include "mergeInCRM": "true"
to attempt to merge the designated records in a natively-synched CRM. This is valid only for instances with are natively synched to Salesforce.
In this example we're merging the information from leadID 351 into 350.
curl -X POST "https://api.cloud-elements.com/elements/api-v2/hubs/marketing/contacts/350/merge" -H "accept: application/json" -H "Authorization: User xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Organization xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc, Element xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -H "content-type: application/json" -d "{ \"leadId\": \"351\", \"mergeInCRM\": true}"
/file/comments
endpointsWe added the following comments endpoints to the /files resource:
When setting up events in Intacct you can now include a Callback Notification Signature Key.
When setting up events in Intacct. you can now include a Callback Notification Signature Key.
You can now specify the fields to include in GET responses. Supported requests include:
Changes to formulas now appear in the audit logs.