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 matches the data node returned by GET and Create transaction APIs:

• data: Object keyed by question or composite field id
• Values: Arrays of QuestionData rows; each row must include id, type, and value (use index for repeatable collection rows; JSON null for value is allowed for an empty optional answer when the property is present)

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

  "data": {
    "259726": [{
      "id": "259726",
      "type": "dropdown",
      "questionText": "Account designation",
      "questionSubText": "Account designation",
      "displayValue": "Owner",
      "value": "Owner",
      "index": 0
    }]
  }
}```

Collection Field Example

  "data": {
    "489363_FirstName": [{
      "id": "489363_FirstName",
      "type": "text",
      "questionText": "First Name",
      "displayValue": "John",
      "value": "John",
      "index": 0
    }],
    "489363_LastName": [{
      "id": "489363_LastName",
      "type": "text",
      "questionText": "Last Name",
      "displayValue": "Doe",
      "value": "Doe",
      "index": 0
    }]
  }
}```

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
• CaseId: The case identifier returned by the upstream product service (may be null until the case is created)
• Data: Updated transaction field data keyed by question ID
• Blueprint: Blueprint for the next step in the workflow
• Subscribers: Reactive subscriber definitions consumed by the UI to drive dependent dataset lookups (may be empty if no subscribers apply to the next step)
• Errors: Empty array on success (or absent)

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

Error Scenarios

• 400 Bad Request:

• VALIDATION_ERROR - Input validation failed (ModelState errors)

• INVALID - Invalid input parameters

• 401 Unauthorized:

• UNAUTHORIZED - Authentication failed or token is invalid

• 403 Forbidden:

• FORBIDDEN - User does not have permission to create transactions

• 500 Internal Server Error:

• TRANSACTION_CREATION_FAILED - Transaction creation failed at service level

• TRANSACTION_ID_NOT_FOUND - Service didn’t return transaction ID

• FIRST_STEP_SETUP_FAILED - First step initialization failed (breadcrumb, payload creation, or save)

• JSON_PARSE_ERROR - Failed to parse service response

• BUILD_BLUEPRINT_ERROR - Error building blueprint after creation

• UNEXPECTED_ERROR - Unexpected system error

Success Response

On success, returns a TransactionResponse with:

• TransactionId: The newly created transaction ID
• CaseId: The case identifier returned by the upstream product service (may be null until the case is fully created)
• Data: Initial transaction field data keyed by question ID
• Blueprint: Complete section and field definitions for the new transaction
• Subscribers: Reactive subscriber definitions consumed by the UI to drive dependent dataset lookups
• Errors: Empty array on success (or absent)

Input Validation

The following fields are validated:

• State: Must be a two-letter code that is a valid US state, territory, or military mail code (see API state mapping)
• CUSIP: Must be a valid CUSIP

Service Routing

The API automatically routes to the appropriate service based on CUSIP:

• Annuity Service: Configured Annuity CUSIPs
• Life Service: Configured Life CUSIPs

Transaction Creation Flow

The transaction creation process includes:

• Validate input parameters
• Determine service routing based on CUSIP
• Create transaction via appropriate service (Life or Annuity)
• Get breadcrumb to determine first step
• Retrieve order entry values for first step
• Create and save first step payload
• Build complete blueprint for the transaction

First Step Setup Failures

The FIRST_STEP_SETUP_FAILED error can occur when:

• No breadcrumb steps are found
• First step name is null or empty
• Order entry values are null or empty
• First step payload creation fails
• First step data save operation fails
• First step save response indicates failure

Submits the transaction to the order-entry service. Returns 400 with the inner Data.Message when the submit Data payload reports Success false and TotalValidationErrors greater than zero.

Returns dataset contents based on the provided transaction, step, field, and dependency inputs.