如何使用HttpClient获取Bearer Token？Postman调用指定API成功但C#代码实现失败，请求排查是否缺少请求头

Hey there! It’s super common to hit discrepancies between Postman and C# HTTP requests—let’s break down why your token call might be failing and how to fix it.

The Likely Culprit: Request Body Format #

From your code, I notice you’re sending client credentials as JSON, but most OAuth2 client_credentials grant endpoints (including many MuleSoft-powered services like NZ Post’s) expect the request body to be in application/x-www-form-urlencoded format. Postman probably defaulted to this format when you set up the request, which is why it worked there but not in your C# code.

Fixing the Code #

Here’s how to adjust your GetToken method to match what Postman is doing:

public static async Task<HttpResponseMessage> GetToken()
{
    // Use form-urlencoded data instead of JSON—this aligns with OAuth2 spec for client_credentials
    var formData = new Dictionary<string, string>
    {
        { "client_id", "xxxxxxxxxxxxxxxxxxxxxxxxx" },
        { "client_secret", "xxxxxxxxxxxxxxxxxxxxxx" },
        { "grant_type", "client_credentials" }
    };

    var content = new FormUrlEncodedContent(formData);
    // Wrap HttpClient in using to properly manage resources
    using var client = new HttpClient();

    // Optional but helpful: Explicitly tell the server we accept JSON responses
    client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));

    var response = await client.PostAsync("https://oauth.xxxx.co.nz/as/token.oauth2", content);
    return response;
}

Additional Checks to Rule Out Other Issues #

• Verify credentials: Double-check that your client_id and client_secret are copied correctly (no extra spaces or typos). The FormUrlEncodedContent handles special character encoding automatically, so you don’t have to worry about manual escaping.
• Compare with Postman’s generated code: A quick way to spot gaps is to use Postman’s built-in code generator. After sending your successful token request in Postman, click the Code button (top-right corner), select C# - HttpClient, and compare that code with yours. It’ll show you exactly what headers/format Postman uses under the hood.
• Check for required custom headers: While rare for client_credentials, some services might require extra headers (like a custom X-API-Key). Double-check the NZ Post API docs to confirm if any additional headers are needed for the token endpoint.

Quick Debug Tip #

After updating the code, inspect the response content to get specific error details:

var response = await client.PostAsync(...);
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);

This will show you server-side error messages (like "invalid grant type" or "invalid credentials") that can pinpoint exactly what’s going wrong.

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