CreateTransactionRequest
objectThe state in which the life or annuity transaction is being solicited.
>= 1 characters
The unique identifier for the product. This code allows the Order Entry API to determine the appropriate distributor, carrier, and product configuration
>= 1 characters
DatasetResponse
objectOutcome of the dataset lookup. “Success” on success; otherwise the backend exception type name (e.g. “NullReferenceException”, “ItemNotFoundException`2”).
>= 1 characters
Human-readable message describing the outcome. On success a confirmation string; on failure the backend error message.
>= 1 characters
Dataset payload serialized as a JSON string. On success, a JSON array of {Name, Value} option objects. On failure, may be “[]” or omitted.
Identifier of the dataset instance returned by the upstream service. Present for success and most failures; absent for low-level exceptions.
DocumentRule
objectConditions under which the rule applies
Rule key
Rule message shown to the user
Rule value
ErrorInfo
objectBackend error codes returned by the Order Entry API indicating validation failures, transaction issues, blueprint generation errors, authorization errors, or unexpected system failures.
Allowed values:VALIDATION_ERRORINVALID_TRANSACTION_IDINVALID_STEP_NAMETRANSACTION_CREATION_FAILEDTRANSACTION_ID_NOT_FOUNDSAVE_TRANSACTION_ERRORSAVE_TRANSACTION_FAILEDINVALID_RESPONSE_FORMATBUILD_BLUEPRINT_ERRORJSON_PARSE_ERRORTRANSFORMER_NULL_RESPONSEEMPTY_BLUEPRINTUNEXPECTED_ERRORSERVICE_ERRORUNAUTHORIZEDFORBIDDENNOT_FOUNDFIRST_STEP_SETUP_FAILED
ErrorResponse
object>= 1 characters
Example:{"code":"VALIDATION_ERROR","description":"Input validation failed","details":"One or more input fields are invalid","timestamp":"2024-01-15T10:30:00.000Z"}