VICIPanel
Troubleshooting/API authentication failed
MediumWeb

API authentication failed

External system cannot authenticate to the VICIdial non-agent API.

Symptoms

  • •CRM integration returns 401 or 403
  • •Custom report scripts fail to fetch data
  • •Agent screen-pop API returns error

Common causes

  • •API user credentials rotated and integration not updated
  • •API user's `user_level` insufficient for the requested action
  • •IP allowlist on the API user blocks source IP
  • •Token expiration on newer token-based endpoints

How to fix it

  1. 1
    Verify user/pass combination in vicidial_users
  2. 2
    Check user's `user_level`, many API functions require level 9 (admin)
  3. 3
    Review `admin_viewable_groups` / `access_recordings` for granular permissions
  4. 4
    Check IP allow list: `modify_same_user_level` and restrictions
Web health and operational view in VICIPanel
How VICIPanel helps

VICIPanel ships OAuth 2.1 for its own API, short-lived tokens, dynamic client registration, and audit log of every access. No more rotating passwords in cron scripts.

Related issues

More Web errors

Agent screen blank or stuck on loading

Agent logs in but sees a blank agent interface or a spinner that never resolves.

Agent kick-all command errors out

Supervisor 'kick all agents' function errors instead of logging agents out.

Screen pop blank or showing wrong lead

When a call connects, the agent sees a blank lead form or data from a previous call.

Stop troubleshooting. Start operating.

VICIPanel's health dashboard catches most of these issues before they impact your agents — with plain-English diagnostics and one-click remediation.

Try the live demoError reference