API
Lynx API — Helpdesk bridge
Exposes lynx_helpdesk tickets, teams, and SLAs over the Lynx REST API.
lynx_api_helpdesk
· v19.0.1.0.0
· Premium
What this solves
Lynx API — Helpdesk bridge
Refactors the existing handcrafted /api/v1/tickets* controller in lynx_helpdesk onto the unified lynx_api framework. Demonstrates the full bridge pattern: declarative resource registration for plain CRUD, hand-written controllers for non-CRUD verbs (assign, resolve, close), and webhook emission from model overrides.
The legacy /api/v1/tickets route stays in place with a Deprecation header pointing to the new /lynx/api/v1/tickets surface — clients have a one-minor-version migration window before the old route is removed.
Key Features
Tickets resource — full CRUD at /lynx/api/v1/tickets with the Odoo helpdesk fields whitelisted; categories, teams, and SLAs are read-only sibling resources.
Custom action endpoints — POST /lynx/api/v1/tickets/{id}/assign, /resolve, /close mirror the helpdesk workflow methods, premium-gated and scope-checked.
Webhook events — ticket.created, ticket.assigned, ticket.resolved, ticket.closed fire automatically from the helpdesk_ticket model overrides; integrators can subscribe via /lynx/api/v1/webhooks.
Premium-gated — every endpoint inherits the api.access premium feature gate. No license, no calls.
Auto-Installation
auto_install=True so the bridge activates as soon as both lynx_api and lynx_helpdesk are present. Installing one without the other has no value — the bridge IS the productized helpdesk REST surface — so co-installation is the only meaningful state.
Depends on
Try Lynx API — Helpdesk bridge on your team.
Free trial, no credit card. Talk to sales when you're ready.