Troubleshooting
Common issues, debugging tips, and error resolution for ContentSellify.
Common Issues & Solutions
🔑 API Authentication Errors (401 Unauthorized)
Symptom: Getting 401 errors when calling API endpoints.
Common Causes:
- Missing or invalid API key
- Using test key in production (or vice versa)
- API key not in Authorization header
- Expired OAuth token
Solutions:
- Verify API key: Dashboard → API Settings → Keys
- Use correct format:
Authorization: Bearer YOUR_API_KEY - Regenerate key if compromised
- Implement token refresh for OAuth
📤 File Upload Failures
Symptom: Files fail to upload or upload gets stuck.
Common Causes:
- File size exceeds 500MB limit
- Unsupported file type
- Poor network connection
- Browser timeout
Solutions:
- Compress files under 500MB
- Use supported formats: PDF, ZIP, MP4, MP3, JPG, PNG
- Use chunked uploads for large files
- Try different browser or clear cache
💳 Payment Processing Errors
Symptom: Payments failing or getting declined.
Common Causes:
- Card declined by bank
- Insufficient funds
- 3D Secure authentication failed
- Card expired or blocked
Solutions:
- Try different payment method
- Contact bank to verify card status
- Enable 3D Secure in settings
- Use test cards for development
💸 Payout Delays or Failures
Symptom: Payouts not arriving or showing as failed.
Common Causes:
- Incorrect bank account details
- Minimum payout amount not met ($10)
- Account verification pending
- Bank processing delays
Solutions:
- Verify bank details: Dashboard → Settings → Bank Account
- Wait until balance reaches $10 minimum
- Complete account verification
- Allow 3-5 business days for processing
📦 Product Not Approved
Symptom: Product submission rejected or pending for days.
Common Causes:
- Low-quality product description or images
- Copyrighted content without license
- Missing required information
- Quality review backlog
Solutions:
- Read rejection feedback carefully
- Use high-quality screenshots/previews
- Provide detailed, accurate descriptions
- Check Pending Approvals for status
⚡ Rate Limit Exceeded (429 Error)
Symptom: Getting 429 "Too Many Requests" errors.
Common Causes:
- Exceeded 100 requests per minute
- No rate limit handling in code
- Burst of concurrent requests
Solutions:
- Implement exponential backoff
- Cache frequently accessed data
- Use webhooks instead of polling
- Upgrade to higher tier for more requests
HTTP Error Codes Reference
| Code | Meaning | Typical Cause |
|---|---|---|
| 400 | Bad Request | Invalid parameters or malformed JSON |
| 401 | Unauthorized | Invalid or missing API key |
| 403 | Forbidden | Insufficient permissions |
| 404 | Not Found | Resource doesn't exist |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Server-side issue (contact support) |
| 503 | Service Unavailable | Maintenance or temporary outage |
Enable Debug Mode
Get detailed error information by enabling debug mode during development:
// Add to your API requests
headers: {
'X-Debug-Mode': 'true'
}⚠️Warning: Never enable debug mode in production. It may expose sensitive information.
Still Need Help?
If you're still experiencing issues, contact our support team:
📧 Email Support
support@bittforge.in
Response within 24 hours
💬 Live Chat
Available in dashboard
9 AM - 6 PM EST, Mon-Fri