Troubleshooting Guide: How to Fix No MediaTypeFormatter is Available to Read an Object of Type Error

Encountering the "No MediaTypeFormatter is available to read an object of type" error in your project can be frustrating. This guide aims to help you understand and resolve this issue by providing step-by-step instructions and addressing frequently asked questions.

Table of Contents

  1. Understanding the Error
  2. Prerequisites
  3. Step-by-Step Solution
  4. FAQs
  5. Related Links

Understanding the Error

The "No MediaTypeFormatter is available to read an object of type" error typically occurs when you are using Web API in your .NET project. This error is caused by the inability of the Web API to deserialize the incoming request body to the expected object type.


  • .NET Framework or .NET Core installed on your machine
  • A Web API project in .NET where the error occurs

Step-by-Step Solution

Step 1: Identify the problematic MediaTypeFormatter

First, identify which MediaTypeFormatter is causing the issue. To do this, check your Web API project's configuration and look for the MediaTypeFormatters that are registered. The default ones are JsonMediaTypeFormatter and XmlMediaTypeFormatter.

Step 2: Inspect the Content-Type header

Inspect the incoming request's Content-Type header. Make sure it is set to a value that matches one of the registered MediaTypeFormatters. For example, if your API expects JSON data, the Content-Type header should be set to "application/json".

Step 3: Ensure the request body is valid

Ensure the request body is formatted correctly according to the Content-Type header. Invalid JSON or XML data can cause the MediaTypeFormatter to fail. You can use online tools like JSONLint or XML Validator to validate your data.

Step 4: Update MediaTypeFormatter settings

If the Content-Type header and request body are correct, you might need to update the MediaTypeFormatter settings in your Web API project. For example, if you are using the JsonMediaTypeFormatter, consider updating the JsonSerializerSettings to handle specific serialization requirements.

config.Formatters.JsonFormatter.SerializerSettings = new JsonSerializerSettings
    ContractResolver = new CamelCasePropertyNamesContractResolver(),
    DateFormatHandling = DateFormatHandling.IsoDateFormat,
    DateTimeZoneHandling = DateTimeZoneHandling.Utc

Step 5: Test the API

After making the necessary updates, test your API again to see if the error is resolved. If the issue persists, consider debugging your Web API project to identify any other potential issues.


Q1: Can I use custom MediaTypeFormatters in my Web API project?

Yes, you can create and use custom MediaTypeFormatters in your Web API project. This allows you to handle specific serialization or deserialization requirements that are not supported by the default MediaTypeFormatters.

Q2: Can I disable XML or JSON formatting in my Web API project?

Yes, you can disable specific MediaTypeFormatters in your Web API project. To do this, remove the MediaTypeFormatter from the global configuration. For example, to disable XML formatting, add the following line of code to your WebApiConfig class:


Q3: How can I support multiple formats in my Web API project?

To support multiple formats in your Web API project, register multiple MediaTypeFormatters in your configuration. The Web API will automatically select the appropriate MediaTypeFormatter based on the incoming request's Content-Type header.

Q4: Can I use MediaTypeFormatters with ASP.NET Core Web API?

Yes, MediaTypeFormatters are supported in ASP.NET Core Web API projects. However, the configuration process is slightly different. Instead of using the config.Formatters collection, you use the AddMvc or AddControllers extension methods to configure MediaTypeFormatters in the Startup class.

Q5: How can I troubleshoot MediaTypeFormatter issues in a production environment?

In a production environment, enabling logging and monitoring your application can help you identify and troubleshoot MediaTypeFormatter issues.

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.