Skip to main content

Axcient x360 Recover | Error 403

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 šŸ§‘ā€šŸ«


Steps To Resolve šŸ‘Øā€šŸ’»

āœ… Follow Liongard’s documentation — but with one critical addition:

  1. Login to the Axcient x360 Portal

  2. Navigate to Settings → API Keys

  3. Click Generate API Key

  4. Name the key (ex: Liongard Inspector)

  5. āœ… 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.
    ​

  6. Accept the License Agreement checkbox

  7. Click Generate API Key

  8. 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 🤩

Did this answer your question?