Submit Power of Attorney Role Change

Submits the Power of Attorney 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).

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Body

application/json

MultiPartyRoleChangeRequest

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.

planCodestring

Plan code (may duplicate path parameter)

policyNumberstring

Policy number (may duplicate path parameter)

caseIdstring

Zinnia Live Case ID

Example:CA0000007389

correlationIdstring

The unique ID to track transaction request across all systems

Example:e3bdb22b-790f-4357-ae60-42cdb0ff0d12

carrierIdstring

Carrier identifier

Example:FNWL

effectiveDatestring(date)required

Effective date for the party role change

Example:2026-07-24

requestSourcestring

Origin of the request

Allowed values:DATA_ENTRYSELF_SERVE

partyUpdatesarray[object]required

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

Show Child Parameters
signaturesarray[object]

Signature details for the agent change

Show Child Parameters
documentsarray[object]

Supporting document reference for a party role change

Show Child Parameters
selfServeFlowboolean

Whether the request originated from a self-serve flow

Example:true

supportingDocumentAttachedboolean

Indicates whether supporting documents are attached

Example:true

changeReasonstring

Reason for the change

Response

application/json

Submit Transaction Successful

TransactionAcceptedResponse

correlationIdstring

Unique identifier which used by every system to trace the request

Example:3a2a3435-2089-4b81-9959-e0d569ccf4f0

caseIdstring

Zinnia Live Case ID

Example:CA0000369469

caseStatusstring

Zinnia Live Case Status

Example:IN_PROGRESS

pdfIdstring

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

post/policy/v1/transactions/{planCode}/{policyNumber}/parties/PowerOfAttorney

Body

{ "correlationId": "e3bdb22b-790f-4357-ae60-42cdb0ff0d12", "planCode": "EVGFIA909", "policyNumber": "EVFIA095509100", "effectiveDate": "2026-07-24", "requestSource": "DATA_ENTRY", "partyUpdates": [ { "action": "ADD", "partyRole": "ATTORNEY_IN_FACT", "party": { "firstName": "John", "lastName": "Doe", "dateOfBirth": "1980-05-12", "gender": "M" } } ] }
 
application/json

Eligibility Check Authorized Signatory Role Change

Evaluates whether the policy is eligible for a Authorized Signatory role change transaction.
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).

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Response

application/json

Authorized Signatory Role Change Eligibility Success Response

TransactionResponse

statusstring

Allowed values:successfailure

errorarray[object]
Show Child Parameters
quoteResponseobject
post/policy/v1/transactions/{planCode}/{policyNumber}/parties/authorizedsignatory/eligibilitycheck
 
application/json

Validate Authorized Signatory Role Change

Validates the Authorized Signatory role change request (one or more PartyUpdate entries -
ADD/UPDATE/DELETE) against business rules before submission.
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).

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Body

application/json

MultiPartyRoleChangeRequest

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.

planCodestring

Plan code (may duplicate path parameter)

policyNumberstring

Policy number (may duplicate path parameter)

caseIdstring

Zinnia Live Case ID

Example:CA0000007389

correlationIdstring

The unique ID to track transaction request across all systems

Example:e3bdb22b-790f-4357-ae60-42cdb0ff0d12

carrierIdstring

Carrier identifier

Example:FNWL

effectiveDatestring(date)required

Effective date for the party role change

Example:2026-07-24

requestSourcestring

Origin of the request

Allowed values:DATA_ENTRYSELF_SERVE

partyUpdatesarray[object]required

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

Show Child Parameters
signaturesarray[object]

Signature details for the agent change

Show Child Parameters
documentsarray[object]

Supporting document reference for a party role change

Show Child Parameters
selfServeFlowboolean

Whether the request originated from a self-serve flow

Example:true

supportingDocumentAttachedboolean

Indicates whether supporting documents are attached

Example:true

changeReasonstring

Reason for the change

Response

application/json

Authorized Signatory Role Change Validation Success Response

TransactionResponse

statusstring

Allowed values:successfailure

errorarray[object]
Show Child Parameters
quoteResponseobject
post/policy/v1/transactions/{planCode}/{policyNumber}/parties/authorizedsignatory/validation

Body

{ "correlationId": "e3bdb22b-790f-4357-ae60-42cdb0ff0d12", "planCode": "EVGFIA909", "policyNumber": "EVFIA095509100", "effectiveDate": "2026-07-24", "requestSource": "DATA_ENTRY", "partyUpdates": [ { "action": "ADD", "partyRole": "AuthorizedSignatory", "party": { "firstName": "John", "lastName": "Doe", "dateOfBirth": "1980-05-12", "gender": "M" } } ] }
 
application/json

Submit Authorized Signatory Role Change

Submits the Authorized Signatory 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).

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Body

application/json

MultiPartyRoleChangeRequest

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.

planCodestring

Plan code (may duplicate path parameter)

policyNumberstring

Policy number (may duplicate path parameter)

caseIdstring

Zinnia Live Case ID

Example:CA0000007389

correlationIdstring

The unique ID to track transaction request across all systems

Example:e3bdb22b-790f-4357-ae60-42cdb0ff0d12

carrierIdstring

Carrier identifier

Example:FNWL

effectiveDatestring(date)required

Effective date for the party role change

Example:2026-07-24

requestSourcestring

Origin of the request

Allowed values:DATA_ENTRYSELF_SERVE

partyUpdatesarray[object]required

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

Show Child Parameters
signaturesarray[object]

Signature details for the agent change

Show Child Parameters
documentsarray[object]

Supporting document reference for a party role change

Show Child Parameters
selfServeFlowboolean

Whether the request originated from a self-serve flow

Example:true

supportingDocumentAttachedboolean

Indicates whether supporting documents are attached

Example:true

changeReasonstring

Reason for the change

Response

application/json

Submit Transaction Successful

TransactionAcceptedResponse

correlationIdstring

Unique identifier which used by every system to trace the request

Example:3a2a3435-2089-4b81-9959-e0d569ccf4f0

caseIdstring

Zinnia Live Case ID

Example:CA0000369469

caseStatusstring

Zinnia Live Case Status

Example:IN_PROGRESS

pdfIdstring

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

post/policy/v1/transactions/{planCode}/{policyNumber}/parties/authorizedsignatory

Body

{ "correlationId": "e3bdb22b-790f-4357-ae60-42cdb0ff0d12", "planCode": "EVGFIA909", "policyNumber": "EVFIA095509100", "effectiveDate": "2026-07-24", "requestSource": "DATA_ENTRY", "partyUpdates": [ { "action": "ADD", "partyRole": "AuthorizedSignatory", "party": { "firstName": "John", "lastName": "Doe", "dateOfBirth": "1980-05-12", "gender": "M" } } ] }
 
application/json

Eligibility Check Multi Owner Change

Evaluates whether the policy is eligible for a Multi Owner Change transaction
(Owner, Joint Owner, and Successor Owner changes in a single request).
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).

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Response

application/json

Multi Owner Change Eligibility Success Response

TransactionResponse

statusstring

Allowed values:successfailure

errorarray[object]
Show Child Parameters
quoteResponseobject
post/policy/v1/transactions/{planCode}/{policyNumber}/parties/MultiOwnerChange/eligibilitycheck
 
application/json