Eligibility Check Billing Feature Change
Evaluates whether the policy is eligible for a billing feature change transaction.
Path Parameters
Plan Code
Policy Number
Response
application/json
Response
Billing Feature Change Eligibility Success Response
TransactionResponse
Allowed values:successfailure
Show Child Parameters
Authentication
Path Parameters
Validate Billing Feature Change
Validates the billing feature change request against business rules before submission.
Path Parameters
Plan Code
Policy Number
Body
application/json
Body
BillingFeatureChangeRequest
Request body for billing feature change validation
(POST /bpm/v1/policies/{planCode}/{policyNumber}/billingfeaturechange/validation
and policy API alias).
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 billing feature change
Example:2026-07-24
Reason for initiating the billing feature change transaction
Allowed values:AMOUNTFREQUENCYPAYMENTDUEDATE
Example:AMOUNT
Billing policy feature details for the change request
>= 1 items
Show Child Parameters
Signature details for billing feature change
Show Child Parameters
Supporting document reference for billing feature change
Show Child Parameters
Whether the request originated from a self-serve flow
Example:true
Indicates whether supporting documents are attached
Example:true
Response
application/json
Response
Billing Feature Change Validation Success Response
TransactionResponse
Allowed values:successfailure
Show Child Parameters
Authentication
Path Parameters
Body
Billing Feature Change
Submit billing feature change request against business rules before submission.
Path Parameters
Plan Code
Policy Number
Body
application/json
Body
BillingFeatureChangeRequest
Request body for billing feature change validation
(POST /bpm/v1/policies/{planCode}/{policyNumber}/billingfeaturechange/validation
and policy API alias).
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 billing feature change
Example:2026-07-24
Reason for initiating the billing feature change transaction
Allowed values:AMOUNTFREQUENCYPAYMENTDUEDATE
Example:AMOUNT
Billing policy feature details for the change request
>= 1 items
Show Child Parameters
Signature details for billing feature change
Show Child Parameters
Supporting document reference for billing feature change
Show Child Parameters
Whether the request originated from a self-serve flow
Example:true
Indicates whether supporting documents are attached
Example:true
Response
application/json
Response
Submit Transaction Successful
TransactionAcceptedResponse
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
Authentication
Path Parameters
Body
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).
Path Parameters
Plan Code
Policy Number
Response
application/json
Response
Payee Role Change Eligibility Success Response
TransactionResponse
Allowed values:successfailure
Show Child Parameters
Authentication
Path Parameters
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).
Path Parameters
Plan Code
Policy Number
Body
application/json
Body
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.
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
Show Child Parameters
Signature details for the agent change
Show Child Parameters
Supporting document reference for a party role change
Show Child Parameters
Whether the request originated from a self-serve flow
Example:true
Indicates whether supporting documents are attached
Example:true
Reason for the change
Response
application/json
Response
Payee Role Change Validation Success Response
TransactionResponse
Allowed values:successfailure