API keys and MCP access

Connect an OAuth assistant to LedgerHQ's direct or complete bookkeeping MCP, or create a personal API key for a developer integration.

Open API And MCP

Open the user menu, choose Firm settings, and open the API and MCP section. The tab separates OAuth assistants from developer API keys. Connections use the companies and permissions available to the person who authorizes them.

Connect A Direct MCP Assistant

Use Work directly with LedgerHQ for everyday bookkeeping requests such as reading books, running reports, and reviewing or posting supported accounting work.

In your AI assistant, add a custom connector, paste this URL, and sign in:

https://ledgerhq.pro/api/mcp

The connection uses LedgerHQ's OAuth flow. No token file or terminal setup is needed.

Connect The Complete Bookkeeping MCP

Use Full bookkeeping access when the assistant needs LedgerHQ's complete direct bookkeeping catalog, including company setup, coding, posting, reconciliation, statements, reports, imports, invoices, and period work.

Add a second custom connector with:

https://ledgerhq.pro/api/mcp/bookkeeping

Sign in through the authorization screen. Every connection receives the same bookkeeping catalog. The connector works directly with LedgerHQ and does not delegate work through Tally.

Review Authorized Assistants

After authorization, the Authorized assistants section lists the connected assistant, its connection kind such as Direct MCP or Bookkeeping MCP, and its Connected status. Choose Revoke when the assistant should no longer reach the firm's books. Revoke old or unrecognized connections promptly.

Authorizing an assistant grants standing access to the books available to that LedgerHQ login until the connection is revoked. Only authorize a client you trust, and use an identity whose firm and company access matches the integration's purpose.

Create A Personal API Key

For scripts and custom integrations, expand For developers and custom integrations in the API and MCP tab. Enter a descriptive key name and create the key. LedgerHQ shows the full value once; copy it immediately into a secret store.

Call the REST API with a Bearer token. The base URL is:

https://ledgerhq.pro/api/v1

The tab shows active keys by name and prefix and lets you revoke them. If advanced access controls are available for the account, grant only the scopes the integration needs.

An API key authenticates a developer integration to LedgerHQ's REST surface. It is separate from OAuth assistant connections. Never paste a key into chat, a commit, a screenshot, or a shared document.

The Authorize Screen

The OAuth screen names the assistant and lists the LedgerHQ capabilities it is requesting. Read the company, report, accounting, and file permissions before choosing Authorize. Choose Deny when the request is unexpected.

The same API and MCP tab is the place to review and revoke the connection later.