Sage 200 API – 400 Bad Request

Posted on July 25, 2023
I have tried a Sage 200 API endpoint and it returned a 400 Bad Request error

What does the 400 Bad Request mean when you are using a Sage 200 API endpoint?

400 Bad Request

This occurs if the data that you are sending over is malformed or contains invalid fields and values. The API will attempt to return meaningful error messages relating to the cause of the first error it encounters. It is common for this to occur if incorrect foreign IDs are supplied in the body of a request.

https://developer.columbus.sage.com/docs#/uk/sage200extra/accounts/gs-what-makes-up-an-api-request

The 400 Bad request status code indicates that the server was unable to process the request due to invalid information sent by the client. In other words, the client request needs modification. https://www.uniprot.org/help/rest-api-headers

Resolution

You should check your API endpoint request and verify if there is any invalid information sent to the Sage 200 API server.

Have Questions?

How can automation help?

Automation helps your business become more efficient and perform better with less resources. So you can reduce on costs and time spent on repetitive menial tasks. Think of automation as a “Robot” that works 24/7 to improve your business performance, without the overheads of employing extra staff.