BillingFeatureChangeTransactionReason
stringReason for initiating the billing feature change transaction
Allowed values:AMOUNTFREQUENCYPAYMENTDUEDATE
BillingFeatureChangePolicyFeature
objectBilling policy feature details for the change request
Type of the policy feature
Allowed values:BILLING
Example:BILLING
Billing payment amount
Example:1000
Date on which the feature change was approved
Example:2026-07-24
frequency
Allowed values:DAILYEVERYTWOWEEKSMONTHLYSEMIANNUALBIANNUALQUARTERLYANNUALSINGLEPAYMENTDEFAULT
BillingFeatureChangeSignature
objectSignature details for billing feature change
Example:true
Example:2026-06-26
Signature type code
Example:OWNER
Signature type label for UI display
Example:Owner
BillingFeatureChangeDocument
objectSupporting document reference for billing feature change
Example:DOC123456
Example:NFO_FORM
Example:2026-06-26
Example:CA0000007389
Example:WL987654321
Example:WL1001
BillingFeatureChangeRequest
objectRequest 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