Fix

The API answers a malformed id as "not found" instead of a server error

An id in an API path that is not a valid UUID now gets the same 404 as a record that does not exist, rather than a server error.

Asking the API for something by an id that is not a valid UUID, such as GET /api/v1/projects/fda7bc05-0000/user_assignments, used to fail with a server error. It now gets exactly the answer a record that does not exist gets on that endpoint: the same status, usually 404, and the same message.

The same goes for id filters on lists. GET /api/v1/time_entries?project_id=…, /api/v1/invoices?client_id=… and /api/v1/expenses?user_id=… with an id that is not a UUID now return an empty list, as /api/v1/projects?client_id=… already did.

Nothing that worked before changes. A request with a valid id gets the same answer it always did.

← 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