Bybit API Discussion

@BybitAPI
Latest publications
Publication date:
16 Jan, 04:26
Which coin is showing the most movement, so that we can test the liquidation/stop-loss / take profit / market order etc features at speed and ensure effective testing? @kolya5544
💬 0 Publication date:
16 Jan, 00:19
This chat can only assist with Bybit API issues. For issues with Bybit P2P, please contact Customer Support: https://www.bybit.com/en/help-center/s/webform
Publication date:
16 Jan, 00:18
How to fill out the Verified Redvisor application?
💬 1 Publication date:
15 Jan, 22:45
Unfortunately it's not possible, as automated taker trading is currently not supported.
Publication date:
15 Jan, 22:44
Thanks for clarifying! Quick context: I already have General Advertiser status ✅
However, my strategy requires TAKER automation (responding to ads), not creating my own ads.
Direct questions:
1️⃣ Is there ANY official way to automate P2P taker operations?
• Undocumented endpoint with proper auth?
• Webhook/WebSocket for real-time ad notifications?
• Planned roadmap feature?
2️⃣ If P2P taker is impossible, should I use Unified Trading API (Spot) instead?
• Which pairs for arbitrage? (USDT/USDC, USDT/FDUSD?)
• Does it support full taker automation?
3️⃣ Can I monitor P2P via API (read-only) then execute on Spot?
Or would this violate policies?
Why maker doesn't work for me:
❌ Too slow (need instant execution)
❌ Capital inefficient (locked in ads)
❌ No control over fill timing
I need: "See opportunity → Execute instantly"
What's the official Bybit solution for automated buy-low-sell-high trading?
Thanks! 🙏
Publication date:
15 Jan, 22:28
Bybit P2P API cannot be used to open orders, it's a tool for P2P makers and lacks taker features. It can only be used to manage ads and existing orders.
Additionally, yes, a General Advertiser status is required to access P2P API.
Publication date:
15 Jan, 22:26
I'm developing an automated P2P trading bot using the official bybit_p2p Python SDK and would like to confirm that my implementation complies with Bybit's Terms of Service and API usage policies.
📋 What I'm Building
A Telegram bot for automated P2P trading (USDT/USD) with the following features:
Core Functionality:
Scanning P2P market ads using get_online_ads() endpoint
Analyzing spread opportunities between buy/sell prices
Executing trades when profitable opportunities are detected
Managing orders, balance, and account information
Filtering merchants by completion rate, order count, and verification status
Technical Implementation:
Using official Bybit P2P SDK (bybit-p2p>=1.1.0)
HMAC-SHA256 authentication with API keys
Proper rate limiting and error handling
Database logging of all transactions
Proxy usage (already confirmed as allowed)
Trading Strategy:
Buy USDT when price ≤ $0.999
Sell USDT when price ≥ $1.000
Target spread: 0.1%+
Using "USD Balance" payment method (no bank transfers)
Daily limits per merchant to prevent excessive trading
❓ Specific Questions
1. API Rate Limits
What are the rate limits for P2P endpoints (/v5/p2p/item/online, etc.)?
Is scanning the market every 30 seconds acceptable, or should I increase the interval?
Are there specific headers I should use to identify my bot?
2. Automated Trading Compliance
Is automated P2P trading allowed on Bybit?
Do I need special permissions or account verification to run an automated trading bot?
Are there any restrictions on the number of daily trades or volume?
3. API Permissions
My API key has "P2P Trading" and "Read" permissions enabled
Is this sufficient, or do I need additional permissions?
Should I enable IP whitelist? (I use rotating proxies)
4. Best Practices
Should I implement exponential backoff for failed requests?
Is there a recommended way to handle retCode: 10004 errors?
Any specific requirements for production bots vs. testing?
5. Account Requirements
Do I need "General Advertiser" status or higher for automated trading?
Are there minimum KYC levels required?
Can I use Testnet for initial testing without affecting my main account?
🛠 Current Implementation Details
Endpoints Used:
POST /v5/p2p/item/online - Get market ads
GET /v5/account/wallet-balance - Check USDT balance
GET /v5/p2p/account/info - Get P2P account info
GET /v5/p2p/order/list - Get order history
SDK Version: bybit-p2p==1.1.0
Authentication: HMAC-SHA256 with API Key & Secret
Environment:
VPS (Ubuntu 24.04)
Python 3.11+
Mainnet (production)
✅ What I've Already Confirmed
✅ Using proxies with proper rotation is allowed
✅ API keys are correctly configured
✅ Manual testing works perfectly with the SDK
🙏 Request for Clarification
Could you please confirm:
Is my use case compliant with Bybit's Terms of Service?
Are there any modifications I should make to ensure compliance?
Are there official guidelines or documentation for building P2P trading bots?
Should I register my bot or notify Bybit before going live?
📧 Additional Information
I'm happy to provide:
Sample code snippets
API request logs
Bot configuration details
Any other information needed for review
Thank you for your time and assistance. I want to ensure my implementation is fully compliant before deploying to production.
Best regards, Zolu
💬 3 Publication date:
15 Jan, 22:19
Yes, you can use any proxy server of your liking, but note that official libraries usually do not natively support such feature. So you have to use external tools to route your requests through a proxy server, or modify the requests session directly
Publication date:
15 Jan, 22:18
Can requests be made with a proxy?
💬 1
Russian
