Skip to main content

KeePassXC Browser API

Python library for communicating with KeePassXC via the browser extension protocol (NaCl-encrypted JSON over a Unix socket).

Features

  • NaCl-encrypted communication with KeePassXC
  • One-time association flow (user approves in KeePassXC window)
  • Biometric unlock (TouchID / system unlock) via triggerUnlock
  • Full browser API support: read entries, write entries, manage groups, TOTP, password generation, lock database
  • Cross-platform: macOS and Linux
  • Shared config (~/.keepassxc/browser-api.json) — associate once, use with all tools

Projects using KeePassXC Browser API

Install

pip install keepassxc-browser-api

Quick start

from keepassxc_browser_api import BrowserClient, BrowserConfig

config = BrowserConfig.load()
client = BrowserClient(config)

# First time: associate with KeePassXC (requires user approval)
if not config.associations:
    client.setup()
    config.save()

# API methods auto-connect, auto-unlock (triggers TouchID/biometrics if locked),
# and verify the association before every call
entries = client.get_logins("https://example.com")
for e in entries:
    print(e.name, e.login)

# Clean up when done
client.disconnect()

Or use the context manager for automatic cleanup:

with BrowserClient(config) as client:
    entries = client.get_logins("https://example.com")
    totp = client.get_totp(entries[0].uuid)

API

BrowserClient

Method Description
setup() First-time association (user approves in KeePassXC)
ensure_unlocked() Connect and unlock (triggers TouchID if locked)
get_logins(url, ...) Find entries matching a URL
set_login(url, username, password, ...) Create or update an entry
get_database_entries() Return all entries
get_database_groups() Return all groups (tree)
create_group(name) Create a new group (use "Parent/Child" path syntax for nesting)
get_totp(uuid) Get TOTP code for an entry
delete_entry(uuid) Delete an entry
lock_database() Lock the database
generate_password() Generate a password (uses KeePassXC settings)
request_autotype(search) Trigger KeePassXC global auto-type

Note: passkeys-get and passkeys-register are not implemented. They require complex WebAuthn/CBOR data structures and are only available in KeePassXC builds compiled with WITH_XC_BROWSER_PASSKEYS.

BrowserConfig

Configuration stored at ~/.keepassxc/browser-api.json (mode 0600).

config = BrowserConfig.load()        # Load from default path
config = BrowserConfig.load(path)    # Load from custom path
config.save()                        # Save to default path
config.save(path)                    # Save to custom path

Error handling

All API methods raise exceptions on failure — they never return False or None on error.

Exception Cause
ConnectionError KeePassXC is not running / socket not found
DatabaseLockedError Database unlock timeout exceeded
ProtocolError KeePassXC returned a protocol-level error response
KeePassXCError Base class — catch this to handle all library errors at once

ProtocolError.error_code contains the KeePassXC error enum value (see PROTOCOL.md for the full list). Common values: 6 = access denied by user, 19 = access to all entries denied.

Special case: get_logins() catches ProtocolError(code=15) (no logins found) internally and returns [] instead of raising.

from keepassxc_browser_api import BrowserClient, BrowserConfig
from keepassxc_browser_api.exceptions import ConnectionError, DatabaseLockedError, ProtocolError

config = BrowserConfig.load()
client = BrowserClient(config)

try:
    entries = client.get_logins("https://example.com")
except ConnectionError:
    print("KeePassXC is not running", file=sys.stderr)
    sys.exit(2)
except DatabaseLockedError:
    print("Database unlock timed out", file=sys.stderr)
    sys.exit(3)
except ProtocolError as e:
    print(f"KeePassXC error {e.error_code}: {e}", file=sys.stderr)
    sys.exit(1)

Protocol documentation

For a detailed description of the KeePassXC browser extension protocol (wire format, encryption, all actions, error codes), see PROTOCOL.md.

Development

# Install in editable mode with dev dependencies
pip install -e ".[dev]"

# Run tests
pytest --tb=short -q

# Run tests with coverage
pytest --cov=keepassxc_browser_api --cov-report=term-missing

# Lint
ruff check --ignore=E501 --exclude=__init__.py ./keepassxc_browser_api

Release files for keepassxc-browser-api 1.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for keepassxc-browser-api 1.5.0
File Size Uploaded
keepassxc_browser_api-1.5.0.tar.gz 32.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for keepassxc-browser-api 1.5.0
File Interpreter ABI Platform
keepassxc_browser_api-1.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 46.6 kB

Release files / keepassxc_browser_api-1.5.0.tar.gz

Download URL keepassxc_browser_api-1.5.0.tar.gz
Size 32.2 kB
Tags Source
SHA-256 checksum
How to use checksums
1e429818c0aa0ab2a99203eaa625815974894cc24d6ad259330adcfe71abeda0
BLAKE2b-256 checksum
How to use checksums
3bab3831d535e693757ba3136921df980f4afc45b2e714b7203fdf22e36098ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 20, 2026.

Transparency log

Release files / keepassxc_browser_api-1.5.0-py3-none-any.whl

Download URL keepassxc_browser_api-1.5.0-py3-none-any.whl
Size 14.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0ed285ee77220e74872075821981e81a7e4458e261288919b284d465030b5d0d
BLAKE2b-256 checksum
How to use checksums
f6314c819ea63c1442a202cd499715962c1b0273207300cb506363e0cc2c8dd6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 20, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.5.0 This release

2 release files

1.4.0

2 release files

1.3.0

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page