使用RestSharp对接Spreadshirt API认证时遇内部服务器错误求助

Hey there! Let's work through that frustrating 500 error you're getting when trying to authenticate with the Spreadshirt API using RestSharp. I've dealt with similar API auth hiccups before, so here are the most likely fixes to try:

1. Fix the Request Body Format (Most Common Culprit) #

Spreadshirt's API almost certainly expects a JSON request body for session creation, but right now your code is sending parameters as form-urlencoded data. That mismatch is probably triggering the server error.

Since you mentioned having a Login class, use RestSharp's built-in JSON support to serialize it properly:

// First, make sure your Login class matches the API's expected fields exactly
public class Login
{
    public string username { get; set; } // Match the exact field name from the API docs
    public string password { get; set; }
}

var client = new RestClient("https://api.spreadshirt.net/api/v1");
var request = new RestRequest("sessions", Method.Post);

// Set the correct content type header
request.AddHeader("Content-Type", "application/json");

// Serialize your Login object directly into the request body
var loginCredentials = new Login { username = "foo", password = "bar" };
request.AddJsonBody(loginCredentials);

var response = client.Execute(request);

2. Verify Serialization Annotations #

If your Login class uses serialization attributes (like for System.Text.Json or Newtonsoft.Json), double-check that the field names match what Spreadshirt's API expects. For example:

// Using System.Text.Json
public class Login
{
    [JsonPropertyName("username")] // Explicitly map to the API's field name
    public string Username { get; set; }

    [JsonPropertyName("password")]
    public string Password { get; set; }
}

Mismatched casing or field names can silently break the request, leading to server-side errors.

3. Enable Request Logging to Debug #

To see exactly what's being sent to the API (and rule out formatting issues), enable RestSharp's logging:

// Add this before executing the request to log details to your console/debug output
client.Log = new ConsoleLogger();
client.UseSystemTextJson(); // Or UseNewtonsoftJson() if you prefer that serializer

This will show you the full request URL, headers, and body—you can compare this directly against the Spreadshirt API docs to spot discrepancies.

4. Double-Check Endpoint and API Version #

Quick sanity check: confirm the endpoint path (/api/v1/sessions) matches the exact path from the Spreadshirt security docs. Some API versions require additional context (like a shop ID prefix), but based on the docs you referenced, /sessions should be correct for v1.

5. Validate Your Credentials #

While a 500 error is usually a server-side issue, invalid or inactive credentials can sometimes trigger unexpected errors. Make sure your foo username and bar password are valid, and that your account has API access permissions enabled.

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