-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid Symbol Error with ByBit v5 API Integration #4822
Comments
Hello again. First of all, please post full code simple example for rerpoduce this error. |
Hello, and thank you for your response. To clarify, the issue with the I appreciate your assistance in investigating this matter further. |
Finally, I've resolved this issue. The root cause is that V5 API POST requests require JSON as params. The issue is not related to the symbol format. |
please check and close. |
Description:
The recent integration of ByBit v5 API support, as introduced in Pull Request #4771, appears to have a critical bug affecting symbol validation. Despite following the symbol format guidelines provided in ByBit's official API documentation, requests to create orders are failing with a "params error: symbol invalid" message. This issue has been identified and corroborated by multiple users, including @damiano1996.
Steps to Reproduce:
Implement a call to ByBit's v5 API for creating an order using the XChange library post-integration of PR #4771.
Ensure the symbol format adheres to the specifications in ByBit's official documentation.
Execute the call.
Expected Result:
The order is successfully created without errors, recognizing the symbol as valid.
Actual Result:
The call fails with the following error message: "params error: symbol invalid". This error persists even when using symbols that are clearly valid according to ByBit's official documentation.
Screenshots:
Screenshot demonstrating the error message:
Screenshot showing the attempted API call with the recommended symbol format:
Thanks!
The text was updated successfully, but these errors were encountered: