Plan Code
Policy Number
Submits the Coverage Joint Insured role change transaction for processing.
Generic Party Role Change endpoint, shared across all multi-party-update transactions (Payee, Trustee, Power of Attorney, Owner, Joint Owner, Authorized Signatory, Coverage Joint Insured, and future party roles using the same MultiPartyRoleChangeRequest/PartyUpdate request format).
Plan Code
Policy Number
Generic request body for a party role change transaction (pa-bpm-txn-common
MultiPartyRoleChangeRequest), shared across all multi-party-update
transactions (Payee, Trustee, Power of Attorney, Owner/Joint Owner,
Authorized Signatory, Coverage Joint Insured, and future party roles).
Each party role is exposed at its own dedicated path (see the
…/parties/{role}/… operations); this schema is the shared contract
across all of them.
Plan code (may duplicate path parameter)
Policy number (may duplicate path parameter)
Zinnia Live Case ID
Example:CA0000007389
The unique ID to track transaction request across all systems
Example:e3bdb22b-790f-4357-ae60-42cdb0ff0d12
Carrier identifier
Example:FNWL
Effective date for the party role change
Example:2026-07-24
Origin of the request
Allowed values:DATA_ENTRYSELF_SERVE
A single party change entry (pa-bpm-txn-common PartyUpdateDto). One
MultiPartyRoleChangeRequest carries a list of these - one per party being
added, updated, or removed in this transaction.
>= 1 items
Signature details for the agent change
Supporting document reference for a party role change
Whether the request originated from a self-serve flow
Example:true
Indicates whether supporting documents are attached
Example:true
Reason for the change
Submit Transaction Successful
Unique identifier which used by every system to trace the request
Example:3a2a3435-2089-4b81-9959-e0d569ccf4f0
Zinnia Live Case ID
Example:CA0000369469
Zinnia Live Case Status
Example:IN_PROGRESS
Identifier for the generated or associated PDF document (e.g. OnBase document number). Returned on systematic program setup and update submit when available.
Example:DOC-10004567
If freelook endDate is less than or equal to policy effective Date, cancel the policy based on the request
Policy Number
The unique ID to track transaction request across all systems
Example:657b717b7dcf554abf9ef067
Date (with pattern “yyyy-mm-dd”)
Match pattern:([0-9]{4})-([0-9]{2})-([0-9]{2})
Property to isolate source transaction(s) that initiated the reversal
Zinnia Live Case ID
Example:CA0000007389
Success
Unique identifier which used by every system to trace the request
Example:3a2a3435-2089-4b81-9959-e0d569ccf4f0
Zinnia Live Case ID
Example:CA0000369469
Zinnia Live Case Status
Example:IN_PROGRESS
Identifier for the generated or associated PDF document (e.g. OnBase document number). Returned on systematic program setup and update submit when available.
Example:DOC-10004567
Example:864e43a0-2c2f-4a11-9d7f-69ed40115066
Example:666911019
Example:POLPG
Success
Allowed values:successfailure
Example:864e43a0-2c2f-4a11-9d7f-69ed40115066
Example:666911019
Example:POLPG
Property to isolate source transaction(s) that initiated the reversal
Success
Unique identifier which used by every system to trace the request
Example:3a2a3435-2089-4b81-9959-e0d569ccf4f0
Zinnia Live Case ID
Example:CA0000369469
Zinnia Live Case Status
Example:IN_PROGRESS
Identifier for the generated or associated PDF document (e.g. OnBase document number). Returned on systematic program setup and update submit when available.
Example:DOC-10004567
preferenceId (should be null for preference creation)
Example:e22cd4aee27d34c9b7c748d50e558b41
carrier id for policy
Example:CARRIERID_1
Delivery Options - Applicable values EMAIL/FAX/MAIL
Allowed values:EMAILFAXMAIL
Example:EMAIL
User’s email
Example:abc.def@gmail.com
Date (with pattern “yyyy-MM-dd’T’HH:mm:ss’Z’”) when the preference will be effective, default value is ‘2999-12-31T00:00:00.000Z’
Date (with pattern “yyyy-MM-dd’T’HH:mm:ss’Z’”) when the preference will stop being effective
Type of document
Allowed values:NWBANSTCONFTAXAGNTPOLPG
Example:AGNT
Unique reference id of the party
Example:f22de4bff27e45d9a7c859e61f668c50
Party that initiated the acknowledgment (i.e. an agent, if not the party referred to by partyId)
Example:f22de4bff27e45d9a7c859e61f668c50
Success
Unique identifier which used by every system to trace the request
Example:3a2a3435-2089-4b81-9959-e0d569ccf4f0
Zinnia Live Case ID
Example:CA0000369469
Zinnia Live Case Status
Example:IN_PROGRESS
Identifier for the generated or associated PDF document (e.g. OnBase document number). Returned on systematic program setup and update submit when available.
Example:DOC-10004567