Eligibility Check Billing Feature Change

Evaluates whether the policy is eligible for a billing feature change transaction.

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Response

application/json

Billing Feature Change Eligibility Success Response

TransactionResponse

statusstring

Allowed values:successfailure

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

Validate Billing Feature Change

Validates the billing feature change request against business rules before submission.

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Body

application/json

BillingFeatureChangeRequest

Request body for billing feature change validation
(POST /bpm/v1/policies/{planCode}/{policyNumber}/billingfeaturechange/validation
and policy API alias).

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 billing feature change

Example:2026-07-24

transactionReasonstring

Reason for initiating the billing feature change transaction

Allowed values:AMOUNTFREQUENCYPAYMENTDUEDATE

Example:AMOUNT

policyFeaturesarray[object]required

Billing policy feature details for the change request

>= 1 items

Show Child Parameters
signaturesarray[object]

Signature details for billing feature change

Show Child Parameters
documentsarray[object]

Supporting document reference for billing feature 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

Response

application/json

Billing Feature Change Validation Success Response

TransactionResponse

statusstring

Allowed values:successfailure

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

Body

{ "correlationId": "e3bdb22b-790f-4357-ae60-42cdb0ff0d12", "effectiveDate": "2026-07-24", "transactionReason": "AMOUNT", "policyFeatures": [ { "featureType": "BILLING", "paymentAmount": 1000, "approvalDate": "2026-07-24", "frequency": "DAILY" } ], "signatures": [ { "isSignedPresent": true, "signDate": "2026-06-26", "signDesignation": null, "signType": "OWNER", "signTypeForUI": "Owner" }, { "isSignedPresent": false, "signDate": null, "signDesignation": null, "signType": "JOINTOWNER", "signTypeForUI": "Joint Owner" } ], "documents": [ { "documentId": "DOC123456", "documentType": "NFO_FORM", "documentDate": "2026-06-26", "caseId": "CA0000007389", "policyNumber": "WL987654321", "planCode": "WL1001" } ], "selfServeFlow": true, "supportingDocumentAttached": true }
 
application/json

Billing Feature Change

Submit billing feature change request against business rules before submission.

post

Path Parameters

planCodestringrequired

Plan Code

policyNumberstringrequired

Policy Number

Body

application/json

BillingFeatureChangeRequest

Request body for billing feature change validation
(POST /bpm/v1/policies/{planCode}/{policyNumber}/billingfeaturechange/validation
and policy API alias).

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 billing feature change

Example:2026-07-24

transactionReasonstring

Reason for initiating the billing feature change transaction

Allowed values:AMOUNTFREQUENCYPAYMENTDUEDATE

Example:AMOUNT

policyFeaturesarray[object]required

Billing policy feature details for the change request

>= 1 items

Show Child Parameters
signaturesarray[object]

Signature details for billing feature change

Show Child Parameters
documentsarray[object]

Supporting document reference for billing feature 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

Response

application/json

Success

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}/billingfeaturechange

Body

{ "correlationId": "e3bdb22b-790f-4357-ae60-42cdb0ff0d12", "effectiveDate": "2026-07-24", "transactionReason": "AMOUNT", "policyFeatures": [ { "featureType": "BILLING", "paymentAmount": 1000, "approvalDate": "2026-07-24", "frequency": "DAILY" } ], "signatures": [ { "isSignedPresent": true, "signDate": "2026-06-26", "signDesignation": null, "signType": "OWNER", "signTypeForUI": "Owner" }, { "isSignedPresent": false, "signDate": null, "signDesignation": null, "signType": "JOINTOWNER", "signTypeForUI": "Joint Owner" } ], "documents": [ { "documentId": "DOC123456", "documentType": "NFO_FORM", "documentDate": "2026-06-26", "caseId": "CA0000007389", "policyNumber": "WL987654321", "planCode": "WL1001" } ], "selfServeFlow": true, "supportingDocumentAttached": true }
 
application/json

Eligibility Check Payee Role Change

Evaluates whether the policy is eligible for a Payee 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

Payee Role Change Eligibility Success Response

TransactionResponse

statusstring

Allowed values:successfailure

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

Validate Payee Role Change

Validates the Payee 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

Payee Role Change Validation Success Response

TransactionResponse

statusstring

Allowed values:successfailure

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

Body

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