Skip to main content

​
Overview

Everhour uses flat query parameters for filtering. There is no shared filter abstraction — the parameters available depend on the endpoint. Refer to the individual endpoint pages in the API Reference for the full list of accepted parameters.

​
Query parameters

Filters are passed as standard URL query parameters. There is no operator syntax such as field[gte]=, filter[status]=, or ?q=. Each parameter has a fixed name and accepted value type.

​
Text search

Use query= to search by name or title where supported. 
GET /projects?query=mobile
GET /tasks/search?query=onboarding

​
Date ranges

Use from=YYYY-MM-DD and to=YYYY-MM-DD to filter by date range. Both bounds are inclusive. Some endpoints also accept a single date=YYYY-MM-DD for an exact-day filter. 
GET /team/time?from=2026-05-01&to=2026-05-31
GET /tasks/ev:123/time?date=2026-05-04

​
Boolean parameters

Boolean parameters accept true or false. Some parameters use a hyphenated form in the URL (for example, exclude-closed=true). 
GET /projects/ev:456/tasks?exclude-closed=true
GET /tasks/search?query=setup&searchInClosed=true
GET /team/time?from=2026-05-01&to=2026-05-31&onlyWithTask=true

​
Pagination

Use limit= and page= to paginate results where supported. 
GET /projects?limit=50&page=2

​
Sorting

Result order is fixed server-side. There are no sort=, order=, sort_by=, or similar parameters on any endpoint. You cannot change the sort direction or field through the API.

​
Per-endpoint filter reference

EndpointSupported filter parameters
GET /projectsquery=, platform=, limit=, page=
GET /projects/{id}/tasksquery=, limit=, page=, exclude-closed=
GET /tasks/searchquery=, limit=, searchInClosed=
GET /tasks/{id}/timefrom=, to=, date=, limit=, page=, onlyWithTask=
GET /team/timefrom=, to=, date=, limit=, page=, onlyWithTask=
GET /clientsquery=
GET /timecardsfrom=, to=

​
Example

The following example fetches time entries for the team within a date range. 
curl -X GET "https://api.everhour.com/team/time?from=2026-05-01&to=2026-05-31" \
  -H "X-Api-Key: YOUR_API_KEY"
The filter parameters accepted by each endpoint are documented on the individual endpoint pages in the API Reference.