Skip to main content

Vodoo

Vodoo

License: MIT Python 3.12+ PyPI Documentation Code style: ruff Type checked: mypy

A Python library and CLI for Odoo. Use it as a library in your own scripts, services, and automations — or as a CLI for quick ad-hoc operations and AI-assisted workflows.

Supports helpdesk tickets, project tasks, projects, CRM leads/opportunities, accounting moves, knowledge articles, and timesheets across Odoo 17–19.

📖 Full Documentation — Getting started, CLI reference, Python library guide, and API docs.

Quick Start — Library

from vodoo import OdooClient, OdooConfig, RecordNotFoundError

config = OdooConfig(
    url="https://my-instance.odoo.com",
    database="mydb",
    username="bot@example.com",
    password="api-key-or-password",
)
client = OdooClient(config)

# Namespace helpers on the client
tasks = client.tasks.list(limit=10)

# Generic client for any model
partners = client.search_read("res.partner", fields=["name", "email"], limit=5)

# Structured exceptions — catch what you need
try:
    record = client.generic.search("res.partner", [("id", "=", 999999999)])
except RecordNotFoundError as e:
    print(f"{e.model} #{e.record_id} not found")

Quick Start — CLI

# Run without installing
uvx vodoo crm list --search "acme"

# Or install globally
pip install vodoo
vodoo helpdesk list --stage "In Progress"
vodoo project-task show 42
vodoo timer start 42

Works well with AI assistants like Claude Code — natural language in, structured Odoo operations out.

Odoo Version Support

Version Protocol Status
Odoo 17 Legacy JSON-RPC ✅ Fully tested
Odoo 18 Legacy JSON-RPC ✅ Fully tested
Odoo 19 JSON-2 (bearer auth) ✅ Fully tested

Auto-detects the Odoo version and selects the appropriate transport. Odoo 19's JSON-2 API is ~3–4x faster than legacy JSON-RPC.

Features

Library

  • 🐍 Clean Python API — OdooClient with namespace helpers (client.helpdesk, client.crm, etc.)
  • ⚡ Full async support via vodoo.aio — AsyncOdooClient with async context manager
  • 🎯 Structured exception hierarchy mirroring Odoo server errors
  • 📦 No CLI dependencies loaded when imported as a library
  • 🔒 Strict mypy typing throughout

CLI

  • 📋 Helpdesk tickets, project tasks, projects, CRM leads, knowledge articles
  • ⏱️ Timer / timesheet management (start, stop, status)
  • 💬 Comments, internal notes, tags, attachments
  • 🔍 Search across text fields (name, email, phone, description)
  • 🧰 Generic CRUD for any Odoo model
  • 🎨 Rich terminal output with tables

Shared

  • 🔀 Auto-detecting transport layer (JSON-2 for Odoo 19+, legacy JSON-RPC for 17–18)
  • ⚙️ Configuration via environment variables, .env, or OdooConfig
  • 🔐 HTTPS enforcement warnings for production safety

Installation

# From PyPI
pip install vodoo

# Or run the CLI without installing
uvx vodoo helpdesk list

# From source (development)
git clone https://github.com/julian-r/vodoo.git
cd vodoo
uv sync --all-extras

Configuration

Create a .vodoo.env, ~/.config/vodoo/config.env, or .env file:

ODOO_URL=https://your-odoo-instance.com
ODOO_DATABASE=your_database
ODOO_USERNAME=your_username
ODOO_PASSWORD=your_password_or_api_key
# Optional alternative: ODOO_PASSWORD_REF=op://Vault/Item/password
ODOO_DEFAULT_USER_ID=123  # Optional: default user for sudo operations

Multi-instance profiles are also supported:

  • .vodoo/instances/<instance>.env
  • ~/.config/vodoo/instances/<instance>.env
  • select via vodoo --instance <instance> ... or VODOO_INSTANCE=<instance>

Or set environment variables directly, or pass values to OdooConfig() in code.

Useful config helpers:

vodoo config list-instances
vodoo config show
vodoo config use staging
vodoo config test --instance staging

Exception Hierarchy

All exceptions inherit from VodooError so you can catch broadly or narrowly:

VodooError
├── ConfigurationError
├── AuthenticationError
├── RecordNotFoundError          ← .model, .record_id attributes
├── RecordOperationError
├── TransportError               ← .code, .data attributes
│   └── OdooUserError            ← odoo.exceptions.UserError
│       ├── OdooAccessDeniedError
│       ├── OdooAccessError
│       ├── OdooMissingError
│       └── OdooValidationError
└── FieldParsingError

Server-side Odoo errors are automatically mapped to the matching exception class, so you can handle OdooAccessError separately from OdooValidationError without parsing error strings.

Library Usage

Namespace Helpers

Each Odoo domain is a namespace on the client with high-level methods: from vodoo import OdooClient, OdooConfig client = OdooClient(OdooConfig( url="https://odoo.example.com", database="prod", username="bot@example.com", password="api-key", ))

Project tasks

tasks = client.tasks.list(domain=[("stage_id.name", "=", "In Progress")], limit=20) task = client.tasks.get(42) client.tasks.comment(42, "Deployed to staging") leads = client.crm.list(domain=[("type", "=", "opportunity")], limit=20) client.crm.set(123, {"expected_revenue": 50000, "probability": 75}) tickets = client.helpdesk.list(domain=[("stage_id.name", "=", "New")], limit=10) client.timer.start_task(task_id=42) client.timer.stop() records = client.search_read("res.partner", [("is_company", "=", True)], fields=["name"]) new_id = client.create("res.partner", {"name": "Acme Corp", "is_company": True}) client.write("res.partner", [new_id], {"phone": "+1234567890"})


### Error Handling

```python
from vodoo import (
    OdooClient, OdooConfig, VodooError,
    AuthenticationError, RecordNotFoundError,
    OdooAccessError, OdooValidationError,
)

try:
    client = OdooClient(OdooConfig(...))
    client.write("res.partner", [999], {"name": "Updated"})
except AuthenticationError:
    print("Bad credentials")
except RecordNotFoundError as e:
    print(f"{e.model} #{e.record_id} does not exist")
except OdooAccessError:
    print("Insufficient permissions")
except OdooValidationError:
    print("Data constraint violated")
except VodooError as e:
    print(f"Something else went wrong: {e}")

Async Usage

All library functionality is also available as async via vodoo.aio:

from vodoo import OdooConfig
from vodoo.aio import AsyncOdooClient

config = OdooConfig(
    url="https://my-instance.odoo.com",
    database="mydb",
    username="bot@example.com",
    password="api-key",
)

async with AsyncOdooClient(config) as client:
    # Namespace helpers
    tasks = await client.tasks.list(limit=10)
    partners = await client.search_read("res.partner", fields=["name", "email"], limit=5)
    # Comments / notes
    await client.crm.comment(123, "Async update")

Every sync namespace has an async counterpart — same methods, just awaited.

CLI Usage

CRM Leads/Opportunities

vodoo crm list --search "acme" --type opportunity --stage "Qualified"
vodoo crm show 123
vodoo crm set 123 expected_revenue=50000 probability=75
vodoo crm note 123 "Followed up via phone"
vodoo crm attach 123 proposal.pdf
vodoo crm url 123

Project Tasks

vodoo project-task list --stage "In Progress"
vodoo project-task show 42
vodoo project-task comment 42 "Deployed to staging"
vodoo project-task attach 42 screenshot.png

Accounting Moves

vodoo account-move list --company "Rath Technologie" --year 2025 --state posted
vodoo account-move attachments 3552
vodoo account-move download-all 3552 --output "~/Belege 2025" --extension pdf

Projects

vodoo project list
vodoo project show 1
vodoo project note 1 "Sprint planning notes"

Helpdesk Tickets (Enterprise)

vodoo helpdesk list --stage "New" --assigned-to "John"
vodoo helpdesk show 123
vodoo helpdesk note 123 "Internal update"
vodoo helpdesk comment 123 "We're looking into this"
vodoo helpdesk download 456 --output ./attachments/

Knowledge Articles (Enterprise)

vodoo knowledge list --category workspace
vodoo knowledge create "Team Handbook" --body "# Onboarding\n\nWelcome!" --category workspace
vodoo knowledge show 123
vodoo knowledge note 123 "Updated installation section"

Timers / Timesheets

vodoo timer start 42
vodoo timer status
vodoo timer stop

Generic Model Operations

vodoo model read res.partner --domain='[["is_company","=",true]]' --field name --field email
vodoo model create res.partner name="Acme" email=info@acme.com
vodoo model update res.partner 123 phone="+123456789"
vodoo model delete res.partner 123
vodoo model call res.partner name_search --args='["Acme"]'

Security / Service Accounts

vodoo security create-groups
vodoo security assign-bot --login service-vodoo@company.com

For production use, run Vodoo with a dedicated least-privilege service account. See the Security Guide.

Documentation

Full docs at julian-r.github.io/vodoo:

Project Structure

src/vodoo/
├── __init__.py           # Public API: OdooClient, OdooConfig, exceptions
├── exceptions.py         # Exception hierarchy (VodooError and subclasses)
├── client.py             # OdooClient — delegates to transport layer
├── transport.py          # Transport abstraction (JSON-2 + legacy JSON-RPC)
├── config.py             # Pydantic configuration from env/.env files
├── auth.py               # Authentication and sudo utilities
├── _domain.py            # DomainNamespace base — shared CRUD, messaging, attachments
├── main.py               # CLI entry point (Typer) — not loaded by library imports
├── helpdesk.py           # Helpdesk ticket operations (enterprise)
├── project_tasks.py      # Project task operations
├── projects.py           # Project operations
├── crm.py                # CRM lead/opportunity operations
├── account_moves.py      # Accounting move operations
├── knowledge.py          # Knowledge article operations (enterprise)
├── generic.py            # Generic model CRUD
├── security.py           # Security groups, user management
├── timer.py              # Timer/timesheet start, stop, status
└── aio/                  # Async versions of all modules above
    ├── client.py         # AsyncOdooClient
    ├── _domain.py        # AsyncDomainNamespace base
    ├── transport.py      # Async JSON-2 + legacy transports
    └── ...               # Async domain modules (same API, awaitable)

Integration Tests

75+ tests per Odoo version against real instances in Docker:

./tests/integration/run.sh           # All community editions (17, 18, 19)
./tests/integration/run.sh 19        # Just Odoo 19
ENTERPRISE=1 ./tests/integration/run.sh 19   # Include enterprise

Development

uv sync --all-extras
uv run ruff check .
uv run ruff format .
uv run mypy src/vodoo

Publishing

Version is derived from git tags via hatch-vcs:

git tag vX.Y.Z && git push origin vX.Y.Z

GitHub Actions builds and publishes to PyPI automatically.

License

MIT — see LICENSE. Copyright (c) 2025 Julian Rath.

Built with Typer, Rich, Pydantic, uv, Ruff, and mypy.

Metadata

Release files for vodoo 3.2.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 vodoo 3.2.0
File Size Uploaded
vodoo-3.2.0.tar.gz 1.8 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for vodoo 3.2.0
File Interpreter ABI Platform
vodoo-3.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.9 MB

Release files / vodoo-3.2.0.tar.gz

Download URL vodoo-3.2.0.tar.gz
Size 1.8 MB
Tags Source
SHA-256 checksum
How to use checksums
020cd5352b08e35281555bd55fa51faeb8664fb7fd1eeb3f3adbfc930fdd1075
BLAKE2b-256 checksum
How to use checksums
f8c13b4ac6e46247b62ea32f7f15c94b6591d6a10faa262b88d8871d6c95322a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 24, 2026.

Transparency log

Release files / vodoo-3.2.0-py3-none-any.whl

Download URL vodoo-3.2.0-py3-none-any.whl
Size 110.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6a2ffb93ac28afb97b57ebbf21fcefdf75bbc88928248bd575a51e2fdb480f74
BLAKE2b-256 checksum
How to use checksums
cd9486f184b12ced9dab84207db7d3b424fa6409881046a1164532e4f5fefd02
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 24, 2026.

Transparency log

Release history Release notifications | RSS feed

4.3.1

2 release files

4.3.0

2 release files

4.2.0

2 release files

4.1.0

2 release files

4.0.0

2 release files

This release

3.2.0 This release

2 release files

3.1.1

2 release files

3.1.0

2 release files

3.0.0

2 release files

2.0.1

2 release files

2.0.0

2 release files

0.3.2

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