JSONError: No data, empty input at 1:1 with empty Scripts

Hi everyone,
I’m encountering a strange issue in Postman and I haven’t been able to find a clear explanation for it.

I’m making a simple GET request to an internal API.
The request works correctly and the server returns:

  • HTTP 206 Partial Content (this is expected)

  • Content-Length: 20

  • No body

  • Content-Encoding: gzip

  • Response body visually empty in Postman

Example response headers:

HTTP/1.1 206 Partial Content
Content-Encoding: gzip
Content-Length: 20
Connection: Keep-Alive

However, in the Test tab, Postman always marks the request as failed, showing this error:

JSONError: No data, empty input at 1:1

This happens even if I delete all test code and leave the Test script completely empty.

It seems like Postman attempts to automatically parse the response body as JSON because of the gzip encoding, even though the decompressed body is empty…and the Test tab fails before my test script even runs.

I can’t modify backend behaivour.

I tried forcing the server not to send compressed responses by explicitly adding:

Accept-Encoding: identity

This worked as expected on the network side (the server stopped sending gzip and returned:

Content-Length: 0
Content-Encoding:  (absent)

However, the behavior in Postman remained exactly the same:

  • Response is 206 OK

  • Body is 100% empty

  • Script is empty

  • Test Results failing with “JSONError: No data, empty input at 1:1“

So disabling gzip did not resolve the issue.

Anybody can help me with this? Sorry for my english

Hey @juanjavierrg.gfi :waving_hand:

Welcome to the Postman Community! :postman:

Could you check to see if you have anything in the Collection or Folder level scripts?

If you have something there that is trying to parse the response as JSON, this would show that error if the response is empty.

Yep, that was it.
I already had a test defined at the collection level, and it was driving me crazy.

1 Like