Submitter Error Messages

If the Submitter API rejects a transaction message or encounters an error before it sends the transaction to Rx Connect, it returns an error. The following is an example of an error response.

Error Response Table

This is a non-exhaustive list of objects and properties that can be included in an error response.

Properties	Notes / Values
status	For more information, see Error Message Codes.
type	https://problems-registry.optum.com/[type-variable] For more information on the different type variables to include in the type URL, see Error Message Codes.
title	For more information, see Error Message Codes.
detail	For more information, see Error Message Codes.
Code	The status number with additional numbers
instance	Submitter endpoint

Error Message Codes

The following are the error messages that Submitter API returns depending on the issue that Submitter encountered.
Note: The value in the Type column is meant to append the following URL:
https://problems-registry.optum.com/[type]

Type	Title	Detail	Status
bad-gateway	Bad Gateway	The server encountered an invalid response while acting as a gateway or proxy. Please try again later	502
bad-request	Bad Request	The request is invalid or malformed	400
not-implemented	Not Implemented	The server does not support the functionality required to fulfill the request.	501
server-error	Server Error	The server encountered an unexpected error	500
service-unavailable	Service Unavailable	The service is currently unavailable	503
Unauthorized	Unauthorized	Submitter ID is invalid or inactive	401