Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

REST API - Error Messages and Warning Messages - Two Extra Fields

The REST APIs would be A LOT easier to work with if there were two additional fields returned. Let's just call them message1 and message2.

These two fields would correspond with the same information that you get when you enter data into a screen. When you enter data into a screen in Acumatica, you either get a Warning (in yellow) or an Error (in red).

message1 would return either "warning" or "error".

message2 would return the same message that you get on the screen.


For example, let's say I try to enter the following bad data into the Sales Orders screen. In this example:

message1 = "error"

message2 = "Error: 'Location' cannot be found in the system."


If I try to enter the same bad data into the REST API, I get an error message. But it's really ugly. The relevant message is there (highlighted in red below), but it's buried in a bunch of technical vomit.


It would be great if we could get two fields that give us the same data we would see on the screen. It would make working with the REST APIs a lot easier.

Also, I'm told there is a similar problem with the SOAP APIs.

  • Tim Rodman
  • Jan 27 2019
  • Future consideration
  • Attach files
  • Vladimir Panchenko commented
    January 31, 2019 17:44

    Thanks Tim,

    Makes total sense. We'll think about implementing it in the future.