⚠ Purpose of This Article:
The current Liongard documentation for the Axcient x360Recover Inspector is missing an important step during API Key creation — enabling the “Billing” API permission. Without this, the inspector fails with a 403 error when attempting to access https://apicpi.axcient.com/billing/v3/api/billing.
1. Summary / Purpose
When configuring the Axcient x360Recover Inspector in Liongard, the documentation instructs users to enable only certain API scopes. However, the “Billing” API scope is also required. Without it, the inspector throws a 403 permissions error and fails to collect data.
2. 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 |
3. 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
4. Procedure / Steps
✅ 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
5. 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 |
6. 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
7. Related Articles / References
[Liongard Doc (missing step)] https://docs.liongard.com/docs/axcient-x360recover-inspector
Axcient API Reference (Billing endpoint)
