Odoo (via Apideck)

Access Odoo through Apideck's CRM, Accounting unified API — one of 21 CRM connectors that share the same method surface. Code you write here ports to Salesforce, HubSpot, Pipedrive and 17 other CRM connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Odoo plumbing.

Beta connector. Odoo is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

• Apideck serviceId: odoo
• Unified APIs: CRM, Accounting
• Auth type: basic
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: CRM · Accounting
• Odoo docs: https://www.odoo.com/documentation/
• Homepage: https://www.odoo.com/

When to use this skill

Activate this skill when the user explicitly wants to work with Odoo — for example, "pull contacts in Odoo" or "sync leads in Odoo". This skill teaches the agent:

1. Which Apideck unified API covers Odoo (CRM, Accounting)
2. The correct serviceId to pass on every call (odoo)
3. Odoo-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• CRM: https://specs.apideck.com/crm.yml · API Explorer
• Accounting: https://specs.apideck.com/accounting.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List contacts in Odoo
const { data } = await apideck.crm.contacts.list({
  serviceId: "odoo",
});

Portable across 21 CRM connectors

The Apideck CRM unified API exposes the same methods for every connector in its catalog. Switching from Odoo to another CRM connector is a one-string change — no rewrite, no new SDK.

// Today — Odoo
await apideck.crm.contacts.list({ serviceId: "odoo" });

// Tomorrow — same code, different connector
await apideck.crm.contacts.list({ serviceId: "salesforce" });
await apideck.crm.contacts.list({ serviceId: "hubspot" });

This is the compounding advantage of using Apideck over integrating Odoo directly: code against the unified CRM API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

Odoo via Apideck Accounting

Odoo is an open-source ERP with cloud (Odoo.com) and self-hosted deployments. Broad module coverage; Apideck targets the Accounting module.

Entity mapping

Odoo entity	Apideck Accounting resource
Customer Invoice (account.move with type "out_invoice")	invoices
Vendor Bill (account.move with type "in_invoice")	bills
Payment	payments
Bill Payment	bill-payments
Credit Note (refund)	credit-notes
Journal Item (account.move.line)	journal-entries
Account (account.account)	ledger-accounts
Partner (res.partner, customer)	customers
Partner (res.partner, supplier)	suppliers
Tax (account.tax)	tax-rates
Product	invoice-items
Analytic Account	tracking-categories
Company (res.company)	companies, subsidiaries
Bank Account	bank-accounts
Department	departments
Expense (hr.expense)	expenses

Coverage highlights

• ✅ Full CRUD on invoices, bills, payments, customers, suppliers
• ✅ Journal entries via account.move lines
• ✅ Analytic accounting (tracking categories)
• ✅ Multi-company (subsidiaries)
• ✅ Bank feeds for reconciliation
• ⚠️ Odoo has many custom modules (Studio, custom fields) — coverage varies per installation; use Proxy for module-specific models
• ❌ Other Odoo modules (Sales, CRM, HR, Manufacturing) — use Proxy or a module-specific connector

Auth notes

• Type: Basic auth (username / API key), managed by Apideck Vault
• Database binding: Odoo users belong to one database (dbname). Multi-db setups require separate connections.
• Self-hosted vs cloud: Apideck connects to any reachable Odoo instance — works for self-hosted provided the URL is accessible.
• Version sensitivity: Odoo's model may change across versions (17 → 18 → 19). Apideck abstracts common operations; custom model access via Proxy.

Example: list customer invoices

const { data } = await apideck.accounting.invoices.list({
  serviceId: "odoo",
  filter: { status: "open" },
});

Example: read custom Odoo model via Proxy

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: odoo" \
  -H "x-apideck-downstream-url: /jsonrpc" \
  -H "x-apideck-downstream-method: POST"

Sibling connectors

Other CRM connectors that share this unified API surface (same method signatures, just change serviceId):

salesforce, hubspot, pipedrive, zoho-crm, activecampaign, close, microsoft-dynamics, teamleader, and 12 more.

Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):

access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.

See also

• Apideck connection guide for Odoo
• CRM OpenAPI spec · API Explorer
• Accounting OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Odoo official docs