API
Lynx API — Timesheets bridge
Timesheet entry over the Lynx REST API.
lynx_api_hr_timesheet
· v19.0.1.0.0
· Standard
Ce que cela résout
Lynx API — Timesheets bridge
Publishes timesheet lines under /lynx/api/v1/timesheets so time tracked in an external tool can be logged straight against a project or task. Create, update and delete are enabled against an explicit writable-field whitelist.
Timesheets are stored on account.analytic.line, the same table that carries accounting analytic entries. The resource therefore declares a base domain restricting it to project-linked lines, so the slug cannot be used to read or write analytic entries that are not timesheets.
Key Features
Log time over REST — POST a line with project, task, date, duration and description; PATCH or DELETE a correction afterwards.
Constrained to timesheets — a base domain of [('project_id', '!=', False)] filters the list, answers 404 on any out-of-scope id, and rejects a create that would land outside it, so accounting analytic entries stay unreachable through this slug.
Whitelisted surface — the monetary and accounting columns on the underlying model are neither readable nor writable here; only the timesheet columns are exposed.
Employee isolation — the dispatcher runs as the calling key's user with no elevation, so the standard timesheet record rules confine a key to the lines its employee is allowed to see.
Scoped access — reads require timesheets:read and writes require timesheets:write, both enforced on every route.
Dépend de
Essayer Lynx API — Timesheets bridge de votre équipe.
Essai gratuit, sans carte de crédit. Parlez à l'équipe des ventes quand vous êtes prêt.