Expected object but found instead – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch expects a JSON object in the request body but finds an empty object “{}” instead. This could be due to a malformed or empty request body. To resolve this issue, ensure that the request body contains a valid JSON object. Check your application code to ensure that it’s correctly formatting the request. If you’re manually sending requests, ensure that the JSON is correctly structured and not empty. Also, ensure that the correct HTTP method (GET, POST, PUT, DELETE) is being used for the request.

This guide will help you check for common problems that cause the log ” expected object but found {} instead ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “expected object but found {} instead” class name is PutPrivilegesRequestBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 XContentParser.Token token = parser.currentToken();
 if (token == null) {
 token = parser.nextToken();
 if (token != XContentParser.Token.START_OBJECT) {
 throw new ElasticsearchParseException("expected object but found {} instead"; token);
 }  List privileges = new ArrayList<>();
 while (parser.nextToken() != XContentParser.Token.END_OBJECT) {
 token = parser.currentToken();


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?