JSONFormatter | JSON - HTML Formatter | JSON Processing library

Controller doesn't know what the name of your route value - is it item_code or id. I recommend you to use this route attributes:

Loading like this in Python you will need to double the backslashes on the Message line. The slash that you have there currently will be used to create the string. You can see this by doing a print of st

However the better way to do this would be to not have st as a string but a dictionary (i.e. remove the triple quotes), then you don't need to mess around with the json library at all here

Your problem has nothing to do with how you are registering your global settings -- setting config.Formatters.JsonFormatter.SerializerSettings.ContractResolver is correct as per this question. Your problem is that Json.NET does not call ResolvePropertyName() when the contract resolver also has a NamingStrategy -- and your base class CamelCasePropertyNamesContractResolver does indeed have a naming strategy.

This can be verified by checking the current Json.NET reference source for DefaultContractResolver.SetPropertySettingsFromAttributes():

If you want to debug the error use breakpoint(), this way you will get an interactive console where you can type in the variable and see its value.

If you want to log the request object modify your JsonFormatter like this

One way is to write your own formatter. Start from e.g. the JsonFormatter and only use those parts that are valid for your requirements.

According to serilog console sink documentation you need to specify formatting inside Args property

There are multiple issues with your text. I will try to elabroate on them in the following parts...

Quite obvious to all of us - this just should not be there

Since your json object starts with [ it's actually a string list, that has to be separated by ,, e.g. ["a", "b", "c"], which is probably the reason for the next point...

First of all the following is kind of a mixture of a string list and a json object

Here is your Valid JSON, it was the array symbol creating the issue. Array closing was missing before edu_data key.

You appear to have encountered a limitation in Json.NET's support for {propertyName}Specified members: the {propertyName}Specified property is not set when populating an instance of a preallocated reference type property. As a workaround, you can deserialize with the setting JsonSerializerSettings.ObjectCreationHandling = ObjectCreationHandling.Replace. If you do, new instances of reference type properties will be created by the serializer and set back after creation, thereby toggling the corresponding {propertyName}Specified property.

A detailed explanation follows. In your Person type, you automatically allocate instances of the child properties Address and Details in the default constructor: