If you are building web APIs or making HTTP requests, you have likely run into the question: which json content type do i use? Setting the correct header ensures that both the client and server understand how to parse and decode the data being sent.

In this guide, we will answer which json content type do i use according to official IETF standards, address the UTF-8 charset debate, and show code examples of how to set this header in major programming languages.

The Official JSON Content Type: application/json

The standard and universally accepted Content-Type for JSON data is:

Content-Type: application/json

This MIME type is registered in the official IETF RFC 8259 specification. Whenever a client sends an HTTP request with a JSON body (e.g., in a POST or PUT request) or when a server returns a JSON response, this header must be included to prevent parsing errors.

Do I Need to Include charset=utf-8?

A common question developers ask is whether they should use application/json; charset=utf-8 instead of just application/json.

According to RFC 8259, **JSON text MUST be encoded in UTF-8** when exchanged between systems. Because UTF-8 is the default and mandatory encoding, appending the charset parameter is redundant and technically not defined by the specification. However, some legacy systems or poorly configured web clients might still require it to parse special characters correctly. As a best practice, stick to the clean application/json header unless integrating with older systems.

Comparing JSON with Other Content Types

To help you understand which json content type do i use in different contexts, here is how it compares to other common HTTP request types:

How to Set JSON Content-Type (Code Examples)

Below are copy-pasteable examples of how to set this header in different front-end and back-end environments:

1. JavaScript (Fetch API)

When sending data from a browser, set the headers object in your fetch configuration:

fetch('https://api.example.com/data', {
    method: 'POST',
    headers: {
        'Content-Type': 'application/json'
    },
    body: JSON.stringify({
        username: 'john_doe',
        role: 'developer'
    })
});

2. PHP Response Header

When writing a backend API in PHP, send the header before outputting any content:

<?php
// Set content type header
header('Content-Type: application/json');

$data = [
    'status' => 'success',
    'message' => 'Data retrieved successfully'
];

echo json_encode($data);
exit;
?>

3. Python Flask API

In Python’s Flask framework, the jsonify function automatically serializes your dictionary and sets the correct header:

from flask import Flask, jsonify

app = Flask(__name__)

@app.route('/api/user')
def get_user():
    user_data = {
        "id": 101,
        "name": "Jane Smith"
    }
    # Flask automatically sets Content-Type to application/json
    return jsonify(user_data)

4. ASP.NET MVC / C#

In ASP.NET MVC, returning a JsonResult automatically handles the response header setting:

public JsonResult GetUserData()
{
    var user = new { Id = 101, Name = "Jane Smith" };
    // Automatically returns JSON with application/json header
    return Json(user, JsonRequestBehavior.AllowGet);
}

Summary

When transmitting data, always default to application/json as your standard MIME type. For more information on how data is prepared for transmission, see our detailed guide on JSON Serialization in JavaScript.