Save Bloomerang constituent-to-donor mapping
Requires an organization donor form and available field pairs. Each canonical provider field may be used once (Name and FullName collide); an enabled relationship-manager custom field must be available and distinct. Requires a mapped field or enabled manager mapping. Saves historical-backfill protections and notification/outgoing suppression, creation/adoption choices and the next approved mapping without syncing. Creation requires outgoing ownership and explicit creation opt-in; omitted creation/manager enablement is false, omitted email-match/backfill choices preserve stored state. Direction follows sync_direction_control: configurable uses requested/current/default direction, locked_bidirectional forces bidirectional, and unavailable preserves current/default direction. Defaults are bidirectional. Returned context/mapping shows effective flags; saving direction and activating ongoing sync are separate. Requires the integration platform global/configured client feature gate (normally integration_platform_foundation). Requires permission: one of access_account_settings.
Authorizations
Passport bearer token authentication for legacy admin sessions.
Path Parameters
Connection id in the current organization.
Body
Validated request fields for this operation.
Hysform id. Validation: required, integer.
1
Field mappings. Validation: required, array.
Source of truth. Validation: nullable; allowed values: provider, hys, bidirectional.
provider, hys, bidirectional, null "provider"
Allow email match. Validation: nullable, boolean.
true
Historical backfill mode. Validation: nullable, boolean.
true
Allow bloomerang constituent creation. Validation: nullable, boolean.
true
Allow same email constituent retry adoption. Validation: nullable, boolean.
true
Relationship manager sync enabled. Validation: nullable, boolean.
true
Relationship manager field path. Validation: nullable, string, max:191.
191"Relationship Manager Field Path"