What authentication does the ezBookkeeping API use?

The spec declares an HTTP bearer token scheme. Obtain the token by POSTing credentials to /api/authorize.json (and following up with /api/2fa/authorize.json when 2FA is enabled) and supply it as the Authorization header on subsequent calls; through Jentic the token is held in the vault.

Can I add a new account through the ezBookkeeping API?

Yes. POST the account payload to /api/accounts/add.json with a valid bearer token; you can later modify the same account via /api/accounts/modify.json or list everything with /api/accounts/list.json.

How do I revoke an old token?

Call GET /api/tokens/list.json to find the token id, then POST to /api/tokens/revoke.json with that id; use /api/tokens/revoke_all.json to wipe every active token at once.

How do I list my accounts through Jentic?

Run pip install jentic, search 'list ezBookkeeping accounts', load /api/accounts/list.json, and execute it against your self-hosted host; the bearer token from /api/authorize.json is injected from the vault automatically.

Is the ezBookkeeping API free?

ezBookkeeping is a free, open-source self-hosted project, so the API itself has no licence fee; running costs are limited to whatever infrastructure you choose to host it on.

Can I limit what my agent is allowed to do with the ezBookkeeping API?

Yes. Because you run Jentic One yourself, your own rules decide which ezBookkeeping operations and credentials the agent can use. You can allow just the calls the task needs, such as listing accounts with /api/accounts/list.json or adding one with /api/accounts/add.json, while withholding sensitive operations like token revocation via /api/tokens/revoke_all.json or user registration via /api/users/register.json. Since ezBookkeeping carries its targets in the request body rather than as path resource ids, scoping at the operation level is enough to keep the agent inside those boundaries.