调用QuickBooks API返回400状态码问题排查求助

Hey there, let's work through this 400 error you're facing with the QuickBooks API. I've looked over your code and the details you shared, so here are the most likely fixes and things to check:

1. Fix the Token Format (Critical!) #

Looking at your callback function, you're storing the token as a stringified JSON object:

oauth2_token_json = JSON.stringify(authResponse.getJson(), null, 2);
newToken = oauth2_token_json;

But the QuickBooks Node SDK expects a parsed JSON object for the token parameter, not a string. When you pass the string to the QuickBooks constructor, the SDK can't properly extract the access_token, refresh_token, and other required fields—this is a common cause of 400 errors.

Update your callback code to save the parsed token object instead:

app.get('/callback', function (req, res) {
  oauthClient
    .createToken(req.url)
    .then(function (authResponse) {
      // Store the parsed JSON object, not a string
      newToken = authResponse.getJson();
      oauthClient.setToken(newToken);
      const tokenString = JSON.stringify(newToken, null, 2);
      console.log("Token:", tokenString);
      res.send(tokenString);
    })
    // Add error handling here to catch token creation issues
    .catch(function(err) {
      console.error("Failed to create token:", err);
      res.status(500).send("Token creation failed: " + err.message);
    });
});

2. Verify Your Realm ID Is Up-to-Date #

You mentioned you created a new sandbox environment—the realm ID for your new sandbox is different from the old one. Double-check that the 5th parameter in your QuickBooks constructor ('4620816365092507370') is the correct realm ID for your new sandbox. Using an outdated realm ID will almost certainly throw a 400 or 403 error.

3. Validate the Customer Payload #

400 errors often stem from invalid request bodies. Let's rule out payload issues:

• Use the QuickBooks Sandbox API Explorer to test your customer JSON directly. This will tell you if any fields are missing, formatted incorrectly, or violate QB's schema.
• Check for duplicate values: FullyQualifiedName must be unique across your sandbox. If you already created a "King Groceries" customer before, this will cause a conflict.
• Ensure all enum fields (like Suffix) match QB's allowed values—"Jr" is valid, but double-check for typos.

4. Use Debug Logs to Get Specific Error Details #

You enabled debugging in the SDK (true for the 7th parameter)—make sure you're checking the full console output. The SDK will print the exact request body sent to QB, as well as the detailed error response from the API. This response will usually tell you exactly what's wrong (e.g., "Invalid access token", "Duplicate FullyQualifiedName", or "Missing required field").

Here's the updated create customer code with better error handling to capture these details:

.then(() => {
  const qbo = new QuickBooks(
    'ABReS9hFdUzNlD8Np17ufW8WU5xLyL0M0rv3HvekbXJdZUiWzi',
    'Uy9NXu2fKmumP3JoCrxKxKugzLkdHhi8Ca00GSBz',
    newToken, // Now passing the parsed token object
    false,
    '4620816365092507370', // Confirm this is your new sandbox's realm ID
    true,
    true,
    null,
    '2.0',
    null
  );

  qbo.createCustomer({
    "FullyQualifiedName": "King Groceries",
    "PrimaryEmailAddr": { "Address": "jdrew@myemail.com" },
    "DisplayName": "King's Groceries",
    "Suffix": "Jr",
    "Title": "Mr",
    "MiddleName": "B",
    "Notes": "Here are other details.",
    "FamilyName": "King",
    "PrimaryPhone": { "FreeFormNumber": "(555) 555-5555" },
    "CompanyName": "King Groceries",
    "BillAddr": {
      "CountrySubDivisionCode": "CA",
      "City": "Mountain View",
      "PostalCode": "94042",
      "Line1": "123 Main Street",
      "Country": "USA"
    },
    "GivenName": "James"
  }, function(err, customer) {
    if (err) {
      // Log the full error to see QB's specific feedback
      console.error("Error creating customer:", err);
      return;
    }
    console.log("Created customer:", customer);
  });
})
// Catch any errors in the promise chain
.catch(err => {
  console.error("Promise chain error:", err);
});

Start with fixing the token format first—this is the most probable culprit. Then verify the realm ID and check the debug logs for specific error messages. That should get you past the 400 error.

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