How to Set the Content-Type Header with HttpClient in C#

By the end of this page, you will understand why Content-Type cannot be added to HttpClient.DefaultRequestHeaders, how Content-Type belongs to the request body instead of the client itself, and how to correctly send JSON using StringContent, HttpRequestMessage, and PostAsync in C#.

HttpClient has different kinds of headers, and each one belongs in a specific place.

• Request headers describe the overall HTTP request.
• Content headers describe the request body.
• Response headers describe the server response.

The key idea is this:

• Accept is a request header. It tells the server what response format you want back.
• Content-Type is a content header. It tells the server what format the body you are sending uses.

That is why this works:

httpClient.DefaultRequestHeaders.Add("Accept", "application/json");

But this fails:

httpClient.DefaultRequestHeaders.Add("Content-Type", "application/json");

DefaultRequestHeaders is only for headers that belong to the request itself. Since Content-Type describes the body, it must be placed on an HttpContent object such as StringContent, ByteArrayContent, or FormUrlEncodedContent.

Think of an HTTP request like sending a package.

• The request headers are the shipping instructions on the outside of the box.
• The content is what is inside the box.
• The Content-Type label belongs on the item inside, not on the shipping company.

So:

• Accept: application/json means: “Please send me JSON back.”
• Content-Type: application/json means: “The data I am sending to you is JSON.”

If there is no body, then there is usually no Content-Type to set.

The most common way to set Content-Type is to create an HttpContent object with the correct media type.

Sending JSON with StringContent

using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main()
    {
        using var httpClient = new HttpClient();
        httpClient.BaseAddress = new Uri("http://example.com/");
        httpClient.DefaultRequestHeaders.Add("Accept", "application/json");

        var json = "{\"name\":\"Alice\"}";
        var content = new StringContent(json, Encoding.UTF8, "application/json");

        HttpResponseMessage response = await httpClient.PostAsync("users", content);
        string result = await response.Content.ReadAsStringAsync();

        Console.WriteLine(result);
    }
}

Why this works

• Accept is added to because it is a request header.

Consider this example:

using var httpClient = new HttpClient();
httpClient.DefaultRequestHeaders.Add("Accept", "application/json");

var json = "{\"id\":1}";
var content = new StringContent(json, Encoding.UTF8, "application/json");

var response = await httpClient.PostAsync("http://example.com/items", content);

Here is what happens step by step:

1. new HttpClient() creates a client for sending HTTP requests.

2. DefaultRequestHeaders.Add("Accept", "application/json") tells the server that JSON is the preferred response format.

3. json stores the request body as a JSON string.

4. new StringContent(...) wraps that string in an HttpContent object.

5. Encoding.UTF8 tells .NET how to encode the text into bytes.

6. "application/json" sets the content header:

This pattern is used any time you send data to an API.

Common examples

• Create a user

  • Send JSON like { "name": "Alice" }
  • Use Content-Type: application/json

• Submit a login form

  • Send form fields such as username and password
  • Use application/x-www-form-urlencoded

• Upload a file

  • Send multipart form data
  • Use multipart/form-data

• Send XML to a legacy API

  • Use application/xml or text/xml

Example: form data

var formData = new FormUrlEncodedContent(new[]
{
    new KeyValuePair<string, string>("username", "alice"),
    new KeyValuePair<string, string>(, )
});

 response =  httpClient.PostAsync(, formData);

In real projects, developers usually do not manually add Content-Type as a raw string to the client. Instead, they create the right HttpContent type for the payload they are sending.

Common patterns

1. JSON API calls

var payload = JsonSerializer.Serialize(new { name = "Alice" });
var content = new StringContent(payload, Encoding.UTF8, "application/json");
var response = await httpClient.PostAsync("users", content);

2. Guard clauses before sending

if (string.IsNullOrWhiteSpace(payload))
{
    throw new ArgumentException("Payload cannot be empty.");
}

This avoids sending invalid requests.

3. Validation of responses

response.EnsureSuccessStatusCode();

This throws if the server returns an error status.

4. Reusable helper methods

  Task<HttpResponseMessage> ()
{
     json = JsonSerializer.Serialize(data);
     content =  StringContent(json, Encoding.UTF8, );
      _httpClient.PostAsync(url, content);
}

1. Setting Content-Type on DefaultRequestHeaders

This is the exact mistake from the question.

Broken

httpClient.DefaultRequestHeaders.Add("Content-Type", "application/json");

Fix

var content = new StringContent(json, Encoding.UTF8, "application/json");

2. Confusing Accept with Content-Type

Beginners often think these mean the same thing.

• Accept = what you want to receive
• Content-Type = what you are sending

Example

httpClient.DefaultRequestHeaders.Add("Accept", "application/json");
var content = new StringContent(json, Encoding.UTF8, "application/json");

3. Forgetting to attach the content to the request

Broken

Quick rules

• Accept goes in request headers.
• Content-Type goes on the request content.
• Do not add Content-Type to HttpClient.DefaultRequestHeaders.
• If there is no request body, there is usually no Content-Type.

Most common JSON pattern

var json = JsonSerializer.Serialize(data);
var content = new StringContent(json, Encoding.UTF8, "application/json");
var response = await httpClient.PostAsync(url, content);

Set Accept

httpClient.DefaultRequestHeaders.Add("Accept", "application/json");

Set Content-Type

var content = new StringContent(json, Encoding.UTF8, "application/json");

Manual content type

Why does adding Content-Type to DefaultRequestHeaders throw an exception?

Because Content-Type is a content header, not a general request header. It must be set on an HttpContent object.

Can I set Content-Type for a GET request?

Usually no, because a normal GET request does not have a body. Content-Type describes the body being sent.

What is the difference between Accept and Content-Type?

Accept tells the server what response format you want. Content-Type tells the server the format of the request body you are sending.

How do I send JSON with HttpClient in C#?

Use StringContent with UTF-8 encoding and application/json, or use PostAsJsonAsync in newer .NET versions.

Is StringContent the only way to set ?

• HttpClient — the main class used to send HTTP requests in C#.
• HTTP headers — useful for understanding the difference between request, response, and content headers.
• HttpRequestMessage — gives more control when building custom requests.
• HttpContent — the base type for request bodies and content headers.
• JSON serialization — commonly used before sending JSON in request bodies.
• POST requests — often used when Content-Type matters because data is being sent.
• REST APIs — many REST endpoints require correct Content-Type values.
• PostAsJsonAsync — a higher-level helper for sending JSON more easily.