Complete documentation of Binance P2P API key registration issue and resolution process
This repository documents a critical Binance P2P API key registration bug where valid API credentials fail on specific P2P endpoints with -2008 Invalid Api-Key ID error, despite working correctly on other endpoints.
- Progress: 3/6 endpoints now working (50% success rate, up from 16.7%)
- Backend Changes: Binance team actively deploying fixes - endpoints fluctuating between working/failing
- Support Escalation: CS Sergei U (Merchant Team) now handling case with technical expertise
- Evidence: Multiple API key generations show backend modifications in progress
- Issue Type: Backend API key registration problem (Binance-side)
- Current Status: Backend fix deployment in progress (confirmed by endpoint fluctuations)
- Working Endpoints:
/getAds,/getUserOrderSummary,/getAvailableAdsCategory(intermittent) - Support Case: #144098731 (escalated to Merchant Team)
- Timeline: Active backend development confirmed July 9, 2025
- Support Timeline - Complete case history including CS Sergei escalation
- Backend Progress Evidence - July 9, 2025 fluctuation documentation
- API Validation Report - Detailed testing results
- Audit Results - Comprehensive endpoint testing
- Failing Endpoints Test - Demonstrates the bug
- Working Endpoint Test - Proves credentials work
- Requirements - Python dependencies
- Original Binance Guides - Official documentation from support
- Security Policy - Responsible disclosure information
- Contributing Guidelines - How to contribute
# This works ✅
curl -X GET "https://api.binance.com/sapi/v1/c2c/ads/getAds?..."
# Returns: 200 OK with valid data
# This fails ❌
curl -X POST "https://api.binance.com/sapi/v1/c2c/ads/search?..."
# Returns: {"code":-2008,"msg":"Invalid Api-Key ID."}- Same API Key: Both requests use identical credentials
- Correct Format: Request structure follows Binance documentation exactly
- Selective Failure: Only affects specific P2P endpoints
- Consistent Pattern: Multiple merchants report identical issue
curl --location 'https://api.binance.com/sapi/v1/c2c/ads/search?recvWindow=5000×tamp={timestamp}&signature={signature}' \
--header 'X-MBX-APIKEY: {api_key}' \
--header 'Content-Type: application/json' \
--data '{
"asset": "USDT",
"fiat": "USD",
"page": 1,
"rows": 10,
"tradeType": "BUY"
}'- Signature Scope: Only
recvWindow,timestampin query string - Body Parameters: All trading parameters in JSON body
- Headers:
X-MBX-APIKEYandContent-Type: application/json - Algorithm: HMAC-SHA256 from query string only
pip install -r test/requirements.txt# Test the working endpoint (should succeed)
python test/test_working_endpoint.py
# Test the failing endpoints (will show -2008 error)
python test/test_failing_endpoints.py- Working endpoint: Returns marketplace data ✅
- Failing endpoints: Return
-2008 Invalid Api-Key ID❌
| Feature | Status | Latest Change |
|---|---|---|
| Get Ads List | ✅ Working | Consistently stable |
| Get User Order Summary | ✅ Working | Recently activated |
| Get Available Ads Category | 🔄 Intermittent | Backend deployment in progress |
| Search Ads | ❌ Failing | Awaiting backend fix |
| Reference Prices | ❌ Failing | Awaiting backend fix |
| Chat Credentials | ❌ Failing | Parameter configuration needed |
- July 5-6: 1/6 endpoints working (16.7%)
- July 9 AM: 3/6 endpoints working (50%)
- July 9 PM: Fluctuating between 1-3 endpoints (backend changes active)
- Current: Backend team actively deploying fixes
- Automated Trading: Severely limited functionality
- Market Analysis: Cannot access filtered data
- Price Discovery: No reference price capabilities
- Bot Development: Blocked advanced features
- Status: 🔄 Backend team actively deploying fixes
- Current Handler: CS Sergei U (Merchant Team) - Technical specialist
- Priority: HIGH (production blocking)
- Evidence: Endpoint fluctuations confirm backend development in progress
- Latest: July 9, 2025 - Multiple API key tests show active backend changes
- Enable P2P API access for affected API keys
- Verify backend registration in P2P systems
- Remove access restrictions blocking specific endpoints
- Test and confirm full functionality restored
- Reproduce the issue using your own Binance API credentials
- Share testing results in GitHub Issues
- Document workarounds or partial solutions
- Update status when Binance resolves the issue
- Never expose real API keys in public repositories
- Use placeholder credentials in code examples
- Document your testing environment for reference
- Report new findings through GitHub Issues
- ✅ No real API keys exposed in this repository
- ✅ All sensitive data properly sanitized
- ✅ Safe for public sharing and collaboration
- Use testnet credentials when possible
- Mask production keys in logs and screenshots
- Follow responsible disclosure for security issues
[✅] Issue Discovery & Documentation
[✅] Binance Support Engagement
[✅] Format Verification & Implementation
[✅] Backend Team Escalation
[🔄] Backend Fix Deployment ← WE ARE HERE
[⏸️] Final Testing & Validation
[⏸️] Production Completion
- Endpoint Fluctuations: Same endpoints switching between working/failing over hours
- Success Rate Changes: 16.7% → 50% → 16.7% within single day
- Error Pattern Evolution: Moving from consistent -2008 to mixed error types
- Support Escalation: Merchant Team (CS Sergei) now handling case
- GitHub Issues - Latest updates and discussions
- Support Timeline - Complete case documentation
This project is licensed under the MIT License - see the LICENSE file for details.
If this documentation helped you understand or resolve similar Binance API issues, please star this repository to help others find it!
📧 Questions? Open a GitHub Issue or check our Contributing Guidelines.
🔔 Updates: Watch this repository for notifications when the issue is resolved.
🐛 Similar Issues? Use our bug report template to document your experience.