Documentation / API Troubleshooting / 401 Unauthorized

401 Unauthorized

401 Unauthorized troubleshooting for PanelConfig API integrations.

Meaning

A 401 means the request did not authenticate. Check for a missing bearer token, a cut off token, an expired token, a revoked or inactive token, or a disabled user.

Checklist

  1. Call /api/v1/me.php with the same token.
  2. Confirm the exact route exists in /api/v1/.
  3. Use the file-based .php path unless your deployment has route rewriting.
  4. Check whether the endpoint requires an admin-capable user.
  5. Check rate-limit behavior and reduce polling if needed.
  6. Review API request records and server/PHP logs.

Example

curl -i https://panel.example.com/api/v1/me.php \
  -H "Authorization: Bearer pc_YOUR_TOKEN" \
  -H "Accept: application/json"

Recovery

  • Do not retry writes blindly in future write endpoints.
  • Rotate tokens if secret exposure is suspected.
  • Use staging to reproduce integration failures.
  • Escalate with timestamp, route, HTTP status, and response message.

Error Handling

flowchart TD
    A[API Request] --> B{Token Valid}
    B -- No --> C[401 Unauthorized]
    B -- Yes --> D{Role Allowed}
    D -- No --> E[403 Forbidden]
    D -- Yes --> F{Rate Window OK}
    F -- No --> G[429 Rate Limit]
    F -- Yes --> H[Return JSON]
403 Forbidden →