Purpose of This Article 💥
When encountering 403 errors, an additional step to verify during API key creation is that the “Billing” API permission is enabled.
Without this, the inspector fails with a 403 error when attempting to access https://apicpi.axcient.com/billing/v3/api/billing.
Summary 🌟
During configuration of the Axcient x360Recover Inspector in Liongard, API scopes must be correctly set when creating the API key. A missing “Billing” API scope may result in 403 permissions errors and prevent data collection, so this scope should be verified if such errors are observed.
Applies To 🤔
Area | Details |
Platform Component | Axcient x360Recover Inspector |
Audience | Internal Support, Partners configuring Axcient Inspector |
Instance(s) | All Liongard Instances |
Role / Access | Axcient portal user with permission to generate API keys |
Prerequisites 🧑🏫
Access to Axcient x360 Portal
Ability to generate API keys
Liongard instance with Inspector configuration permissions
Reference doc: https://docs.liongard.com/docs/axcient-x360recover-inspector
Steps To Resolve 👨💻
✅ Follow Liongard’s documentation — but with one critical addition:
Login to the Axcient x360 Portal
Navigate to Settings → API Keys
Click Generate API Key
Name the key (ex: Liongard Inspector)
✅ Check the following permissions (this is the missing step!):
x360Cloud
x360Recover
x360Sync
✔ Billing ← Required but not listed in the Liongard doc
📷 See screenshot provided: “Billing” must be enabled to avoid 403 errors.
Accept the License Agreement checkbox
Click Generate API Key
Paste the key into Liongard → Inspectors → Axcient x360Recover → Configure
Troubleshooting & Common Issues 🚀
Symptom | Cause | Resolution |
“Billing” API scope not enabled | Edit or recreate API key → enable “Billing” | |
Inspector status = Error / Red | API authentication succeeds, but billing endpoint blocked | Confirm key includes Billing, re-add key in Liongard |
No Systems/Organizations populating | Key only has Recovery & Cloud scopes | Add Billing → Save Inspector → Re-run Inspector |
Best Practices / Notes 🗒️
Even if you don’t use Billing data in Liongard, Axcient’s API architecture requires Billing access for x360Recover queries to function properly
Recommend naming API keys clearly (e.g., “Liongard Inspector – with Billing”)
Store API key securely — Axcient only shows it once
Related Articles / References 🤩
Axcient API Reference (Billing endpoint)
