Fix

API time reports filter by client, project, engagement and person

The API's time reports now honor client, project, engagement, person and billable filters, refuse parameters they do not take, the engagements report gives each engagement's id, and project and time entry responses include the names they were missing.

GET /api/v1/reports/time/… ignored client_id and engagement_id and returned the whole workspace's report as if it were filtered. Time reports now take client_id, project_id, engagement_id, user_id and billable, and every API report answers a parameter it does not take with an error that names it, instead of quietly leaving it out. Rows of GET /api/v1/reports/time/engagements now carry engagement_id beside engagement_name (null for time on projects in no engagement), so two engagements with the same name can be told apart.

GET /api/v1/projects/{id}, and the response to creating or updating a project, now include the client's name. Creating a time entry through the API now answers with the person's, project's and task's names, the same as reading the entry back.

In the assistant and over MCP, the budget answers now include each project's id and its client's id, so a follow-up question about one project does not have to look it up again by name.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free