Overview
The Find Time Entry endpoint allows you to search for time entries with comprehensive filtering options. This endpoint supports advanced search criteria including date ranges, project/task filters, team member selection, and billable status filtering for detailed time tracking analysis.This endpoint provides the most comprehensive filtering options among all find endpoints, allowing you to locate specific time entries based on multiple criteria for detailed time tracking and reporting workflows.
Authentication
All requests require a valid API key in the Authorization header:Find Time Entry
Request Body
The unique identifier of the workspace to search within. Must be a valid UUID format.Example:
"w1b2c3d4-e5f6-7890-abcd-ef0987654321"Search for time entries by description text. Performs case-insensitive partial matching.Example:
"Development work" or "meeting" (will match entries containing these terms)Filter time entries by specific team member ID.Example:
"tm1a2b3c4-d5e6-7890-abcd-ef1234567890"Filter time entries by specific project ID.Example:
"p1a2b3c4-d5e6-7890-abcd-ef1234567890"Filter time entries by specific task ID.Example:
"t1a2b3c4-d5e6-7890-abcd-ef1234567890"Filter by billable status. Accepts
"true" or "false".Example: "true" (only billable entries) or "false" (only non-billable entries)Filter by entry method. Accepts
"true" or "false".Example: "true" (manually entered) or "false" (tracked with timer)Filter entries created after this date. Must be ISO 8601 format.Example:
"2024-01-01T00:00:00Z"Filter entries created before this date. Must be ISO 8601 format.Example:
"2024-01-31T23:59:59Z"Filter entries with start time after this date. Must be ISO 8601 format.Example:
"2024-01-01T09:00:00Z"Filter entries with start time before this date. Must be ISO 8601 format.Example:
"2024-01-01T17:00:00Z"Filter entries with end time after this date. Must be ISO 8601 format.Example:
"2024-01-01T10:00:00Z"Filter entries with end time before this date. Must be ISO 8601 format.Example:
"2024-01-01T18:00:00Z"Filter entries with duration greater than or equal to this value (in seconds).Example:
3600 (1 hour minimum)Filter entries with duration less than or equal to this value (in seconds).Example:
28800 (8 hours maximum)Response
Success Response
Returns an array containing the matching time entry object with comprehensive details, or an empty array if no match is found:Unique time entry identifier (UUID format)
Date when the time entry occurred (ISO 8601 format)
Description of the work performed
Start time of the work session (ISO 8601 format, null if not tracked)
End time of the work session (ISO 8601 format, null if not tracked)
Duration of the work session in seconds
Duration of the work session in hours (calculated from seconds)
Whether this time entry is billable to the client
Whether this entry was manually entered or tracked with a timer
Unique identifier of the workspace containing this time entry
Name of the workspace containing this time entry
Unique identifier of the team member who logged this time entry
Full name of the team member who logged this time entry
Email address of the team member who logged this time entry
Role name of the team member who logged this time entry
Unique identifier of the associated project (null if no project)
Name of the associated project (null if no project)
Status of the associated project (null if no project)
Unique identifier of the associated client (null if no client)
Name of the associated client (null if no client)
Unique identifier of the associated task (null if no task)
Name of the associated task (null if no task)
Status of the associated task (null if no task)
Unique identifier of the associated timesheet (null if not part of a timesheet)
Status of the associated timesheet (null if not part of a timesheet)
Array of tags associated with this time entry
Number of tags associated with this time entry
ISO 8601 timestamp when time entry was created
ISO 8601 timestamp when time entry was last modified
No Results Response
When no matching time entries are found, returns an empty array:Error Responses
400 Bad Request - Invalid Parameters
400 Bad Request - Invalid Parameters
Solution: Ensure all parameters use correct formats (UUIDs, ISO 8601 dates, valid boolean strings)
401 Unauthorized
401 Unauthorized
500 Internal Server Error
500 Internal Server Error
Solution: Retry the request or contact support if the issue persists
Advanced Filtering Options
Date Range Filtering
The endpoint supports multiple date-based filters:Entry Date Filtering
Entry Date Filtering
Fields:
Purpose: Filter by when the time entry was created
Use Case: Find entries from specific time periods
date_after, date_beforePurpose: Filter by when the time entry was created
Use Case: Find entries from specific time periods
Work Session Filtering
Work Session Filtering
Fields:
Purpose: Filter by actual work session times
Use Case: Find entries from specific work hours or shifts
start_time_after, start_time_before, end_time_after, end_time_beforePurpose: Filter by actual work session times
Use Case: Find entries from specific work hours or shifts
Duration Filtering
Duration Filtering
Fields:
Purpose: Filter by work session duration
Use Case: Find short breaks, long work sessions, or specific duration ranges
duration_min, duration_maxPurpose: Filter by work session duration
Use Case: Find short breaks, long work sessions, or specific duration ranges
Project and Task Filtering
Filter time entries by their project or task associations:- Project Filtering: Use
project_idto find all time entries for a specific project - Task Filtering: Use
task_idto find all time entries for a specific task - Combined Filtering: Use both filters together for more specific results
Team Member Filtering
Filter time entries by the team member who logged them:- Individual Filtering: Use
team_member_idto find entries for a specific team member - Team Analysis: Combine with date filters to analyze individual productivity
Billable and Entry Method Filtering
Filter by business-relevant criteria:- Billable Status: Use
billableto separate billable from non-billable work - Entry Method: Use
manually_enteredto distinguish between timer-tracked and manually entered time
Zapier Integration Usage
Common Use Cases
Time Entry Analysis
Time Entry Analysis
Use Case: Analyze time tracking data for reporting, billing, or productivity analysis.Implementation: Use multiple filters to create detailed reports on time allocation, billable hours, or team productivity.
Billing and Invoicing
Billing and Invoicing
Use Case: Generate billing reports or create invoices based on billable time entries.Implementation: Filter by
billable: "true" and date ranges to get billable hours for specific periods.Project Time Tracking
Project Time Tracking
Use Case: Monitor time spent on specific projects or tasks for project management.Implementation: Use
project_id or task_id filters to track project progress and time allocation.Team Productivity Monitoring
Team Productivity Monitoring
Use Case: Monitor team member productivity and work patterns.Implementation: Use
team_member_id and date filters to analyze individual or team productivity.Timesheet Management
Timesheet Management
Use Case: Manage timesheet submissions and approvals.Implementation: Use
timesheet_id and timesheet_status to work with timesheet data.Zapier Field Mapping
When setting up Zapier actions, you can map these time entry fields:- Time Entry ID →
id(for referencing in other API calls) - Time Data →
duration,duration_hours,start_time,end_time(for time calculations) - Work Information →
description,date(for work documentation) - Billing Data →
billable(for billing workflows) - Project/Task Data →
project_id,project_name,task_id,task_name(for project association) - Team Member Data →
team_member_id,team_member_name,team_member_email(for team management) - Client Data →
client_id,client_name(for client association) - Tag Data →
tagsarray,tag_count(for categorization)
Time Entry Types
Timer-Tracked Entries
Entries created using the timer feature:- Characteristics: Have
start_timeandend_timevalues - Manually Entered:
false - Use Case: Real-time work tracking
Manually Entered Entries
Entries created by manually entering time:- Characteristics: May not have
start_timeandend_timevalues - Manually Entered:
true - Use Case: Retroactive time entry or estimated time
Best Practices
Search Optimization:
- Use specific date ranges to limit results and improve performance
- Combine multiple filters for more precise results
- Use description text search for finding specific types of work
- Consider using duration filters to find unusual time entries
- Cache frequently used filter combinations
Rate Limits
This endpoint follows standard API rate limiting:- Rate Limit: 100 requests per minute per API key
- Burst Limit: 10 requests per second
- Reset Period: Rolling 60-second window
Rate Limit Headers: Response headers include current usage information:
X-RateLimit-Limit: Maximum requests per windowX-RateLimit-Remaining: Remaining requests in current windowX-RateLimit-Reset: Timestamp when the limit resets