ProductPricingYearCharge
objectQuestionData
objectOne row of captured or echoed answer data. Must include id, type, and value (the JSON property value must be present on each row; use JSON null for an empty optional answer when applicable). On PUT, id must match the enclosing data field key (or the leaf key inside a collection item’s data). type must be a QuestionData storage type (see QuestionDataStorageTypes); collection value rows use collectionItem on each CollectionItem.
Must match the field key under data for this row exactly, including case; inside collection rows, must match the leaf key in the item’s data map exactly, including case.
>= 1 characters
Data-storage type for the question row. Must match the corresponding blueprint field type and be one of: input, dropdown, radio, checkbox, checkboxgroup, date, phone, email, money, number, label, information, collection, Person, Address, Hidden. Values are case-sensitive.
Allowed values:inputdropdownradiocheckboxcheckboxgroupdatephoneemailmoneynumberlabelinformationcollectionPersonAddressHidden
>= 1 characters
Example:input
The title of the question shown to the user. This value should be kept in sync with the title property of the associated field
The subtext shown to the user below the question title. This value should be kept in sync with the text property of the associated field
The display text representing the user’s selected answer. For example, a country dropdown may display ‘United States of America’ to the user, while the blueprint stores the value as ‘USA’
Any OfThe actual value of the question (required on each QuestionData row in data; JSON null is allowed for an empty optional answer). Can be a string, integer, number, float, date, date-time, boolean, or array of CollectionItem objects depending on the field type.
String value for simple fields
Example:PrimaryBeneficiary
Zero-based row index for repeatable collection rows in transaction data lists; 0 for single-value fields. Must be greater than or equal to 0.
>= 0
True when value is a prefill; omitted in JSON when false.
True when the field is prefilled and must be shown as read-only/locked in the UI; omitted in JSON when false. Enforcement is client-side — the API does not reject edits to a readonly row.
QuestionDataRows
arrayAll answer rows for one question or composite collection field id. Use index on each row for repeatable collection instances. Each row must include id, type, and value (see QuestionData schema).
Must match the field key under data for this row exactly, including case; inside collection rows, must match the leaf key in the item’s data map exactly, including case.
>= 1 characters
Data-storage type for the question row. Must match the corresponding blueprint field type and be one of: input, dropdown, radio, checkbox, checkboxgroup, date, phone, email, money, number, label, information, collection, Person, Address, Hidden. Values are case-sensitive.
Allowed values:inputdropdownradiocheckboxcheckboxgroupdatephoneemailmoneynumberlabelinformationcollectionPersonAddressHidden
>= 1 characters
Example:input
The title of the question shown to the user. This value should be kept in sync with the title property of the associated field
The subtext shown to the user below the question title. This value should be kept in sync with the text property of the associated field
The display text representing the user’s selected answer. For example, a country dropdown may display ‘United States of America’ to the user, while the blueprint stores the value as ‘USA’
Any OfThe actual value of the question (required on each QuestionData row in data; JSON null is allowed for an empty optional answer). Can be a string, integer, number, float, date, date-time, boolean, or array of CollectionItem objects depending on the field type.
String value for simple fields
Example:PrimaryBeneficiary
Zero-based row index for repeatable collection rows in transaction data lists; 0 for single-value fields. Must be greater than or equal to 0.
>= 0
True when value is a prefill; omitted in JSON when false.
True when the field is prefilled and must be shown as read-only/locked in the UI; omitted in JSON when false. Enforcement is client-side — the API does not reject edits to a readonly row.
RenderCondition
Single condition or nested condition group controlling whether a field/section is rendered.
One OfKind of comparison performed by the condition.
Allowed values:equalityequalityConditionrangepresence
Example:equalityCondition
When true the target must equal value; when false it must differ.
Example:true
The value to compare against the resolved target answer.
Example:NY
The answer node identifier whose value is evaluated by this condition.
Example:SolicitationStateCode
RepeatableBlueprint
objectBlueprint id this repeat block is bound to (matches SubsectionBlueprint.id or FieldGroupBlueprint.id).
Localized label for the control that adds another row.
Show Child Parameters
Localized label for removing a row.
Show Child Parameters
Minimum number of instances.
Maximum number of instances.
Optional binding path for persisted repeat instances.