Best Practices
Common Issues
Issue: "Failed to download document"
Cause: URL not accessible
Solution:
- Use S3 presigned URLs
- Verify URL returns FTR file
- Check URL hasn't expired
Issue: "Invalid FTR file format"
Cause: Corrupted or invalid file
Solution:
- Test file in FTR player first
- Verify file extension is
.ftr - Check file size is not 0 bytes
Issue: Slow conversion
Cause: Large file or multi-channel audio
Solution:
- Use webhooks instead of polling
- 8-hour files can take 10-15 minutes
- Set timeout to 2x file duration
Issue: Permission denied (403)
Cause: API key missing converter access
Solution:
- Verify
ftr_converterin API key permissions - Contact support to enable access
Best Practices
Before Converting
- Verify FTR file quality - test in FTR player
- Use S3 presigned URLs - more secure than public URLs
- Plan storage - download M4A within 7 days
During Conversion
- Use webhooks for long files (1+ hours)
- Implement retry logic - exponential backoff
- Monitor progress - check
progressfield
After Completion
- Download immediately - files expire after 7 days
- Verify audio - play M4A to confirm quality
- Archive properly - store in your own S3/storage
- Clean up - delete conversion jobs when done
Pricing
| Service | Cost |
|---|---|
| Per minute of audio | ~$0.01 |
| 3-hour hearing | ~$1.80 |
| 8-hour full day | ~$4.80 |
| Storage (7 days) | Included |
| Downloads | Unlimited (free) |