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)
ā


