List time sheets
GET/api/v1/entry_sheets/time
Retrieves a paginated list of time entry sheets with optional filtering, sorting, and field selection.
Permissions: Users see their own sheets. Managers, approvers, and timekeeping assistants see sheets they have permission to view based on group-scoped roles.
Performance: By default, returns basic fields only. Use $keys=rows to include full entry
data (cells, notes, attachments), but this limits results to 10 sheets per request.
Filtering: Supports rich filtering on dates, states, totals, users, and related data.
See the $filter parameter documentation for details.
The Entry Sheet REST API was introduced in Journyx version 13.5.0 (25H2). Please ensure your Journyx instance is running this version or later to access these endpoints.
Entry Sheets do not respond to the DELETE HTTP method. You can zero-out
the entries in a sheet to effectively clear its contents, but the sheet
object itself remains for auditing and compliance reasons.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
- 503
Successful response
A 400 Bad Request is returned when the client request was malformed,
invalid, or otherwise could not be processed as-is. Usually, the cause for
the error is included in the error.message field of the response, and the
client should correct the request and try again.
See also Core Concepts#Error Responses.
Not authenticated - you must be signed in to access this resource. Please check the section of the documentation on authentication.
A 403 Forbidden response means that you are not authorized to perform
this action or access this object, or the object does not exist at all.
The client request may have been valid but the client does not have permission to access the requested resource or perform the requested action.
:::tip 403 Forbidden also used when objects don't exist
In most cases, the system will not return a 404 Not Found error response;
it returns 403 Forbidden both when the object doesn't exist at all,
and also when it exists but the client does not have permission to access it.
This is a security measure to prevent unauthorized users from determining
whether an object exists or not.
:::
See also Core Concepts#Error Responses.
Not found - the requested resource could not be found or does not exist. This may also include cases where the resource does exist, but the client does not have permission to access that resource.
:::tip 403 Forbidden also used when objects don't exist
In most cases, the system will not return a 404 Not Found error response;
it returns 403 Forbidden both when the object doesn't exist at all,
and also when it exists but the client does not have permission to access it.
This is a security measure to prevent unauthorized users from determining
whether an object exists or not.
:::
See also Core Concepts#Error Responses.
Internal server error; an unexpected error occurred on the server. This could be due to a temporary condition or might be the result of a bug in the server software. Also, in some cases, an incorrect client input can trigger this error, and can be resolved by correcting the input.
If the error persists, please contact support along along with the following details when possible:
- any error messages received from the server
- the full request and response details (full headers and body)
- a description of the steps that led to the error
- the time range when it occurred.
Service unavailable - the server is currently unable to handle the request, usually due to maintenance activity on the server. Check if the server's web interface is currently available, or try again later.