Unique identifier assigned when an order entry transaction is created
Transaction
Transaction management operations
Retrieves the order entry blueprint and its associated responses for a created life or annuity transaction
This endpoint reopens an existing transaction and returns the order entry blueprint along with any previously saved responses, allowing the user to resume where they left off
Error Scenarios
-
400 Bad Request:
-
VALIDATION_ERROR- Input validation failed -
INVALID_TRANSACTION_ID- Transaction ID is less than or equal to 0 -
401 Unauthorized:
-
UNAUTHORIZED- Authentication failed or token is invalid -
403 Forbidden:
-
FORBIDDEN- User does not have permission to access this resource -
404 Not Found:
-
TRANSACTION_ID_NOT_FOUND- Transaction not found in the system -
NOT_FOUND- Transaction or step not found -
500 Internal Server Error:
-
BUILD_BLUEPRINT_ERROR- Error building the blueprint -
JSON_PARSE_ERROR- Error parsing JSON response -
UNEXPECTED_ERROR- Unexpected system error
Success Response
On success, returns a TransactionResponse with:
- TransactionId: The transaction ID
- Data: Transaction field data
- Blueprint: Complete section and field definitions
- Error: null (no error)
Path Parameters
Response
application/json
Response
Returns a product’s order entry blueprint with associated answer data
TransactionResponse
The unique identifier for the created transaction
>= 1 characters
The case identifier returned by the product service
Dictionary of question data keyed by question ID
The blueprint containing section and field definitions
Show Child Parameters
Subscribers defining dataset dependency actions
Show Child Parameters
Collection of errors if the operation failed
Example:{"code":"VALIDATION_ERROR","description":"Input validation failed","details":"One or more input fields are invalid","timestamp":"2024-01-15T10:30:00.000Z"}
Show Child Parameters
Collection of validation errors when transaction validation fails. Includes transaction ID, field ID, and error messages.
Example:{"answerNodeId":"Transaction.PrimaryOwner.FirstName","message":"First name is required","sectionName":"PersonalInformation"}
Show Child Parameters
Authentication
Path Parameters
Update transaction data (enhanced blueprint)
Updates transaction data for enhanced blueprint transactions without providing a step name. When validation fails, returns 200 with a blueprint containing a validation-messages section and a validationErrors array listing field-level validation errors.
Path Parameters
Body
application/json
Body
Transaction update request - a dictionary keyed by question ID whose values are QuestionData objects.
Response
application/json
Response
OK
TransactionResponse
The unique identifier for the created transaction
>= 1 characters
The case identifier returned by the product service
Dictionary of question data keyed by question ID
The blueprint containing section and field definitions
Show Child Parameters
Subscribers defining dataset dependency actions
Show Child Parameters
Collection of errors if the operation failed
Example:{"code":"VALIDATION_ERROR","description":"Input validation failed","details":"One or more input fields are invalid","timestamp":"2024-01-15T10:30:00.000Z"}
Show Child Parameters
Collection of validation errors when transaction validation fails. Includes transaction ID, field ID, and error messages.
Example:{"answerNodeId":"Transaction.PrimaryOwner.FirstName","message":"First name is required","sectionName":"PersonalInformation"}
Show Child Parameters
Authentication
Path Parameters
Body
Retrieves the order entry blueprint and its associated responses for a created life or annuity transaction on a specific step.
In a multi-blueprint setup, this endpoint allows navigation to a specific section within the blueprint structure and returns the blueprint for the selected section for rendering
Error Scenarios
-
400 Bad Request:
-
VALIDATION_ERROR- Input validation failed -
INVALID_TRANSACTION_ID- Transaction ID is less than or equal to 0 -
INVALID_STEP_NAME- Step name is null or whitespace -
401 Unauthorized:
-
UNAUTHORIZED- Authentication failed or token is invalid -
403 Forbidden:
-
FORBIDDEN- User does not have permission to access this resource -
404 Not Found:
-
TRANSACTION_ID_NOT_FOUND- Transaction not found in the system -
NOT_FOUND- Transaction or step not found -
500 Internal Server Error:
-
BUILD_BLUEPRINT_ERROR- Error building the blueprint -
JSON_PARSE_ERROR- Error parsing JSON response -
UNEXPECTED_ERROR- Unexpected system error
Success Response
On success, returns a TransactionResponse with:
- TransactionId: The transaction ID
- Data: Transaction field data
- Blueprint: Complete section and field definitions
- Error: null (no error)
Path Parameters
Unique identifier assigned when an order entry transaction is created
PascalCase step identifier matching the section ID in the blueprint (e.g. CarrierProductSelection, EntityOwners). Values are returned verbatim from the backend blueprint - do not lowercase or transform them.
Response
application/json
Response
Returns a product’s order entry blueprint with associated answer data
TransactionResponse
The unique identifier for the created transaction
>= 1 characters
The case identifier returned by the product service
Dictionary of question data keyed by question ID
The blueprint containing section and field definitions
Show Child Parameters
Subscribers defining dataset dependency actions
Show Child Parameters
Collection of errors if the operation failed
Example:{"code":"VALIDATION_ERROR","description":"Input validation failed","details":"One or more input fields are invalid","timestamp":"2024-01-15T10:30:00.000Z"}
Show Child Parameters
Collection of validation errors when transaction validation fails. Includes transaction ID, field ID, and error messages.
Example:{"answerNodeId":"Transaction.PrimaryOwner.FirstName","message":"First name is required","sectionName":"PersonalInformation"}
Show Child Parameters
Authentication
Path Parameters
Update the Order Entry transaction data for life and annuity products.
In a multi-blueprint setup, this endpoint is used to save user responses and return the next relevant blueprint for continued rendering
Request Body Format
The request body is a JSON object where:
- Keys: Question IDs (e.g., “259726”, “489363”)
- Values: QuestionData objects containing field information and values
Supported Field Types
- Field Type | Description | Value Type | -
input| Text input field | string | -dropdown| Select dropdown field | string | -radio| Radio button field | string | -checkbox| Checkbox field | boolean | -date| Date picker field | string (YYYY-MM-DD) | -phone| Phone number field | string | -collection| Complex nested data structure | array of CollectionItem | #### Simple Field Example
"259726": {
"id": "259726",
"type": "dropdown",
"questionText": "Account designation",
"questionSubText": "Account designation",
"displayValue": "Owner",
"value": "Owner"
}
}```
Collection Field Example
"489363": {
"id": "489363",
"type": "collection",
"questionText": "Name",
"questionSubText": "",
"displayValue": "",
"value": [
{
"surrogateId": "489363_1",
"type": "collectionItem",
"data": {
"489363_FirstName": {
"id": "489363_FirstName",
"type": "input",
"questionText": "First Name",
"questionSubText": "",
"displayValue": "John",
"value": "John"
},
"489363_LastName": {
"id": "489363_LastName",
"type": "input",
"questionText": "Last Name",
"questionSubText": "",
"displayValue": "Doe",
"value": "Doe"
}
}
}
]
}
}```
Error Scenarios
-
400 Bad Request:
-
VALIDATION_ERROR- Input validation failed (ModelState errors) -
INVALID_TRANSACTION_ID- Invalid transaction ID provided -
INVALID_STEP_NAME- Invalid step name provided -
401 Unauthorized:
-
UNAUTHORIZED- Authentication failed or token is invalid -
403 Forbidden:
-
FORBIDDEN- User does not have permission to update this transaction -
500 Internal Server Error:
-
SAVE_TRANSACTION_ERROR- Save operation failed at service level -
SAVE_TRANSACTION_FAILED- Save operation not successful -
INVALID_RESPONSE_FORMAT- Invalid response format from service -
EMPTY_BLUEPRINT- Empty blueprint returned after save -
BUILD_BLUEPRINT_ERROR- Error building blueprint for next step -
UNEXPECTED_ERROR- Unexpected system error
Success Response
On success, returns a TransactionResponse with:
- TransactionId: The transaction ID that was updated
- Data: Updated transaction field data
- Blueprint: Blueprint for the next step in the workflow
- Error: null (no error)
Workflow Progression
This endpoint is used to:
- Save user input for the current step
- Validate the input data
- Automatically determine next step from breadcrumb
- Return the blueprint for the next step
Path Parameters
The unique identifier for the transaction
PascalCase step identifier matching the section ID in the blueprint (e.g. CarrierProductSelection, EntityOwners). Values are returned verbatim from the backend blueprint - do not lowercase or transform them. Optional for enhanced blueprint.
Body
application/json
Body
The input data for updating the transaction (dictionary of question data)
Transaction update request - a dictionary keyed by question ID whose values are QuestionData objects.
Response
application/json
Response
Returns the Order Entry blueprint for next step or success status
TransactionResponse
The unique identifier for the created transaction
>= 1 characters
The case identifier returned by the product service
Dictionary of question data keyed by question ID
The blueprint containing section and field definitions
Show Child Parameters
Subscribers defining dataset dependency actions
Show Child Parameters
Collection of errors if the operation failed
Example:{"code":"VALIDATION_ERROR","description":"Input validation failed","details":"One or more input fields are invalid","timestamp":"2024-01-15T10:30:00.000Z"}
Show Child Parameters
Collection of validation errors when transaction validation fails. Includes transaction ID, field ID, and error messages.
Example:{"answerNodeId":"Transaction.PrimaryOwner.FirstName","message":"First name is required","sectionName":"PersonalInformation"}