CreateTransactionRequest
objectUS state, territory, or military mail code (2 characters). Uppercase letters only.
Allowed values:ALAKAZARAAAEAPCACOCTDEDCFLGAGUHIIDILINIAKSKYLAMEMDMAMIMNMSMOMTNENVNHNJNMNYNCNDOHOKORPAPRRISCSDTNTXUTVTVIVAWAWVWIWY
Match pattern:^[A-Z]{2}$
Example:NC
Configured product CUSIP (9 characters). Uppercase letters and digits only.
Match pattern:^[0-9A-Z]{9}$
Example:90353U115
Optional opportunity identifier in UUID format.
Example:a1b2c3d4-e5f6-7890-abcd-ef1234567890
DatasetRequest
objectUnique identifier of the transaction (positive integer as a string).
>= 1 characters
Name of the wizard step containing the dependent control.
>= 1 characters
Identifier of the field (control) whose dataset is being requested.
>= 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.
DeleteCommentRequest
objectUnique identifier of the comment to delete (positive integer encoded as a string)
Match pattern:^[1-9][0-9]*$
>= 1 characters
Unique identifier of the transaction the comment belongs to (positive integer encoded as a string)
Match pattern:^[1-9][0-9]*$
>= 1 characters
DeleteCommentResponse
objectCase identifier associated with the transaction. Populated on successful deletes.
Indicates whether the operation was successful
Human-readable message describing the result
Status code of the operation (e.g., “Success”, “ValidationError”, “Failure”)