Common Errors

This guide covers the most frequent errors you may encounter when using Conviro and how to resolve them.

HTTP 401 -- Unauthorized

Meaning: Your API key or session token is invalid or expired.

Causes & Fixes:

• API key is wrong -- double-check the key at Dashboard -> Settings -> API Keys
• API key was revoked -- generate a new key and update your integration
• Session expired -- log out and log back in to the dashboard
• Missing Authorization header -- ensure your API request includes Authorization: Bearer sk_your_key

HTTP 403 -- Forbidden

Meaning: You do not have permission to access this resource.

Causes & Fixes:

• Domain not allowed -- add your website domain to Dashboard -> Assistants -> Your Bot -> Channels -> Allowed Domains
• Plan limit reached -- you are trying to use a feature not available on your current plan (e.g. WhatsApp on Starter)
• Role restriction -- your team role (Agent) may not have permission for this action; ask an Admin or Owner
• Bot is inactive -- activate the bot in Dashboard -> Assistants

HTTP 404 -- Not Found

Meaning: The requested resource does not exist.

Causes & Fixes:

• Wrong endpoint -- check the API documentation at /developers for correct URLs
• Deleted resource -- the chatbot, session, or contact was deleted
• Typo in ID -- double-check the resource ID in your request URL

HTTP 429 -- Too Many Requests (Rate Limiting)

Meaning: You have exceeded the API rate limit for your plan.

Causes & Fixes:

• Check the rate limit headers in the response:

X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset

• Reduce request frequency -- add delays or batch operations
• Upgrade your plan -- higher plans have higher rate limits
• Cache responses -- avoid making the same request repeatedly

Rate limits by plan:

CORS Errors

Meaning: The browser is blocking a cross-origin request.

Symptom: You see an error like Access to XMLHttpRequest has been blocked by CORS policy in the browser console.

Causes & Fixes:

• Widget domain not allowed -- add your domain to the Allowed Domains list
• Mixed content -- ensure your site uses HTTPS (not HTTP) if the widget loads from HTTPS
• Proxy or CDN interference -- check if your CDN is stripping CORS headers

Webhook Delivery Failures

Meaning: Conviro sent a webhook but your server did not respond with a 2xx status code.

Causes & Fixes:

• Server is down -- check that your webhook endpoint is running and accessible
• Timeout -- Conviro waits 10 seconds for a response. Ensure your endpoint responds quickly
• SSL certificate issue -- your endpoint must have a valid SSL certificate (self-signed certs are not accepted)
• Firewall blocking -- whitelist Conviro's IP range in your firewall
• Wrong URL -- verify the webhook URL in Dashboard -> Settings -> Webhooks

Retry policy: Conviro retries failed webhooks 3 times with exponential backoff (1 min, 5 min, 30 min). After 3 failures, the webhook is marked as failing and you receive an email notification.

Check webhook delivery logs at Dashboard -> Settings -> Webhooks -> Delivery Log.

Message Limit Reached

Meaning: You have used all your monthly messages.

Causes & Fixes:

• Free/Starter -- conversations are paused until the next billing cycle. Upgrade to a higher plan for more messages.
• Pro/Growth -- enable overage billing at Dashboard -> Settings -> Billing to automatically purchase additional message blocks.
• Check usage -- monitor your consumption at Dashboard -> AI Usage.

General Tips

• Always check the browser console (F12) for client-side errors.
• For API errors, inspect the response body -- it usually contains a descriptive error message.
• Check the Conviro status page for any ongoing incidents or maintenance.
• If you cannot resolve the issue, contact [email protected] with the error details, request ID (if available), and steps to reproduce.