Ezbookkeeping Mayswind ezBookkeeping API

Name: ezBookkeeping API
Brand: ezBookkeeping API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingbearer39 EndpointsREST

For Agents

Manage personal-finance transactions, accounts, categories, tags and tokens on a self-hosted ezBookkeeping deployment via 39 JSON endpoints with bearer-token auth.

Install Jentic One Beta

Connect the ezBookkeeping API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ezBookkeeping API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ezBookkeeping API.

Authorise a user and obtain a bearer token via /api/authorize.json with optional 2FA

List, add, modify and inspect financial accounts through /api/accounts/list.json and /api/accounts/add.json

Manage personal profile and registration via /api/users/profile/get.json and /api/users/register.json

GET STARTED

Start building with ezBookkeeping API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ezBookkeeping API for, with concrete tasks.

★ Self-Hosted Personal Finance Automation

Drive a self-hosted ezBookkeeping deployment from scripts and agents, including login, account management, and token lifecycle. Authorise via /api/authorize.json, optionally exchange a 2FA code through /api/2fa/authorize.json, and use the resulting bearer token to call account, profile and token endpoints. Because hosting is per-user, the {host} placeholder in the base URL must be filled with the deployment's hostname.

POST credentials to https://my-ezbk.example.com/api/authorize.json, then call GET /api/accounts/list.json with the returned bearer token to enumerate accounts.

Account Onboarding Flow

Programmatically register a new ezBookkeeping user, retrieve their profile, and seed the deployment with initial accounts. Use /api/users/register.json to create the user, /api/authorize.json to obtain a token, and /api/accounts/add.json for each starting account. Suitable for households or small teams setting up a shared ezBookkeeping instance from a configuration file.

Call /api/users/register.json with the new user payload, /api/authorize.json to obtain a token, then loop /api/accounts/add.json for each account in the configuration.

Token Hygiene and 2FA Recovery

Maintain account security by listing active tokens, revoking individual stale ones, or rotating all tokens at once with /api/tokens/revoke_all.json. The /api/2fa/recovery.json endpoint supports recovery-code submission when the second factor is unavailable. Useful for households operating shared deployments who need to expire access for departed users.

Call GET /api/tokens/list.json, identify stale tokens, then call /api/tokens/revoke.json for each to revoke them in turn.

Agent-Driven Bookkeeping via Jentic

An AI agent configured for a household's self-hosted ezBookkeeping deployment can use Jentic to discover and call the right endpoints rather than embedding the full client. Bearer tokens issued by /api/authorize.json live in the Jentic vault, so the agent can list and modify accounts without ever holding the user's password.

Through Jentic, search 'list ezBookkeeping accounts', load /api/accounts/list.json, and execute it against the household deployment's host.

Key Endpoints

39 endpoints — jentic publishes the only available openapi specification for ezbookkeeping api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/authorize.json

Authorise a user and return a bearer token

POST

/api/2fa/authorize.json

Submit a 2FA code to complete login

GET

/api/tokens/list.json

List the active tokens for the current user

POST

/api/tokens/revoke_all.json

Revoke all tokens for the current user

GET

/api/accounts/list.json

List financial accounts

POST

/api/accounts/add.json

Add a new financial account

POST

/api/accounts/modify.json

Modify an existing financial account

POST

/api/users/register.json

POST

/api/authorize.json

Authorise a user and return a bearer token

POST

/api/2fa/authorize.json

Submit a 2FA code to complete login

GET

/api/tokens/list.json

List the active tokens for the current user

POST

/api/tokens/revoke_all.json

Revoke all tokens for the current user

GET

/api/accounts/list.json

List financial accounts

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Bearer tokens issued by /api/authorize.json are stored encrypted in the Jentic vault; agents receive a scoped token at execution time and never handle the user's password or 2FA secret.

Intent-based discovery

Agents search Jentic for intents like 'list ezBookkeeping accounts' and Jentic returns the corresponding /api/accounts/list.json operation with its input schema, so the agent does not have to memorise the JSON-RPC-style URL conventions.

Time to first call

Direct integration: 1-2 days to wire authorisation, 2FA fallback and account flows for a self-hosted host. Through Jentic: under an hour to search, load, and execute.

FAQs

Specific to using ezBookkeeping API through Jentic.

Why is there no official OpenAPI spec for ezBookkeeping API?

ezBookkeeping does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ezBookkeeping API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

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.

Ezbookkeeping Mayswind ezBookkeeping API

Connect the ezBookkeeping API to your agent

Capabilities

Start building with ezBookkeeping API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs