Facebook
LinkedIn
YouTube
Getting Started
Authentication
Authentication
  • V2 Authentication (Deprecated)
  • V3 Authentication
V2 API Documentation (Deprecated)V3 API Documentation
Getting Started
Authentication
Authentication
  • V2 Authentication (Deprecated)
  • V3 Authentication
V2 API Documentation (Deprecated)V3 API Documentation
  1. Getting Started
  • Choosing the Right API Version
  • Getting Started
  • Architecture
  • Quick Start
  • Authentication
  • Roles and API Access
  • API Categories
  • API Endpoints Reference
  • Making Your First API Call
  • Working with Encrypted Tokens
  • Code Examples
  • Error Handling
  • Best Practices
  • Troubleshooting
  • Support
  1. Getting Started

Troubleshooting

Problem: 401 Unauthorized Error#

Possible Causes:
Access token is expired
Token was revoked (user logged out)
Token is invalid or corrupted
Missing Authorization header
Solutions:
1.
Check if token is expired and refresh it
2.
Verify the Authorization header format: Bearer <token>
3.
Re-authenticate if refresh token is also expired
4.
Check if the token is URL-encoded correctly

Problem: Token Refresh Fails#

Possible Causes:
Refresh token is expired (6 months)
Refresh token was already used (token rotation)
Refresh token was revoked
Solutions:
1.
Re-login to get new token pair
2.
Check token expiration times
3.
Verify the refresh token is stored correctly

Problem: CORS Errors in Browser#

Possible Causes:
Frontend URL not in CORS whitelist
Missing CORS headers in preflight request
Solutions:
1.
Contact API administrator to whitelist your domain
2.
Use a backend proxy for development
3.
Check browser console for specific CORS errors

Problem: Audio File Upload Fails (Media Prompts)#

Possible Causes:
File size exceeds 50MB limit
Audio file type not allowed
Missing multipart/form-data content type
Incorrect field name
Solutions:
1.
Check file size (max 50MB for audio files)
2.
Verify audio format (wav, mp3, mp4, ogg, webm, m4a, aac, flac)
3.
Use multipart/form-data content type
4.
Ensure field name is 'file'
5.
Check that message_type is provided (prompt, whisper, voicemail, survey)

Problem: Empty or Incorrect Data#

Possible Causes:
Wrong organization ID (ouid)
Incorrect date range
Missing required query parameters
Solutions:
1.
Verify organization ID with your administrator
2.
Check date format (ISO 8601 UTC, e.g., 2026-01-01T00:00:00Z)
3.
Review API documentation for required parameters

Getting Help#

If you encounter issues:
1.
Check Request ID:
All error responses include a requestId
Include this ID when contacting support
2.
Review Logs:
Check browser console for client-side errors
Review server logs if you have access
3.
Contact Support:
Email: support@convirza.com
Include: request ID, timestamp, endpoint, error message
Modified at 2026-03-23 20:39:39
Previous
Best Practices
Next
Support
Built with