Ruby客户端提交ETH兑USD卖出订单时参数报错，疑与文档冲突

Hey Robin, let's work through this confusing issue you're facing with your Ruby client sell order call. When docs say one thing but code throws an error, it usually boils down to small mismatches between documentation, SDK behavior, or how you're passing parameters—here's how to unpack it:

First, Clarify API vs. SDK Discrepancies #

More often than not, the gap between docs and your error comes from one of these two scenarios:

• The general API documentation doesn't align with how the Ruby client SDK is implemented, or
• There's a tiny oversight in how you're structuring your parameters.

1. Check the Ruby Client's Specific Rules #

The official API docs might state you can use either amount or total, but Ruby gems sometimes have their own enforcement. For example:

• The SDK's place_sell_order method might require amount as a mandatory parameter, with total being an optional override (or vice versa).
• The gem might not actually support the total parameter at all—even if the raw API endpoint does.

Take a quick look at:

• The gem's README or inline method comments (run yard doc if it uses YARD documentation)
• The actual source code of the sell order method to see which parameters it accepts and validates.

2. Parameter Combination Best Practices #

Most crypto exchange APIs follow these rules for sell orders:

• You should not pass both amount and total—they're mutually exclusive. If you send both, the server might throw an error or prioritize one over the other (which is probably not what you intend).
• The account parameter is almost always required (to specify which wallet/account you're selling from). Make sure you're passing this correctly—if it's missing, the error might manifest as a parameter issue even if your total is set properly.

3. Use the Error Message to Narrow It Down #

You didn't share the exact error text, but it's your most valuable clue:

• If the error says something like missing parameter: amount, that means the Ruby SDK is enforcing amount as required, even if the API docs say otherwise.
• If it says invalid parameter: total, the SDK or API might not actually support this parameter (so the docs are likely outdated).
• If it's an account-related error, double-check that your account ID is correct and has sufficient ETH balance.

4. Test with Raw API Calls (Bypass the SDK) #

To confirm whether the issue is with the SDK or the API itself:

• Use curl to send a raw POST request to the Place sell order endpoint, using only total and account parameters (plus any required auth headers):

  curl -X POST "https://api.your-exchange.com/sell" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"account": "your_account_id", "total": "100", "base_currency": "ETH", "quote_currency": "USD"}'
  

• If this request succeeds, the problem is definitely in the Ruby client. If it fails, the docs are likely incorrect, or you're missing another required parameter.

Final Takeaway #

My guess is either the Ruby SDK doesn't fully support the total parameter (despite the API docs), or you accidentally passed both amount and total in your call. Start by checking the SDK's parameter requirements and your code for conflicting params, then use the error message to zero in on the exact issue.

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