Update contact data connections
POST/v1/contacts/data/mappings
Links your firm's contacts to CRM contact records, and returns the contact data connections as Get the contact data connections returns them. The request body is keyed by CRM; each value maps a contact ID to the ID of the CRM record to link it to. For each CRM you send, your firm's contacts that you leave out are unlinked from that CRM; CRMs you leave out do not change. A contact you link to a Wealthbox or Redtail record takes the details of that record, such as its name and contact information; a Wealthbox or Redtail record ID that the CRM does not return unlinks the contact from that CRM. A negative contact ID, such as -1, creates a contact from the CRM record; in Slant, only from a professional contact. To link a contact to a Slant person, link the contact's household to the Slant household of that person first; see Update household data connections. A Slant record can be linked to one contact only. A Slant record that is linked to a different contact is refused with 409, unless that contact is an archived contact of your firm: then the record moves to the contact you link it to. When the other contact is an active contact of your firm, details.held gives its ID and name: remove that link, then link the record again. Nothing is written to the CRMs.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 429
The contact data connections after the change.
The request body is invalid, for example wealthbox, redtail or slant is not an object whose values are integers or strings, a negative key is linked to a Slant person, or a contact is linked to a Slant person while its household is not linked to Slant.
The access token is missing, invalid, or expired.
The access token does not have the write:household scope or the write:crm scope.
The request would link a Slant record to two contacts, link a Slant record that a different contact holds, or link a contact to a Slant person who is not in the Slant household that the contact's household is linked to.
Too many requests. Wait the number of seconds in the Retry-After-per-person header (script-audience tokens) or the Retry-After header (other requests) before you retry. See Rate limit.