Contact Support
Response Times
| Plan | Initial Response | Severity 1 (Outage) |
|---|---|---|
| Basic | 2 business days | 24 hours |
| Standard | 1 business day | 8 hours |
| Pro | 4 hours | 1 hour |
Severity 1 issues are defined as complete service outages affecting production workloads.
Before Contacting Support
To help us resolve your issue quickly, please include:- Project ID — Found in your dashboard under Settings
- Request ID — Included in every API response header (
X-Request-Id) - Timestamp — When the issue occurred (UTC preferred)
- Error message — Full error response from the API
- Steps to reproduce — What you were doing when the issue occurred
Common Issues
Authentication errors (401)
Authentication errors (401)
- Verify your API key is correct and not revoked
- Ensure you’re using
Bearerauthentication:Authorization: Bearer sk_live_... - Check that you’re using the correct environment (live vs sandbox)
- See Authentication for details
Rate limiting (429)
Rate limiting (429)
- Default rate limit is 100 requests per second per project
- Implement exponential backoff on 429 responses
- Check
X-RateLimit-Remainingheader to monitor usage - See Rate Limits for details
Upload failures
Upload failures
- Ensure upload URLs haven’t expired (valid for 1 hour)
- Verify file format is supported (WAV, MP3, M4A, FLAC)
- For large files, use multipart upload
- See Uploads for details
Webhook not receiving events
Webhook not receiving events
- Verify your endpoint returns 2xx status codes
- Check that your endpoint responds within 30 seconds
- Ensure your endpoint accepts POST requests with JSON body
- Verify webhook signature validation logic
- See Webhooks for details
Transcription quality issues
Transcription quality issues
- Ensure audio quality is sufficient (clear speech, minimal background noise)
- Check that the correct language is being detected
- For domain-specific vocabulary, contact support about custom dictionaries
Developer Resources
API Reference
Complete endpoint documentation
Quickstart
Get started in minutes
Changelog
Latest platform updates
Feature Requests
Have an idea for improving Bota? We’d love to hear from you. Email your feature requests to [email protected] with:- Use case — What problem are you trying to solve?
- Proposed solution — How would you like it to work?
- Priority — How important is this for your integration?

