Update an association

put

https://{youraccountname}.api-us1.com/api/3/accountContacts/{id}

Changes a link. Send only the fields to change; the others keep their values. Changing account moves the contact to that account. Saving a link also sets the contact's account (orgid and orgname on the contact) and can start automations that run when a contact's account changes. Changing contact does not clear orgid and orgname on the contact that was linked before. Needs permission to edit contacts. PATCH /accountContacts/{id} does the same thing.

Please note that we currently allow single account per contact.

{
	"accountContact": {
		"jobTitle": "Product Manager"
	}
}

{
    "accountContact": {
        "account": "3",
        "contact": "2",
        "jobTitle": "CEO",
        "createdTimestamp": "2019-06-26T11:26:15-05:00",
        "updatedTimestamp": "2019-06-26T11:29:57-05:00",
        "links": {
            "account": "http://hosted.localdev/api/3/accountContacts/19/account",
            "contact": "http://hosted.localdev/api/3/accountContacts/19/contact"
        },
        "id": "19"
    }
}

Responses

200The link was changed. accounts holds the linked account.

400The body is a non-empty JSON list or a non-empty single value instead of an object. This is checked before anything else. An empty body is read as an empty object.

403The caller lacks permission to edit contacts. Nothing was changed.

404No link has this id.

422The changed link failed validation. Nothing was saved. Possible problems: account or contact was set to an empty value or to an id that does not exist; or contact was changed to a contact already linked to a different account, or already linked to this account (which gives both errors).