API
Lynx API — Expenses bridge
Expense capture and submission over the Lynx REST API.
lynx_api_hr_expense
· v19.0.1.0.0
· Standard
What this solves
Lynx API — Expenses bridge
Publishes hr.expense under /lynx/api/v1/expenses so an external tool can file expenses directly into the tenant instead of re-keying them in the backend. Built for capture: create and update are enabled against an explicit writable-field whitelist, and a custom verb submits an expense into the approval flow.
Odoo 19 removed hr.expense.sheet; expenses are flat records carrying their own state, so this bridge exposes a single resource rather than an expense/report pair.
Key Features
Expense capture over REST — POST an expense with description, date, category, quantity, amount, currency and paid-by mode; PATCH it while it is still a draft.
Submit verb — POST /lynx/api/v1/expenses/{id}/submit runs the standard action_submit transition, so an API-created expense reaches an approver without a detour through the UI.
Whitelisted surface — computed and workflow-owned fields such as state, price_unit and company_id are readable but never writable, so the API cannot short-circuit an approval.
Employee isolation — the dispatcher runs as the calling key's user with no elevation, so the standard expense record rules confine a key to the expenses its employee is allowed to see.
Scoped access — reads require expenses:read and writes require expenses:write, both enforced on every route.
Depends on
Try Lynx API — Expenses bridge on your team.
Free trial, no credit card. Talk to sales when you're ready.