Case identifier.
Example:CA0001552404
Evaluates whether the authenticated user may perform configured case-level features
for the given case. The caller supplies only caseId; policy number, plan code,
carrier, process, process subtype, and case correlationId are resolved from Case
Management.
The service maps the case process/processSubType to a transaction type, resolves
enabled features from feature configuration, and evaluates configured checks such as
case status, carrier onboarding, user permission, and Zahara transaction status.
Zahara transaction status is matched by the case correlationId against the list of
Zahara transactions returned for the case policy’s plan code and policy number.
If items is omitted or empty, all features configured for the resolved
carrier/plan/transaction are evaluated. partyId is extracted from the
Authorization bearer token; it is never a body field.
Case identifier.
Example:CA0001552404
Optional request body for case-level eligibility. The caller supplies only caseId in the path; policy and transaction context are resolved from Case Management. When items is absent or empty, all configured case features are evaluated.
Case feature identifiers to evaluate.
Example:cancelTransaction
Case eligibility evaluation completed. One result entry per evaluated case feature.
Top-level case eligibility response envelope.
Case eligibility response type.
Allowed values:case
Example:case
Case identifier evaluated.
Example:CA0001552404
Carrier code resolved from Case Management.
Example:EVGL
Process key resolved from Case Management.
Example:Withdrawal
Process subtype key resolved from Case Management.
Example:Full Surrender
Transaction type resolved from case process mapping.
Example:FullSurrender
Composed eligibility result for a single case feature. Null fields are omitted from the JSON response. Evaluated results include the configured check sections; unavailable or unmapped features include notAvailable/notConfigured metadata.
The plan code for the policy number
Example:planCode
Policy Number
Example:policyNumber
Policyholder Authorization request
Unique record ID (maps to transactionID)
Example:546bed32-a8b6-43dc-8772-cefb1d469b1d
Correlation ID linking BPM - MPV transaction
Example:468cd184-fb43-4a20-aa8c-23df99c0a353
Case identifier within BPM
Example:CA0000487609
Policy Number associated with the transaction
Example:FM00000001
Policy Holder Authorization Status
Allowed values:APPROVEDDENIED
Example:APPROVED
Name of Policy Holder
Example:Flora Anderson
Generated at Time
Example:2025-06-02T10:45:00Z
Source system sending the callback
Default:MPV
Example:My Policy View
OK - Callback processed successfully
Example:200
Transaction Model success
Model for a transaction with detailed information.
Unique identifier for the transaction record.
Correlation ID associated with the transaction.
Type of transaction.
Carrier associated with the transaction.
Source of the transaction.
Type of the entity involved.
Unique identifier for the entity.
Actual entity information as JSON Object.
Expiration timestamp for the transaction.
Timestamp when the transaction was created.
Timestamp when the transaction was last updated.
User or system that created the transaction.
User or system that last updated the transaction.
Identifier model with key-value pair.
Allowed values:SystematicProgramSetupSystematicProgramUpdate
Success response
Allowed values:SystematicProgramSetupSystematicProgramUpdate
Success response