Skip to main content
GET
List tasks

Authorizations

X-API-Key
string
header
required

Your Flozy API key. Starts with flz_live_.

Query Parameters

page
integer
default:1

Page number.

Required range: x >= 1
limit
integer
default:25

Results per page (max 100).

Required range: 1 <= x <= 100
order
enum<string>
default:desc

Sort direction.

Available options:
asc,
desc

Full-text search.

status
enum<integer>

Keep only tasks with this status. Takes the same integer the task body and the task response use — 1 todo · 2 in progress · 3 completed · 4 in review — so a value can be copied straight out of a GET /tasks item. Exactly one value: there is no "any open status" form, so filter per status if you need several.

Available options:
1,
2,
3,
4
Example:

1

priority
enum<integer>

Keep only tasks with this priority, as the same integer used everywhere else on this resource: 1 low · 2 medium · 3 high. Exactly one value.

Available options:
1,
2,
3
Example:

3

lead_id
integer

Keep only tasks attached to this lead. Ids come from GET /leads. Tasks with no lead are never matched, and an id belonging to another agency matches nothing rather than erroring.

Required range: x >= 1
Example:

42

due_after
string<date>

Keep only tasks due on or after this date. Format is YYYY-MM-DD — a date-time is rejected here, not truncated, unlike the due_date body field, which accepts one and truncates it. The bound is inclusive. A task with no due_date is not matched.

Example:

"2026-01-01"

due_before
string<date>

Keep only tasks due on or before this date. Same format and rules as due_after; also inclusive, so passing the same value for both returns exactly the tasks due that day. A task with no due_date is not matched, so combining this with status is how you ask "what is overdue".

Example:

"2026-12-31"

Response

Paginated tasks.