GuidesAPI DocsChangelogMy AppsSeismic Exchange
API Docs

Get all tasks

get
https://api.seismic.com/programs/v2/spaces//tasks

Retrieves a list of tasks within a space with extensive filtering capabilities including date ranges, assignees, statuses, priorities, programs, parent tasks, custom properties, and associations. This endpoint supports cursor-based pagination and flexible sorting for building task management interfaces and reporting systems.

Key Features:

  • Query tasks using multiple filtering criteria simultaneously including date ranges, assignees, priorities, statuses, programs, parent relationships, custom properties, and associations
  • Support hierarchical task structures with parent-child filtering
  • Perform flexible sorting on multiple fields for optimal display ordering
  • Navigate large datasets efficiently with cursor-based pagination
  • Optionally include association data for detailed task views
  • Results include complete task metadata such as assignees, due dates, priorities, and status information

Authorization Logic:

  1. User must have a valid JWT token with viewing or management scopes
  2. User must have role-based permissions to view tasks
  3. Tasks are filtered based on user's access permissions

Usage Example:

Retrieve all high-priority tasks assigned to specific users with due dates within the next week for dashboard display, or filter by program and status to track program execution.

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
date-time

Filter for tasks with planned end date (due date) on or after this ISO 8601 date-time value (inclusive boundary). Use to find tasks due within a specific timeframe or starting from a particular date. Combine with plannedEndDateTo for date range queries. Example value 2025-07-01T00:00:00Z for tasks due July 1st or later.

date-time

Filter for tasks with planned end date (due date) before this ISO 8601 date-time value (exclusive boundary). Use with plannedEndDateFrom to create date ranges for finding tasks due within specific periods. Exclusive means tasks with this exact date-time are not included. Example value 2025-08-01T00:00:00Z for tasks due before August 1st.

date-time

Filter for tasks with planned start date on or after this ISO 8601 date-time value (inclusive boundary). Use to find tasks scheduled to begin within a specific timeframe or starting from a particular date. Combine with plannedStartDateTo for date range queries capturing tasks starting within defined periods.

date-time

Filter for tasks with planned start date before this ISO 8601 date-time value (exclusive boundary). Use with plannedStartDateFrom to create date ranges for finding tasks starting within specific periods. Exclusive means tasks with this exact date-time are not included. Useful for scheduling and capacity planning queries.

date-time

Filters tasks to include only those created on or after this timestamp, expressed in ISO 8601 format with timezone (e.g., 2024-01-15T00:00:00Z). The boundary is inclusive, meaning tasks created exactly at this moment are included in results. Useful for time-range queries to find recently created tasks or tasks created within a specific period when combined with createdAtTo. Essential for synchronization scenarios and audit trail queries.

date-time

Filters tasks to include only those created before this timestamp, expressed in ISO 8601 format with timezone (e.g., 2024-02-01T00:00:00Z). The boundary is exclusive, meaning tasks created exactly at this moment are excluded from results. Combine with createdAtFrom to establish a creation date window, such as filtering all tasks created in January 2024 or during a specific sprint period.

date-time

Filters tasks to include only those last modified on or after this timestamp, expressed in ISO 8601 format with timezone (e.g., 2024-01-15T00:00:00Z). The boundary is inclusive, capturing tasks updated exactly at this moment. Particularly useful for synchronization scenarios where you need to fetch tasks modified since the last sync operation, change tracking, and incremental update workflows.

date-time

Filters tasks to include only those last modified before this timestamp, expressed in ISO 8601 format with timezone (e.g., 2024-02-01T00:00:00Z). The boundary is exclusive, excluding tasks updated exactly at this moment. Combine with updatedAtFrom to identify tasks modified during a specific timeframe, such as changes made during a particular sprint or time period for audit and reporting purposes.

ids
array of strings

Filters the result set to include only tasks matching one or more specified task identifiers. Accepts a comma-separated list of base64url-encoded task IDs (e.g., taskABC123,taskXYZ789). Useful for bulk retrieval operations where you need to fetch specific tasks by their known identifiers, such as refreshing status for tasks displayed in a dashboard or verifying task details after a batch operation.

ids
string

Filters tasks by performing a case-insensitive partial text match on the task title field. Supports substring matching, so a search for Marketing will match titles like Q4 Marketing Campaign, Marketing Review, and Email Marketing Task. Particularly useful for user-driven search interfaces where users type keywords to find relevant tasks without knowing exact titles.

string

Filters tasks by performing a case-insensitive partial text match on the task description field. Allows substring matching within the description content, enabling searches for tasks containing specific keywords, program names, or requirements details. Useful for finding tasks related to a particular feature, bug fix, or work item when the title alone is insufficient for identification.

assigneeIds
array of strings

Filters tasks to include only those assigned to one or more specified users. Accepts a comma-separated list of base64url-encoded user identifiers (e.g., userABC123,userXYZ789). Returns tasks where any of the specified users appear in the task assignee list. Essential for views showing workload for specific team members or filtering My Tasks displays to show assignments for the current user.

assigneeIds
priorities
array of strings

Filters tasks to include only those matching one or more specified priority levels from the enumerated set (critical, high, medium, low, noPriority). Accepts a comma-separated list of priority values. Returns tasks where the priority matches any of the specified values. Commonly used to create filtered views showing high-priority work items, critical blockers requiring immediate attention, or low-priority tasks for backlog grooming.

priorities
string

Filters tasks by matching against user-defined keyword tags associated with each task. Accepts a comma-separated string of keyword values. Returns tasks tagged with any of the specified keywords. Keywords function as flexible categorization metadata, enabling cross-cutting organization schemes like filtering by sprint label, technology stack, department, or program phase independent of formal hierarchical structures.

assignerIds
array of strings

Filters tasks to include only those created or assigned by one or more specified users. Accepts a comma-separated list of base64url-encoded user identifiers (e.g., userABC123,userXYZ789). Returns tasks where any of the specified users appear as the assigner. Useful for tracking task delegation patterns, manager oversight views showing work distributed by team leads, or audit scenarios requiring visibility into who created specific work items.

assignerIds
stepIds
array of int32s

Filters tasks to include only those currently in one or more specified workflow steps from their associated status schema. Accepts a comma-separated list of integer step identifiers (e.g., 1,3,5). Returns tasks at any of the specified workflow stages. Essential for kanban board views, workflow stage reports showing tasks In Progress or Blocked, and status-based automation triggers requiring identification of tasks in specific states.

stepIds
string

Filters tasks to include only those using the specified workflow status schema identifier. Each space may have multiple status schemas defining different workflow configurations for different types of work. Useful for segmenting tasks by workflow type, such as separating bug tracking workflows from feature development workflows, or filtering tasks following a specific approval process. Accepts a single base64url-encoded status schema ID.

string

Opaque pagination cursor token returned from the previous page response, used to retrieve the next page of results in a cursor-based pagination sequence. Do not construct cursor values manually; always use the nextCursor value from the previous response. Cursor-based pagination ensures consistent results even when the underlying data changes between page requests, avoiding issues with offset-based pagination where inserted or deleted records can cause result skipping or duplication.

int32

Specifies the maximum number of task records to return in a single page response, capped at a system-defined maximum (typically 100-500). Controls page size for pagination to balance response payload size with the number of API calls needed. Smaller limits reduce memory usage and response time but require more requests for complete data sets. Larger limits minimize round trips but increase latency and payload size.

sort
array of strings

Defines the sort order for returned tasks using field:direction pairs (e.g., createdAt:desc, updatedAt:asc). Accepts an array of sort criteria applied in sequence, with earlier criteria taking precedence. Common sort fields include createdAt, updatedAt, title, and priority. Direction values are asc (ascending) or desc (descending). Multi-field sorting enables complex orderings like sorting by priority descending, then by creation date ascending for equal priorities.

sort
boolean

Controls whether the response includes subtasks nested under parent tasks in the hierarchical task structure. When true, returns both parent tasks matching the filter criteria and all their descendant subtasks regardless of whether subtasks match filters. When false or omitted, returns only tasks directly matching the filter criteria without including their subtasks. Essential for complete task tree retrieval or flat task list displays.

programIds
array of strings

Filters tasks to include only those associated with one or more specified programs. Accepts a comma-separated list of base64url-encoded program identifiers (e.g., programABC123,programXYZ789). Returns tasks linked to any of the specified programs. Programs provide hierarchical organization for related tasks, enabling portfolio management views, program-level filtering, and program-scoped reporting. Useful for dashboards showing work items within specific initiatives or programs.

programIds
boolean

Filters tasks based on whether they are associated with any program. When true, returns only tasks that have been linked to at least one program. When false, returns only standalone tasks not associated with any program. Useful for identifying orphaned tasks, program coverage reports, or filtering programmatic work versus ad-hoc tasks. Mutually exclusive filtering with programIds parameter for different use cases.

customProperties
object

Filter by custom property values using property ID and value criteria.

Syntax: customProperties[{propertyId}][operator]={operator}&customProperties[{propertyId}][id]=%22{valueId}%22

Note: Both id and value parameters must be enclosed in quotes and URL-encoded (%22).

Example: customProperties[abc][operator]=Equal&customProperties[abc][id]=%22xyz%22

followerIds
array of strings

Filters tasks to include only those followed by one or more specified users. Accepts a comma-separated list of base64url-encoded user identifiers (e.g., userABC123,userXYZ789). Returns tasks where any of the specified users appear in the follower list. Followers receive notifications about task changes without being directly assigned. Useful for stakeholder views, manager oversight of team work, or filtering tasks of interest to specific users who are tracking but not directly responsible.

followerIds
associatedNodeIds
array of strings

Filters tasks to include only those associated with one or more specified content entities or workspace resources. Accepts a comma-separated list of GUID-formatted entity identifiers (e.g., 56d7d33f-1d42-461b-85eb-26b7b2872c88). Returns tasks linked to any of the specified entities through association relationships. Associations connect tasks to related content items, enabling content-centric task views, document workflow tracking, and resource-based task filtering for content management scenarios.

associatedNodeIds
creatorIds
array of strings

Filters tasks to include only those originally created by one or more specified users. Accepts a comma-separated list of base64url-encoded user identifiers (e.g., userABC123,userXYZ789). Returns tasks where any of the specified users appear as the creator. Distinct from assignerIds which tracks who assigned the task, creatorIds identifies the original author. Useful for user activity reports, creator productivity metrics, or filtering tasks authored by specific team members.

creatorIds
boolean

Controls whether the response includes detailed association data for each task, such as linked content entities, workspace resources, or related entities. When true, the response includes expanded association objects with full metadata. When false or omitted, association data is excluded to reduce payload size and improve response time. Essential for views requiring complete task context with linked resources, but can be omitted for lightweight task list displays focused solely on task properties.

string

Filters tasks to include only those with the specified parent task identifier, enabling hierarchical task filtering. Accepts a single base64url-encoded parent task ID to return direct child tasks. Use the special value noParent to return only top-level tasks without a parent (root tasks). Essential for building tree views, parent-child drill-downs, subtask panels, or filtering top-level work items versus nested subtasks in hierarchical task structures.

Responses

Updated 1 day ago

Language
Response 
Click Try It! to start a request and see the response here! Or choose an example:
application/json
Updated 1 day ago