Could not parse http response unexpected token – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch encounters an unexpected token while parsing an HTTP response. This could be due to malformed JSON or incorrect data format. To resolve this issue, you can: 1) Check the JSON syntax for any errors and correct them. 2) Ensure the data format matches the expected format in Elasticsearch. 3) If you’re using a client library, ensure it’s compatible with your Elasticsearch version. 4) Check the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” could not parse http response. unexpected token [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: response, plugin.

Log Context

Log “could not parse http response. unexpected token [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 headers.put(headerName; values.toArray(new String[values.size()]));
 } else {
 throw new ElasticsearchParseException("could not parse http response. unexpected token [{}]"; token);
 }  if (status < 0) {
 throw new ElasticsearchParseException(


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?