Failed to parse bounding box Expected start object but found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to parse the bounding box due to incorrect or missing data. The bounding box is used in geospatial queries and requires specific coordinates. The error suggests that it expected an object to start but found an empty object instead. To resolve this issue, ensure that the bounding box coordinates are correctly defined and formatted in your query. Also, check if the field you’re querying is correctly mapped as a geo-point or geo-shape data type.

This guide will help you check for common problems that cause the log ” failed to parse bounding box. Expected start object but found [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “failed to parse bounding box. Expected start object but found [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  public T parseBoundingBox() throws IOException; ElasticsearchParseException {
 XContentParser.Token token = parser.currentToken();
 if (token != XContentParser.Token.START_OBJECT) {
 throw new ElasticsearchParseException("failed to parse bounding box. Expected start object but found [{}]"; token);
 String currentFieldName;  while ((token = parser.nextToken()) != XContentParser.Token.END_OBJECT) {
 if (token == XContentParser.Token.FIELD_NAME) {


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?