Rovo Dev CLI – 403 Forbidden when running acli rovodev run (credits/check endpoint)

Maarten Knaepen

Hi,

I'm suddenly unable to start Rovo Dev using the CLI. The command fails with a <span>403 Forbidden</span> when calling the Rovo API.

This worked fine on 6 March, and nothing in my setup has changed since then.

Command

<span>acli rovodev run</span>

Error

<span>Failed to connect to the Rovo Dev API on http status error, please try again later.</span>

Relevant logs

<span>Using endpoint: https://api.atlassian.com/rovodev/v3/credits/check
Client error '403 Forbidden' for url 'https://api.atlassian.com/rovodev/v3/credits/check'
Retrying...</span>

After several retries the CLI exits with:

<span>Error - Failed to connect to the Rovo Dev API on http status error</span>

Question

Has anyone seen this before?

Since it worked yesterday (6 March), I'm wondering if this might be:

• an Atlassian-side permission or rollout change

• an expired auth/session token

• a Rovo Dev API issue

Any ideas on how to debug or fix this?

Thanks!

Jovana Dunisijevic

Hi @Maarten Knaepen

Thanks for raising this – and for including the exact CLI output, that’s really helpful.

A 403 on https://api.atlassian.com/rovodev/v3/credits/check generally means the call is reaching the Rovo Dev API, but the current auth context isn’t allowed to access that endpoint (rather than a network or CLI bug). Because it was working on 6 March and then stopped, the most common causes are:

1. Auth / token issues
- Your local auth state may be stale or tied to a different Atlassian account/workspace than the one that has Rovo Dev access.
- Your session might have expired or been invalidated by a permissions/rollout change.

2. Org / site permissions or rollout
- Your org admin might have:
- Turned off Rovo Dev for your site or org, or
- Restricted access to specific groups, or
- Changed which sites/users are in the rollout cohort.

To help debug, could you try:

1. Re‑auth the CLI

acli auth logout
acli auth login

Then re‑run:

acli rovodev run --debug

and see if you still get 403 Forbidden on the credits/check call.

2. Confirm the account and site
- In the browser, make sure you’re logged in with the same Atlassian account you use in the CLI.
- Confirm you’re running Rovo Dev against a site where your admin has enabled Rovo Dev and given you access.

3. Check with your org / site admin
- Ask your admin to confirm:
- Rovo Dev is still enabled for your cloud site.
- Your user/group is still included in the allowed rollout/audience.
- If they recently changed Rovo Dev settings or experiments/rollouts, that can surface as a 403 on the `credits/check` endpoint.

Hope this helps troubleshoot it!