Task Execution

Version: 1.0.0 OpenAPI: 3.0.3

OpenAPI APIGEE mirror of next-gen-swagger/task-execution/next-gen-task-execution-api.yaml — paths and components resolve from that file via $ref (same operations as Pulse deployment, different base URLs).

APIGEE-only: send api_key (API key) in addition to X-reflexis-csrf-token-X (session token). Clients often send Origin and Referer matching the gateway host.

Dashboard counts: GET /task/v1/dashboard/feed-entity-count returns one or more projection families (status, priority, due) of feed counts over the user's line-of-sight in a single response. feed_entity_projections (CSV, default status,priority) selects which families are computed; period (YYYYMMDD,YYYYMMDD — inclusive range anchored in the user's session timezone) scopes status.completed (via COMPLETION_DATE) and the priority distribution (via END_DATE_TIME). The due section ignores period and returns by_due[] with five fixed calendar buckets (today, this_week, last_week, this_month, last_month). Tiles include new_tasks_today, in_progress, review, overdue, and completed, plus by_status / by_priority distributions (and optional approaching_overdue when approach_deadline is set). returned counts using the priority labels in app-config. The dashboard lives under its own URL space (/task/v1/dashboard/*) — see the /task/v1/dashboard/{retrieve-type} entry below.

Feed list task progress: After GET /task/v1/feeds/list, call GET /task/v1/feeds/task-progress with feed_keys (CSV, max 50 unique parent keys) and the same view/RU params. Returns progress_details[] with total_task_count, completed_task_count, and progress_percent (Mongo aggregation; TM-70644 semantics). List responses do not embed progress fields by default.

Saved Filters (TM-76046 / TM-77095): GET|POST|PUT|DELETE /task/v1/feed-filters and PUT /task/v1/feed-filters/default are published on this proxy (revision 12+). FEED omits category; Calendar uses category=CALENDAR + sub_category / sub_filter_data_category. Proxy bundle: apidocs/nextgen/task-execution/. Smoke: smoke-feed-filters.sh.

Task pinning (TM-74802): Pin CRUD is published on the MyWork APIGEE proxy (/mywork/v1/user-preferences, /mywork/v1/user-preferences/TASK_PINS/{feed_key}). Pin-open UX uses GET /task/v1/feeds/{feed_key}/visibility on this proxy. List responses may stamp boolean pinned when TASK_PIN_COUNT > 0.

Companion APIGEE specs: mywork/next-gen-mywork-apigee-api.yaml (app config, broadcasts, user notes, recent tabs, user preferences / TASK_PINS), walk-execution/next-gen-walk-execution-apigee-api.yaml (walk execution).

Servers

URLDescription
https://dev-api.zebra.comDev APIGEE
https://stage-api.zebra.comStage APIGEE
https://test-api.zebra.comTest APIGEE
https://api.zebra.comProd APIGEE

Security schemes

NameTypeDescription
ApiKeyHeaderapiKeyAPIGEE API key header validated by VerifyAPIKey policy.
AuthTokenHeaderapiKeySession authentication token validated server-side against the user session store.

Operations

Use the sidebar to browse individual operations generated from this specification.