Get tasks assigned to the authenticated user

Retrieves tasks from a workspace where the authenticated user has involvement as creator, assignee, assigner, or follower. This endpoint provides a personalized task view filtering the workspace's full task list to show only tasks relevant to the current user, enabling users to quickly access their personal task queue, track assignments they've made, and monitor tasks they're following. Returns a paginated list with cursor-based navigation supporting efficient retrieval of large personal task collections. Use this endpoint when building My Tasks dashboards, personal productivity views, or notification systems that need to show user-specific task lists. For example, call this endpoint to display a user's assigned tasks on their homepage, show tasks they created that need follow-up, or list tasks they're following for status updates. The response includes complete task details (title, description, dates, priority, status, assignee information, custom properties) along with pagination metadata for seamless navigation through large task sets. Supports optional filtering by title for search functionality and flexible sorting by creation date, update date, or other task attributes to organize personal task views.

Key Features:

  • Automatically filters tasks to those where current user is creator, assignee, assigner, or follower for personalized views

  • Returns complete task details including title, description, dates, priority, status, assignee, custom properties, and metadata

  • Supports cursor-based pagination for efficient navigation through large personal task collections

  • Enables title-based filtering for quick task search within user's personal queue

  • Provides flexible sorting options (createdAt, updatedAt, plannedEndDate) for organizing personal task lists

  • Includes count and limit metadata for building pagination UI components

    Authorization Logic:

  • User must have view or manage permissions for the specified space (seismic.programs.view or seismic.programs.manage)

  • Only returns tasks where authenticated user has direct involvement (creator/assignee/assigner/follower relationship)

  • Respects task-level access controls and space permissions for proper data isolation

  • Returns 403 if user lacks required view permissions for the space

  • Returns 404 if space does not exist or user has no access

Usage Examples:

Example 1: Get my assigned tasks for today's work

Call GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/tasks/my?sort=plannedEndDate:asc&limit=50 to retrieve up to 50 tasks where the current user is involved, sorted by due date ascending to prioritize urgent tasks. Use the returned task list to populate a My Tasks widget showing what needs attention today.

Example 2: Search my tasks for specific title keyword

Call GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/tasks/my?title=presentation&limit=20 to find tasks containing 'presentation' in the title within the user's personal task queue. Useful for quick search functionality in task management interfaces.

Example 3: Paginate through large personal task list

Initial call: GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/tasks/my?limit=50 returns first 50 tasks and a cursor token. Next page: GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/tasks/my?cursor=eyJjdXJzb3IiOjUwfQ&limit=50 retrieves the next 50 tasks. Continue until cursor is null.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
length between 7 and 22

The unique identifier of the space containing the target entity. This determines the scope of entity queries and ensures proper access control. The space must be accessible to the authenticated user with appropriate permissions. It can be the unique identifier (GUID) of the space or the word "default" to indicate the default programs space. Common values include "default" and "rkr83lapKkyCJuLLWqLqzB".

Query Params
sort
array of strings

Optional array of sort criteria to order the returned tasks in the response. Each criterion uses the format 'field:direction' where field is a sortable task property (createdAt, updatedAt, plannedStartDate, plannedEndDate, title, priority) and direction is either 'asc' (ascending) or 'desc' (descending). Multiple sort criteria are applied in array order with the first criterion taking precedence. Common examples: 'plannedEndDate:asc' for urgency-based ordering showing soonest due dates first, 'createdAt:desc' for newest tasks first, 'updatedAt:desc' for recently modified tasks. Default order when omitted is system-defined (typically by creation date descending).

sort
string

Optional text filter to search for tasks by title keyword or phrase. Performs partial, case-insensitive matching on task titles, returning only tasks where the title contains the specified text. Use for implementing search functionality in task lists, enabling users to quickly find tasks by name or keyword. For example, 'presentation' would match tasks titled 'Q4 Sales Presentation', 'Update Presentation Deck', or 'Presentation Review'. Leave empty or omit to retrieve all tasks without title filtering. Combine with other filters and sorting for refined searches.

string

Optional pagination cursor token obtained from a previous response to retrieve the next page of results. This opaque string (typically base64-encoded JSON) maintains the query state including position, sort order, and filters. On the initial request, omit this parameter to retrieve the first page. Use the cursor value returned in the response to fetch subsequent pages by including it in the next request. Continue pagination until the response returns a null cursor indicating no more results. Cursor tokens are temporary and may expire after a period of inactivity. Do not construct cursor values manually; always use values returned by the API.

int32

Optional maximum number of tasks to return in a single page of results. Controls pagination page size for managing response payload sizes and UI rendering performance. Valid range is typically 1-100 with a default of 50 when omitted. Use lower limits (10-25) for initial page loads in UI for faster response times, and higher limits (50-100) for bulk operations or background processing. The actual number of returned items may be less than the limit if fewer matching tasks exist or the end of results is reached. Combine with cursor parameter for paginated navigation through large task lists.

Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json