Dashboard
The Dashboard shows your workspace's pipeline, from customer feedback to release. Read the count at each step, the most recently changed sessions, tasks, bug reports and feature requests, how many items arrived each day over the last 8 weeks, and what needs your attention. The counts behind the sidebar's badges and status dots are here too. See Dashboard.
Get pipeline-dashboard stats for a workspace
Returns the aggregate counts that drive the workspace dashboard's pipeline: customer feedback and stakeholder feedback (including the interest each side has expressed on feature requests), feature requests by status, work items (tasks and bug reports) by To Do / In Progress / In Review / Done, coding sessions by status group, and releases. Also returns the 7-day arrival counts that every card but Releases shows as "+N past 7 days", the KPI figures and the recent activity feed.
path Parameters
workspaceIdWorkspace UUID
Get pipeline-dashboard stats for a workspace › Responses
Dashboard stats payload
Get the dashboard's tabbed updates section
Returns a headline count, a labelled facet breakdown and the ten most recently updated rows for each of sessions, tasks, bug reports, feature requests and customer feedback. The breakdown uses the same facet vocabulary as the dashboard's pipeline (sessions, tasks and bug reports by status group, feature requests by status, feedback by channel), so without a personal scope each total equals what the pipeline counts for that entity: the task and bug-report totals add up to the Work items card, and the feedback total is the Customer feedback card less the customer interest it also counts. Pass mine=true (or myTeams=true) to scope the sessions, tasks, bug reports and feature requests to rows assigned to the calling user (or their teams); feedback is then null, because a conversation has no assignee. Service-auth callers, which have no user identity to scope by, get empty sessions, tasks and bugReports under a personal scope, and null featureRequests and feedback. The per-entity facet params narrow the returned ROWS only - total and breakdown stay unfiltered, so each facet keeps reporting its real count. An absent param means no filter; an empty one (tasks=) means every facet is unchecked and yields no rows. Unknown facet keys are ignored.
path Parameters
workspaceIdWorkspace UUID
query Parameters
mineScope every list to rows assigned to the calling user
myTeamsScope every list to rows assigned to a team the calling user belongs to (ORs with mine)
sessionsComma-separated session status groups to list (planning, needs_you, building, completed)
tasksComma-separated task status groups to list (todo, in_progress, in_review, done)
featureRequestsComma-separated feature-request statuses to list (new, in_review, promoted, rejected)
bugReportsComma-separated bug-report status groups to list (todo, in_progress, in_review, done)
feedbackComma-separated feedback channels to list (agentic_voice, agentic_email, feedback_stream, interview_manual, support)
Get the dashboard's tabbed updates section › Responses
Dashboard updates payload
Get the dashboard's daily arrival trend series
Returns 56 one-day UTC buckets of counts (oldest first, last bucket = today, partial) behind the dashboard cards' background trend lines. The arrival series (customer feedback conversations, customer and stakeholder interest on feature requests, internal meetings, notes, feature requests, tasks, bug reports and coding sessions) each use exactly the predicate of the matching 7-day count in windows of GET /dashboard/stats, so a card's trend line and its "+N past 7 days" count always agree. releasesShipped is the one series with no count in windows (its 7-day total is kpis.releasesShipped7d): it counts released versions by the day they shipped, and the Releases card shows no weekly count.
path Parameters
workspaceIdWorkspace UUID
Get the dashboard's daily arrival trend series › Responses
Dashboard trends payload
Get the items requiring the calling user's attention
Returns up to ten sessions assigned to the caller that are awaiting user input or plan approval, and up to ten feedback conversations whose feature requests were promoted into features the caller owns. Returns empty lists for service-auth callers, which have no user identity to scope by. The dashboard's third "For you" block, mentions, is served by GET /notifications instead.
path Parameters
workspaceIdWorkspace UUID
Get the items requiring the calling user's attention › Responses
Dashboard attention payload
Get per-domain dashboard summaries for a workspace
Returns a headline count, a labelled status breakdown, and the three most recently updated items for each dashboard metric, grouped into Product (feature requests, features), Engineering (sessions, tasks) and Feedback (agentic interviews, direct feedback).
path Parameters
workspaceIdWorkspace UUID
Get per-domain dashboard summaries for a workspace › Responses
Dashboard summary payload
Get the calling user's open-work counts for a workspace
Returns two families of counts that drive the sidebar's operational badges. Caller-scoped: sessions blocked on them (awaiting plan approval or user input, as assignee OR creator), open tasks assigned to them, and open bug reports assigned to them. Workspace-scoped: whether applications, sessions, features or automations have work in flight, plus features awaiting review and automation runs that failed recently, the open feature requests (New or In Review, the whole workspace), the In Progress releases ready to merge and being prepared, and readers' likes and dislikes on the workspace's public release notes (Productmind's own workspace only). Counts only, no rows. Service-auth callers, which have no user identity to scope by, receive zeros for the caller-scoped family and real values for the workspace-scoped one.
path Parameters
workspaceIdWorkspace UUID
Get the calling user's open-work counts for a workspace › Responses
Open-work counts payload