Empty response with http status code 409

Clearance and Reporting
1

Hello,

We have recently started observing an issue when sending some documents to the reporting endpoint.
For certain requests we receive an HTTP Code 409, which normally indicates a duplicate document — however, the response body is completely empty.

According to the ZATCA documentation, in such cases the response body should contain an error structure similar to the following:

{
  "validationResults": {
    "infoMessages": [],
    "warningMessages": [],
    "errorMessages": [
      {
        "type": "ERROR",
        "code": null,
        "category": null,
        "message": "Invoice was already Reported successfully earlier.",
        "status": "ERROR"
      }
    ],
    "status": "ERROR"
  },
  "reportingStatus": "NOT_REPORTED"
}

But instead of receiving the expected JSON error response, we are consistently getting an empty response body, which causes processing errors on our side since the payload cannot be parsed.

Could you please advise why the reporting endpoint returns an empty body for HTTP 409 and whether this behavior is expected?
If not, is there a workaround or fix planned?

Thank you.

2

Ignore the response analysis when it is empty or inconsistent, when the response code is 409, and consider that the simplified invoice has been successfully reported and keep a note that you received an empty response from ZATCA.