Saves a comment against the specified transaction.
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request body failed validation or required fields are missing. -
INVALID_TRANSACTION_ID- The supplied transaction ID is invalid (not a positive integer). -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
NOT_FOUND- No transaction exists for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Body
application/json
Body
The comment payload to save.
Indicator identifying whether the comment applies to the application or sub-application
Source system or user group that authored the comment
Free-form comment text
>= 1 characters
Status code of the transaction at the step the comment was added
Display name for the status at the step the comment was added
Title of the wizard step the comment was added on
Unique identifier of the transaction the comment belongs to (positive integer encoded as a string)
Match pattern:^[1-9][0-9]*$
>= 1 characters
Response
application/json
Response
Returns the save comment envelope
SaveCommentResponse
Case identifier associated with the transaction. Populated on successful saves.
Indicates whether the operation was successful
Human-readable message describing the result
Status code of the operation (e.g., “Success”, “ValidationError”, “Failure”)
Authentication
Body
Deletes a comment from a transaction.
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request body failed validation, required fields are missing, or the comment ID is invalid. -
INVALID_TRANSACTION_ID- The supplied transaction ID is invalid (not a positive integer). -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
NOT_FOUND- No comment exists for the specified comment ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Body
application/json
Body
The comment and transaction identifiers for the comment to delete.
Unique 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
Response
application/json
Response
Returns the delete comment envelope
DeleteCommentResponse
Case 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”)
Authentication
Body
Retrieves the comments for a transaction.
Error Responses
-
400 Bad Request
-
INVALID_TRANSACTION_ID- The supplied transaction ID is invalid (not a positive integer). -
VALIDATION_ERROR- Pagination parameters are invalid (both page and pageSize must be supplied together; page must be ≥ 1; pageSize must be between 1 and 100). -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
NOT_FOUND- No comments exist for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Query Parameters
1-based page number. Omit both page and pageSize to return all comments.
Number of comments per page (1–100). Omit both page and pageSize to return all comments.
Path Parameters
Unique identifier of the transaction (positive integer encoded as a string).
Response
application/json
Response
Returns the comments envelope
GetCommentsResponse
Case identifier associated with the transaction
Comments data payload
Show Child Parameters
Indicates whether the operation was successful
Human-readable message describing the result
Status code of the operation
Authentication
Path Parameters
Query Parameters
ReviewerAction
Reviewer workflow actions (Approved, Declined, Terminate) forwarded to the product order-entry service
Executes a reviewer action for the given transaction (forwards to the product order-entry service).
Error Responses
-
400 Bad Request
-
VALIDATION_ERROR- The request failed input validation. -
INVALID_TRANSACTION_ID- The supplied transaction ID is not a valid value. -
401 Unauthorized
-
UNAUTHORIZED- Authentication failed or the access token is missing, expired, or invalid. -
403 Forbidden
-
FORBIDDEN- The authenticated user is not authorized to access this resource. -
404 Not Found
-
TRANSACTION_ID_NOT_FOUND- No transaction exists for the specified transaction ID. -
429 Too Many Requests
-
RATE_LIMIT_EXCEEDED- The client has exceeded the permitted request rate or quota. -
500 Internal Server Error
-
UNEXPECTED_ERROR- An unexpected internal system error occurred while processing the request. -
502 Bad Gateway
-
UPSTREAM_SERVICE_ERROR- An upstream dependency returned an invalid or unsuccessful response. -
503 Service Unavailable
-
SERVICE_UNAVAILABLE- The service or a required dependency is temporarily unavailable. -
504 Gateway Timeout
-
UPSTREAM_TIMEOUT- A required downstream service did not respond within the configured timeout.
Standard Error Response
All error responses conform to the standard ErrorResponse schema and include:
- A stable error code from
ErrorInfo.code. - A human-readable error message.
- Optional diagnostic details, when applicable.
- A timestamp indicating when the error occurred.
This consistent format enables clients to implement standardized error processing, logging, and troubleshooting across all Order Entry API endpoints.
Body
application/json
Body
Action and transaction identifier.
ReviewerActionRequest
Review outcome: Approved, Declined, or Terminate.
>= 1 characters
Order-entry transaction (instance) identifier.
>= 1<= 2147483647
Response
application/json
Response
Returns the reviewer action outcome
ReviewerActionResponse
Case identifier returned by the upstream service when available.
True when the reviewer action completed successfully.
Human-readable outcome message.
High-level status string returned to the client.