求助：第三方API返回JSON的ASCII转义字符转特殊字符问题

Fixing Unicode Escape Sequences in Third-Party API Responses #

Hey there! I get it, dealing with those escaped Unicode characters (like \u00e1 or \u00e3) in a third-party API response can be frustrating when you can’t tweak the backend. The good news is this is a standard JSON format quirk, and we can easily decode these sequences on the client side to get the proper UTF-8 characters you expect.

Why the Accept Header Didn’t Work #

First, a quick clarification: those \uXXXX sequences are valid Unicode escape sequences defined by the JSON spec. The server is already returning UTF-8 encoded JSON—they just chose to represent non-ASCII characters with escape codes instead of raw bytes. Setting the Accept header won’t change this behavior, since the response is technically compliant with UTF-8 standards. The fix has to happen on your end during JSON parsing.

Solutions by Programming Language #

Below are practical fixes for the most common languages you might be using:

Python

If you’re using requests, the library automatically handles these escapes when you use .json() to parse the response:

import requests

response = requests.get("your-api-endpoint-url")
parsed_data = response.json()
print(parsed_data["message"])  # Outputs: "Usuário não encontrado"

If you’re working with a raw JSON string directly, use the built-in json module—it decodes escape sequences by default:

import json

raw_json_str = '{"message": "Usu\u00e1rio n\u00e3o encontrado", "status": "fail"}'
parsed_data = json.loads(raw_json_str)
print(parsed_data["message"])

JavaScript (Browser/Node.js)

The native JSON.parse() function in JavaScript automatically resolves Unicode escape sequences. Whether you’re using fetch or handling raw strings, this works out of the box:

// For raw JSON strings
const rawJson = '{"message": "Usu\u00e1rio n\u00e3o encontrado", "status": "fail"}';
const data = JSON.parse(rawJson);
console.log(data.message); // Outputs: "Usuário não encontrado"

// For fetch API calls
fetch("your-api-endpoint-url")
  .then(res => res.json())
  .then(data => console.log(data.message));

Java

Popular JSON libraries like Gson or Jackson will decode these escape sequences automatically during parsing. Here’s an example with Gson:

import com.google.gson.Gson;

public class ApiResponseHandler {
    public static void main(String[] args) {
        String rawJson = "{\"message\": \"Usu\\u00e1rio n\\u00e3o encontrado\", \"status\": \"fail\"}";
        
        Gson gson = new Gson();
        ApiResponse response = gson.fromJson(rawJson, ApiResponse.class);
        
        System.out.println(response.getMessage()); // Outputs: "Usuário não encontrado"
    }

    // Simple POJO to map the response
    static class ApiResponse {
        private String message;
        private String status;

        public String getMessage() { return message; }
        public void setMessage(String message) { this.message = message; }
        public String getStatus() { return status; }
        public void setStatus(String status) { this.status = status; }
    }
}

Key Takeaway #

Don’t waste time trying to get the backend to change its output—these escape sequences are valid JSON. The solution is to use your language’s standard JSON parsing tools, which are designed to handle exactly this scenario and convert those escape codes into readable UTF-8 characters.

内容的提问来源于stack exchange，提问作者Rafael Lima