---
title: "My Tasks"
method: GET
path: "/v2.0/tasks/my-tasks"
tags: ["Tasks & Appointments V2"]
---

# My Tasks

`GET /v2.0/tasks/my-tasks`

Returns tasks assigned to the caller, sorted by startTime descending. Supports cursor-based pagination via currentId (offset) + limit.

Notes:
- currentId must be >= 0 (INVALID_PARAMETER otherwise).
- limit must be in [1, 100] (LIMIT_NOT_VALID otherwise).
- timeZoneCode selects how start/end times are formatted; when omitted, the caller's configured timezone is used.

## Query parameters

- `userId` integer, nullable — User ID to query tasks for. Defaults to the current authenticated user if not provided.
- `currentId` integer — Cursor-based pagination anchor. Pass the last returned item's id to fetch the next page. Default 0 (start from beginning).
- `limit` integer — Page size, 1–100. Default 10.
- `timeZoneCode` string, nullable — IANA timezone code (e.g. 'America/New_York'). If not provided, falls back to the user's configured timezone.

## Headers

- `Authorization` string, required

## Response `200`

Tasks assigned to the caller.

- TaskV2ListResponse — Wrapped response for GET /v2.0/tasks and GET /v2.0/tasks/my-tasks. Task entries are returned under the 'tasks' key.
  - `tasks` TaskResponseV2[] — Tasks and / or appointments matching the query.
    - `id` integer — The Id of the task
    - `leadId` integer — The lead(Id) associated with the task
    - `creatorId` integer — The creator's Id of the task
    - `content` string — The content of the task
    - `type` string — The type of the task
    - `startAt` string — When this task/appointment starts. ISO8601 format with timezone, e.g., '2026-03-01T15:00:00GMT'
    - `endAt` string — When this task/appointment ends (or expected completion time for regular tasks). ISO8601 format with timezone
    - `timeZoneCode` string — Timezone code for this task/appointment
    - `allDay` boolean — Whether this is an all-day event
    - `finishFlag` boolean — If the task is finished or not
    - `overdueFlag` boolean — If the task is overdue or not
    - `finishTime` string — The finish time of the task
    - `createTime` string — The create time of the task
    - `lastUpdate` string — The last update time of the task
    - `leadName` string — The lead's name associated with the task
    - `leadEmail` string — The lead's email associated with the task
    - `leadPhone` string — The lead's phone associated with the task
    - `leadFirstName` string — The lead's first name of the task
    - `leadLastName` string — The lead's last name of the task
    - `reminderType` integer — The reminder's type of the task
    - `assignedRole` string — The role of the task assigned to
    - `assignedUser` string — The user of the task assigned to
    - `teamId` integer — The team's Id associated with the task
    - `subject` string — The subject of the task
    - `body` string — The body of the task
    - `assignedUserId` integer — The user's Id of the task assigned to
    - `pipelineId` integer — The pipeline(Id) of the associated lead
    - `queryInfo` string — The queryInfo of the task
    - `leadUserId` integer — The lead's user Id associated with the task
    - `queryId` integer — The queryId of the task
    - `address` string — Address for appointment type tasks

## Other responses

- `400` — currentId < 0 (INVALID_PARAMETER) or limit out of range (LIMIT_NOT_VALID).
- `401` — Missing or invalid authentication token.
- `500` — Internal server error.

---

[API](https://skmtc.net/lofty/apis/lofty-service-open-apis.md) · [All operations](https://skmtc.net/lofty/apis/lofty-service-open-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lofty/lofty-service-open-apis/versions/23e640467118/schema)