Do you use a custom WebApi formatter in your site?

The problem is probably related to a custom WebApi formatter used which interferes with the EditorialBoosting ApiController. The formatter converts all response properties to lowercase, but Find UI expects property names to be capitalized.

Hi Aniket!

We have code looking like this:

public static class WebApiConfig
{
	public static void Register(HttpConfiguration config)
	{
		// Web API configuration and services

		var formatter = GlobalConfiguration.Configuration.Formatters.JsonFormatter;
		formatter.SerializerSettings.ContractResolver = new CamelCasePropertyNamesContractResolver();

		// Web API routes
		...
	}
}

So my guess is that it interferes with the ApiController you mentioned.

What would - in your opinion - be the best way to handle this?

Can you confirm that removing the code resolves the issue? If it does, I would remove it and check how it affects your application. 

Removing the code does indeed resolve the issue. Thank you!

As for the CamelCasePropertyNamesContractResolver I decided to enforce it on the controller level rather than the global level.

Got inspiration from

https://stackoverflow.com/questions/19956838/force-camelcase-on-asp-net-webapi-per-controller/19959579

and

https://stackoverflow.com/questions/23504944/camel-casing-issue-with-web-api-using-json-net