SaveCommentResponse
objectCase identifier associated with the transaction. Populated on successful saves.
Indicates whether the operation was successful
Human-readable message describing the result
Status code of the operation (e.g., “Success”, “ValidationError”, “Failure”)
SaveEsignatureRequest
objectTransaction (case) identifier to submit for e-signature.
>= 1
Final signer roster with selected auth method and contact details.
>= 1 items
Show Child Parameters
SaveEsignatureResponse
objectTrue when the case was submitted to DocuSign for e-signature.
User-safe confirmation or failure text from the submission result.
SaveEsignatureSignerRequest
objectDocuSign recipient ID from GET signers (required for submission).
Access code when required; empty string when none.
Selected auth method for submission (for example Phone).
Country calling code (default 1 for US).
Signer email; may be empty for some roles.
Entity role (for example PrimaryOwner, AgentOfRecord).
Display name sent to DocuSign for this recipient.
Phone digits only; stored without dashes.
Signing order when routing is sequential.
SectionBlueprint
objectThe unique identifier for the section
>= 1 characters
A key used to group related sections within the blueprint
An identifier (partName) for the section
>= 1 characters
The section title in multiple languages. Supports localization through language codes (e.g., en, fr)
Show Child Parameters
An array of module names associated with this section
Indicates whether this section is custom
Array of subsections within this section
Show Child Parameters
Role identifier controlling copy behavior. Use ‘none’ to disable copying, or a role name (e.g., ‘owner’, ‘annuitant’, ‘insured’, ‘payor’). Multiple roles may be comma-separated.
An array of conditions that determine when a section is rendered
An array of PDF document identifiers where this section appears
An array of platforms where this section is available (e.g., D2C-only versus advisor-driven experiences)
Visibility conditions for the section. When present, the section is only visible when all conditions are met. Example: { “booleanOperator”: “AND”, “conditions”: [ { “type”: “equality”, “isEqual”: true, “value”: “NY”, “targetNodeId”: “SolicitationStateCode” } ] }
Example:{"booleanOperator":"AND","conditions":[{"type":"equality","isEqual":true,"value":"Yes","targetNodeId":"Transaction.SolicitationState"},{"type":"equality","isEqual":true,"value":"Yes","targetNodeId":"Transaction.SolicitationState"}]}
Show Child Parameters
Repeat-instance metadata when the wizard section declares IsRepeated.