Hi gwomacks ,
Please log a case via the link that Sean_DC replied with, that will make sure our API support team get you a full response.
That said, I was just able to achieve associating contacts by sending a new DefaultCompanyID through using the format:
"defaultcompanyid": {
"companytype": 1,
"accno": 17
},
Exact packet, using the Motopartz demo data:
{
"jobtitle": "Sales",
"firstname": "Phillip",
"lastname": " Ball",
"fullname": "Phillip Ball",
"directphonenumber": "02 8486 0620",
"mobilephonenumber": "0405 271 460",
"email": "digital@benefitz.example.com",
"postaladdress": {
"line1": "PO BOX 33-1630",
"line2": "NORTH SYDNEY",
"line3": "NSW 2009",
"line4": null,
"line5": null
},
"postalcode": "",
"deliveryaddress": {
"line1": "BENEFITZ ADVERTISING AND GRAPH",
"line2": "46A ALFREDS RD",
"line3": "NORTH SYDNEY",
"line4": "NSW 2009",
"line5": null,
"line6": null
},
"advertsourceid": 0,
"active": true,
"optoutemarketing": false,
"salespersonid": 0,
"defaultcompanyid": {
"companytype": 1,
"accno": 17
},
"extrafields": [],
"id": 100
}
I sent this to the endpoint:
ENVIRONMENT/contact/100/
As a PUT request, and it reassociated the contact. Note the important parts are:
companytype must be specified (1 Debtor, 2 Creditor, 3 Prospect)
accno must be specified.
When using this method, the existing association is removed, so it is not possible to use the API to register a contact simultaneously against multiple accounts at this time. If this feature was needed I'd talk to the implementation partner about adding a custom endpoint with a trigger so you can add the logic required to suit your client.