QuickBooks API未返回刷新令牌及调用报错问题求助

Let's break down your two main issues and walk through actionable fixes for each:

1. Missing Refresh Token #

The #1 reason you're not receiving a refresh token is missing the required offline_access scope in your OAuth2 authorization request. QuickBooks explicitly requires this scope to issue a refresh token—without it, you’ll only get a short-lived access token with no way to refresh it.

Update your quickbook_params to include the offline access scope:

quickbook_params = {
  response_type: 'code',
  state: session[:state],
  scope: 'com.intuit.quickbooks.accounting offline_access' # Added offline_access
}

After making this change, re-authenticate your app. You should now see a refresh_token present in the resp object returned by client.access_token!.

2. 500 Internal Server Error When Fetching Customer #

A 500 error from QuickBooks' API can be vague, but these common checks will help you narrow it down:

a. Confirm the Customer ID Exists in Your Sandbox #

The endpoint /v3/company/$realm_id/customer/1 assumes a customer with ID 1 exists in your QuickBooks sandbox company. If this ID doesn’t exist, the API may return an unexpected 500 instead of a more descriptive 404. First, list all customers to get valid IDs:

curl -H "Authorization: bearer $auth_token" -H "Accept: application/json" "https://sandbox-quickbooks.api.intuit.com/v3/company/$realm_id/query?query=SELECT * FROM Customer"

Or in your Rails code:

customers = qbo_api.query("SELECT * FROM Customer")
# Inspect the customers response to find valid, existing IDs

b. Add Required Request Headers #

Your curl command is missing the Accept header, which tells QuickBooks what response format you expect. Without this, the API may struggle to process the request. Update your curl command:

curl -H "Authorization: bearer $auth_token" -H "Accept: application/json" "https://sandbox-quickbooks.api.intuit.com/v3/company/$realm_id/customer/VALID_CUSTOMER_ID"

Most QuickBooks API gems (like QboApi) handle this header by default, but it’s worth confirming the gem isn’t omitting it.

c. Capture Full Error Details #

Your current code swallows errors into a generic string, hiding critical debugging info. Modify your query page action to capture the full error context:

page_action :query do
  QboApi.log = true
  if ENV['QBO_API_ACCESS_TOKEN']
    qbo_api = QboApi.new(
      access_token: ENV['QBO_API_ACCESS_TOKEN'],
      realm_id: ENV['QBO_API_REALM_ID']
    )
    begin
      session[:qb_customer] = qbo_api.get :customer, 1
    rescue => e
      # Capture full error details for debugging
      session[:qb_customer] = "Error Message: #{e.message}\nFull Response: #{e.response.inspect}"
    end
  end
  redirect_to admin_quickbooks_path
end

This will show you the exact error message and raw response from QuickBooks, which could reveal issues like expired tokens, missing permissions, or sandbox data inconsistencies.

d. Validate Access Token & Realm ID #

Double-check that ENV["QBO_API_ACCESS_TOKEN"] and ENV["QBO_API_REALM_ID"] are set correctly. An expired or invalid access token can trigger unexpected server errors. You can verify your token’s validity using Intuit’s developer tools directly.

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