JARVIS

What this page can and cannot tell you

It reports whether each setting is present or missing. It never shows a value, a length, a prefix or a hash of one. It makes no connection attempt: checking readiness must not spend the refresh token, because Intuit invalidates the one you present on every exchange.

Read-only, honestly stated

Intuit publishes no read-only accounting scope. com.intuit.quickbooks.accounting is read/write at Intuit's end, so a token minted from it is technically capable of altering the company file.

Jarvis enforces read-only behaviour in its own transport: it calls only the GET /query endpoint, assertReadOnlyRequest refuses any other method against an Intuit host, and assertReadOnlyQuickBooks refuses a reader that grows a second method. Those are this application's controls, not Intuit's permissions.

Treat the refresh token as a credential that could alter the books if it leaked. Do not also grant Intuit's separate payments scope: nothing here can use it and it widens the blast radius for no benefit. Its literal name is deliberately not printed on this page, so that a repository-wide search for a write scope stays a reliable check.

One-time operator checklist

1. developer.intuit.com → create an app → Keys & credentials → Production.
2. Add a redirect URI you control. It only has to receive the code once.
3. Open the OAuth 2.0 Playground for that app. Select com.intuit.quickbooks.accounting and nothing else.
4. Authorise the company file and exchange the code for tokens.
5. Set the four variables on the server, then restart the services.
6. Return here and press Re-check.

There is deliberately no form on this page. This repository has no established pattern for accepting a secret through a browser, and inventing one for a single screen would be the riskiest code in the project.