Task-view feeds with cursor pagination (forces view_type=TV)

GET /task/v1/feeds/list/tasks

Operation id: retrieveFeedsTasks

Description

Retrieves a paginated list of task-only feeds. Identical to retrieve-type=list but view_type is automatically set to TV (Task View) server-side, regardless of any value sent by the client. Sending view_type is harmless but it will be overridden.

Supports cursor-based pagination (same rules as /feeds/list), sorting, projections, and all standard feed filters.

Cursor-Based Pagination

  1. Initial: GET /task/v1/feeds/list/tasks?status=N&limit=20
  2. Next page: add starting_after=<next_cursor from response>
  3. Prev page: add ending_before=<previous_cursor from response>
  4. Use only one of starting_after / ending_before per request (both → E112)
  5. limit clamped to 1–100 (below 1 defaults to 20, above 100 caps at 100)

Projections — Default Fields

When projections is omitted, the following fields are returned per feed object:

feed_key, feed_title, message_type, status, priority, feed_type, feed_type_id, cluster_id, cluster_child_id, start_date_time, end_date_time, display_launch_date, create_dtm, last_updated_time, task_count, overdue_task_count, pin, favorite_flag, acknowledged_flag, is_confidential, has_survey, title_css, panel_config, assign_to_desc, has_comments, enable_comment, future_feed, show_why_url, has_action, enable_action, show_how_url, has_history, has_user_notes, has_actions, has_contents, has_key_attributes

Projections — Additional Available Fields

transaction_key, feed_owner, feed_type_id_desc, ext_link_info, dept_id, end_date_utc, display_start_date, last_action_time_in_millis, profile_id, display_date, has_predecessor, show_acknowledge, last_updated_time_in_millis, event_date, additional_attributes, show_claim, promote_to_note_flag, update_all_mul_asg_task_attr, flag, is_edited, allow_future_quick_links, thread_flag, acknowledge_flag, txn_dtm, lock_status, start_date_utc, unit_id, last_action_time, action_taken_flag, time_to_act, feed_description, feed_params, event_end_date, watch_flag, follow, user_id, feed_task_count, display_end_date


Error Scenarios

ScenarioHTTPError CodeMessage
Missing / invalid X-reflexis-csrf-token-X401E202User session is invalid
Both starting_after and ending_before400E112Cannot use both starting_after and ending_before simultaneously.
No data found200E404No data found

Error Codes Reference

CodeDescription
E112Both pagination cursors provided simultaneously
E202Invalid or expired authentication token
E404No data found for the given filter criteria

Tags: MyWorkFeeds

Parameters

Query parameters

NameTypeRequiredDescription
acknowledge_flagintegerNoAcknowledge filter: -1=all, 0=not acknowledged, 1=acknowledged
com_attr_valstringNoCommunication attribute value filter
cut_off_timeinteger (int64)NoCut-off time in epoch ms
ending_beforestringNoBackward pagination cursor (use previous_cursor from previous response)
favoriteintegerNoFavorite filter: -1=all, 0=not favorite, 1=favorite
feed_titlestringNoText search on feed title (URL-encoded, auto-decoded)
feed_type_idstringNoFeed type ID filter
filter_idstringNoSystem filter ID
followintegerNoFollow filter: -1=all
limitintegerNoMax records per page (clamped to 1-100)
message_typestringNoFeed message type code
msg_attr_valstringNoMessage attribute value filter
pinintegerNoPin filter: -1=all, 0=not pinned, 1=pinned
prioritystringNoComma-separated priority integers
projectionsstringNoComma-separated field names to include in each feed object
promote_to_note_flagintegerNoPromote-to-note filter
return_formatstringNoReturn format: J=JSON
return_typestringNoReturn type filter
selected_datesstringNoComma-separated dates in YYYYMMDD format
sort_bystringNoComma-separated sort columns
sort_orderstringNoComma-separated sort directions: A=ascending, D=descending
starting_afterstringNoForward pagination cursor (use next_cursor from previous response)
statusstringNoComma-separated status codes: N, R, P, O, C, F, E
tagsstringNoTags filter
task_viewstringNoDisplay view: P=Project View, T=Task View
week_datesstringNoComma-separated week dates in YYYYMMDD format

Security

  • ApiKeyHeader (apiKey)
    • APIGEE API key header validated by VerifyAPIKey policy.
  • AuthTokenHeader (apiKey)
    • Session authentication token validated server-side against the user session store.

Responses

200 — Success — {feed_details[], previous_cursor, next_cursor, has_more, last_fetch_time}

list response fields:

FieldTypeDescription
feed_details[]ArrayFeed objects (fields controlled by projections)
has_moreBooleantrue if more records available after current page
next_cursorStringOpaque cursor for next page — use with starting_after. null if no more pages.
previous_cursorStringOpaque cursor for previous page — use with ending_before. null if on first page.
last_fetch_timeLongEpoch ms when data was fetched

count response fields:

FieldTypeDescription
count_data.priorities[]ArrayEach: name (priority), id, value (count as String)
count_data.totalIntegerTotal count across all priorities

list-latest response fields:

FieldTypeDescription
feed_list_latest[]ArrayFeed objects changed/added since from_time
statusStringOK on success

Content type: application/json

400E111 — Invalid retrieve-type (allowed: list, count, list-latest).

E112 — Both starting_after and ending_before provided simultaneously. E114 — start_date required for count. E115 — end_date required for count. E116 — Refresh interval exceeded for list-latest.

Content type: application/json

401 — Missing or invalid X-reflexis-csrf-token-X session token

Content type: application/json

500 — Unexpected server-side error

Content type: application/json

Response models

200 — Success — {feed_details[], previous_cursor, next_cursor, has_more, last_fetch_time}

list response fields:

FieldTypeDescription
feed_details[]ArrayFeed objects (fields controlled by projections)
has_moreBooleantrue if more records available after current page
next_cursorStringOpaque cursor for next page — use with starting_after. null if no more pages.
previous_cursorStringOpaque cursor for previous page — use with ending_before. null if on first page.
last_fetch_timeLongEpoch ms when data was fetched

count response fields:

FieldTypeDescription
count_data.priorities[]ArrayEach: name (priority), id, value (count as String)
count_data.totalIntegerTotal count across all priorities

list-latest response fields:

FieldTypeDescription
feed_list_latest[]ArrayFeed objects changed/added since from_time
statusStringOK on success

Content type: application/json

Schema

JSON object (structure varies by endpoint).

{
  "type": "object",
  "description": "JSON object (structure varies by endpoint)."
}

Example:

{
  "status": "OK",
  "feed_details": [
    {
      "feed_key": 44814719,
      "feed_title": "Your%20request%20for%20download",
      "status": "R",
      "priority": 1,
      "message_type": "DOWNLOADFILEMSG",
      "cluster_id": "SYSADMIN_1773851291103",
      "cluster_child_id": "-1",
      "start_date_time": "2026-03-18 11:28:13",
      "end_date_time": "2026-03-25 11:28:08",
      "pin": 0,
      "favorite_flag": false,
      "has_survey": false,
      "enable_action": true
    }
  ],
  "previous_cursor": null,
  "next_cursor": "eyJza2lwIjoyMH0=",
  "has_more": true,
  "last_fetch_time": 1774373200310
}

400E111 — Invalid retrieve-type (allowed: list, count, list-latest).

E112 — Both starting_after and ending_before provided simultaneously. E114 — start_date required for count. E115 — end_date required for count. E116 — Refresh interval exceeded for list-latest.

Content type: application/json

Schema

PropertyTypeRequiredDescription
statusstringYesAlways "ER" for error responses
errorCodestringYesApplication-level error code (e.g. E202, E105, E404)
responsestringYesHuman-readable error message
{
  "type": "object",
  "example": {
    "status": "ER",
    "errorCode": "E202",
    "response": "User session is invalid"
  },
  "required": [
    "status",
    "errorCode",
    "response"
  ],
  "properties": {
    "status": {
      "type": "string",
      "description": "Always \"ER\" for error responses",
      "enum": [
        "ER"
      ]
    },
    "errorCode": {
      "type": "string",
      "description": "Application-level error code (e.g. E202, E105, E404)"
    },
    "response": {
      "type": "string",
      "description": "Human-readable error message"
    }
  }
}

Example:

{
  "status": "ER",
  "errorCode": "E112",
  "response": "Cannot use both starting_after and ending_before simultaneously."
}

401 — Missing or invalid X-reflexis-csrf-token-X session token

Content type: application/json

Schema

PropertyTypeRequiredDescription
statusstringYesAlways "ER" for error responses
errorCodestringYesApplication-level error code (e.g. E202, E105, E404)
responsestringYesHuman-readable error message
{
  "type": "object",
  "example": {
    "status": "ER",
    "errorCode": "E202",
    "response": "User session is invalid"
  },
  "required": [
    "status",
    "errorCode",
    "response"
  ],
  "properties": {
    "status": {
      "type": "string",
      "description": "Always \"ER\" for error responses",
      "enum": [
        "ER"
      ]
    },
    "errorCode": {
      "type": "string",
      "description": "Application-level error code (e.g. E202, E105, E404)"
    },
    "response": {
      "type": "string",
      "description": "Human-readable error message"
    }
  }
}

Example:

{
  "status": "ER",
  "errorCode": "E202",
  "response": "User session is invalid"
}

500 — Unexpected server-side error

Content type: application/json

Schema

PropertyTypeRequiredDescription
statusstringYesAlways "ER" for error responses
errorCodestringYesApplication-level error code (e.g. E202, E105, E404)
responsestringYesHuman-readable error message
{
  "type": "object",
  "example": {
    "status": "ER",
    "errorCode": "E202",
    "response": "User session is invalid"
  },
  "required": [
    "status",
    "errorCode",
    "response"
  ],
  "properties": {
    "status": {
      "type": "string",
      "description": "Always \"ER\" for error responses",
      "enum": [
        "ER"
      ]
    },
    "errorCode": {
      "type": "string",
      "description": "Application-level error code (e.g. E202, E105, E404)"
    },
    "response": {
      "type": "string",
      "description": "Human-readable error message"
    }
  }
}

Example:

{
  "status": "ER",
  "errorCode": "E302",
  "response": "Internal server error"
}