We will release an update to our API which starts to enforce stricter validation of incoming requests. In the past we were rather tolerant on the requests we were accepting, even requests which did not conform to our documentation or conform to the HTTP standards. We are in the process of being stricter on what we accept. This is *not* a breaking change or an API upgrade as we will still accept the requests as were documented but we will start rejecting invalid requests.
However some customers are being impacted by this change resulting in an Error 400 when creating a request, what we have seen happening is customers using undocumented features such as:
- for an `application/json` request, the body included an UTF-8 BOM header
- sending a Content-Type HTTP header for GET requests
- including fields or properties with an explicit "null" as a value, if you want a field or property to use the default value, you should just omit the field.
If you are conforming to our documentation and the HTTP specifications you should not be impacted. To make sure you are not impacted we have a testing environment available. A simple call to this endpoint confirms if you are compatible or not. Please contact support via firstname.lastname@example.org
, phone or chat to get information on this testing endpoint. Due to the fact that we think little customers are impacted we planned the change for 21th of November, so we strongly recommend to valid the request on the short term.
Nov 11, 14:05 CET