Update household data connections
POST/v1/households/data/mappings
Links your firm's households to CRM household records, and returns the household data connections as Get the household data connections returns them. The request body is keyed by CRM; each value maps a household ID to the ID of the CRM record to link it to. For each CRM you send, your firm's households that you leave out are unlinked from that CRM; CRMs you leave out do not change. A household you link takes the name of its CRM record. A negative household ID, such as -1, creates a household from the CRM record; to see it, call Get the household data connections. A household can be linked to one CRM only, and a Slant household record to one household only. Nothing is written to the CRMs.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 429
The household data connections after the change.
The request body is invalid, for example a key is not wealthbox, redtail or slant, a household ID is not a whole number, or a Wealthbox or Redtail record ID is not a whole number.
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 household to two CRMs, or a Slant household record to two households, or a negative key would create a contact for a Slant person whose record a different contact holds, other than an archived contact of your firm. For an active contact of your firm, details.held gives its ID and name; remove that link, then send the request again. Nothing changes.
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.