Feature requests
Feature requests collect what customers and your team ask for, with the evidence of who wants each one. Create, update and search requests, record interests and link the customer interactions behind them, and merge duplicates. When you decide to build one, promote it into a feature or a task. See Feature requests.
List feature requests in a workspace
Returns feature requests — user-submitted ideas and demands that may become product features. Includes interest counts, tags, status, and the Applications/Features each request is linked to. Filterable by status, priority, source, application, feature, and tags. Returns: id, title, description, priority, status, interestCount, tags, relationships, linkedEntity (the Feature or Task a promoted request became, or the request a merged one was folded into), createdAt.
path Parameters
workspaceIdWorkspace UUID
query Parameters
pagePage number (1-indexed, default 1)
limitItems per page (default 50)
sortByField to sort by
sortOrderSort direction (default desc)
searchFull-text search across searchable fields
priorityFilter by priority (single value or array)
statusFilter by status (single value or array)
sourceFilter by source (single value or array)
applicationFilter by linked application id
featureFilter by linked feature id
tagsFilter by tag names (single value or comma-separated array)
accountFilter by requesting account ids (single value or comma-separated array), matched through feature-request interests
assigneeIdFilter by assignee: a user or team UUID, or a comma-separated list of them (requests assigned to ANY listed user/team match). my-teams stands for every team the caller belongs to.
activityAfter^(?:(?:\d\d[2468][04…Only the items with activity after this ISO 8601 instant (for example 2026-10-26T09:00:00Z): for a session its last activity, or its last update when it has none; for every other list its last update (updatedAt). Send it with limit=1 and read pagination.total to count what changed since then. The response names the instant it applied in filters.activityAfter. A value that is not an ISO 8601 instant is refused with 400.
includeSessionsOpt in to each request's sessions: the coding sessions of the task it was promoted to (id, displayId, name, category, status), scans and code chats left out; empty for a request not promoted to a task. Returned only to a caller who may read coding sessions. Defaults to false.
List feature requests in a workspace › Responses
List of feature requests
Create a feature request
Submit a new feature request to capture user demand. Requests start in 'new' status and can be moved to in_review, then promoted, merged, or rejected. When a specific customer or teammate asked for it, pass them in interests (a customer is their contact id from list-contacts): that records who wants it, counts toward its interest count and files it under the customer's account, while a name written into the description counts nothing. Every entry is checked before anything is written, so one that cannot be recorded (an unknown contact) rejects the whole call and creates nothing. Recording interests needs permission to update feature requests as well as to create them. To add interest to a request that already exists, use add-feature-request-interest.
path Parameters
workspaceIdWorkspace UUID
Create a feature request › Request Body
titledescriptionMarkdown, at most 200,000 characters.
sourceWhat KIND of request this is, e.g. customer_feedback for something customers ask for. It does not record WHO asked: pass the people in interests.
priorityestimatedEffortsortOrderOptional. Who asked for this request, recorded as interest in the same call: each entry is exactly the body add-feature-request-interest takes. A customer is { requestingContactId } (find the contact with list-contacts, or add someone not on file yet with create-contact; their account comes with them). This is what counts the demand on the request and files it under the customer's account: a name written into the description counts nothing. Every entry is checked before anything is written, so an unknown contact rejects the whole call and creates nothing. Needs permission to update feature requests. At most 20.
Create a feature request › Responses
Created feature request
Update feature request status
Transition a feature request between statuses: new, in_review, promoted, merged, rejected.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Update feature request status › Request Body
statusUpdate feature request status › Responses
Feature request status updated
Merge feature requests into a target
Merge one or more source feature requests into a target feature request. Copies interests from sources to target, creates MERGED_WITH relationships, sets source statuses to 'merged', and uses an LLM to synthesize an updated description for the target.
path Parameters
workspaceIdWorkspace UUID
Merge feature requests into a target › Request Body
sourceIdstargetIdMerge feature requests into a target › Responses
Merge result with updated target and description status
Find a feature request by topic (semantic search)
Semantic search over feature-request titles using the knowledge base (LanceDB). Handles paraphrases that keyword search would miss. Every hit is matchType: "semantic" with an absolute similarity score (comparable across queries). Returns a lean shape (id + title + score + matchType) — follow up with get-feature-request for full details. Hits below the server-side noise floor are filtered, so an empty list means no real match. Prefer list-feature-requests for structured filtering (status / source / priority).
path Parameters
workspaceIdWorkspace UUID
query Parameters
qSearch query
limitMax results (default 10, cap 50)
Find a feature request by topic (semantic search) › Responses
Ranked feature-request matches with relevance scores
Bulk promote feature requests to a feature
Promote multiple feature requests to the same feature. Sets their status to 'promoted' and creates PROMOTED_TO entity relationships. Every request must be in 'new' or 'in_review' status: if any is not, the call returns 409 naming each one, and nothing is promoted.
path Parameters
workspaceIdWorkspace UUID
Bulk promote feature requests to a feature › Request Body
idsfeatureIdBulk promote feature requests to a feature › Responses
Promoted feature requests
Promote a feature request to a feature
Promote a single feature request to a feature. Sets the request status to 'promoted' and creates a PROMOTED_TO entity relationship. Only a request in 'new' or 'in_review' status can be promoted: a 'merged', 'rejected' or already 'promoted' request returns 409. To promote a rejected request, set it back to 'in_review' first; to promote the demand of a merged request, promote the request it was merged into.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Promote a feature request to a feature › Responses
Promoted feature request
Bulk promote feature requests to tasks
Promote multiple feature requests into one task each, optionally all under the same parent feature. Every task inherits its own request's title, description and priority. Sets each request's status to 'promoted' and creates a PROMOTED_TO entity relationship to its task. Every request must be in 'new' or 'in_review' status: if any is not, the call returns 409 naming each one, and no task is created.
path Parameters
workspaceIdWorkspace UUID
Bulk promote feature requests to tasks › Request Body
idsFeature request UUIDs
featureIdOptional parent Feature UUID applied to every created task.
Bulk promote feature requests to tasks › Responses
The created tasks paired with their promoted feature requests
Promote a feature request to a task
Promote a single feature request into a Task - use this when the request is a piece of work inside a feature that already exists, rather than a capability of its own (for that, use promote-feature-request). The task inherits the request's title, description and priority unless overridden, and may be parented to a feature. Sets the request's status to 'promoted' and creates a PROMOTED_TO entity relationship. A request can be promoted only once, to a feature OR a task, and only from 'new' or 'in_review' status: a 'merged', 'rejected' or already 'promoted' request returns 409, and no task is created. To promote a rejected request, set it back to 'in_review' first; to promote the demand of a merged request, promote the request it was merged into.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Promote a feature request to a task › Request Body
titleTask title. Defaults to the feature request's title.
descriptionTask description, markdown. Defaults to the feature request's description.
featureIdOptional parent Feature UUID. Omit to create a workspace-level task with no feature.
Promote a feature request to a task › Responses
The created task and the promoted feature request
Get interest source summary for a feature request
Returns an aggregated summary of all interest sources for a feature request — showing where demand is coming from (manual entries, customer interactions, etc.).
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Get interest source summary for a feature request › Responses
Source summary
List interests for a feature request
Who wants a feature request: every interest recorded on it, newest first. Each carries its source (a customer, a teammate, or other input such as a market signal), the customer's contact and account, the teammate's role and name, the sentiment, the position and what they said. Interests that were removed are not listed. Check this before recording an interest, so the same person's ask is not recorded twice.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
List interests for a feature request › Responses
List of interests
Add manual interest to a feature request
Record who wants a feature request, such as a customer mentioning it in a call or email. Three kinds: a customer (requestingContactId, their contact id from list-contacts; the contact's account is attached with them), a teammate (stakeholderRole, plus stakeholderUserId or stakeholderName), or other input (source set to competitive_intelligence, market_signal, strategic_directive or support_pattern, with a description; no contact). Each call adds one interest: check list-feature-request-interests first, because calling twice records the same ask twice. When the ask came from a customer meeting or conversation already recorded in the workspace, use link-interaction-interest instead.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Add manual interest to a feature request › Request Body
sourceWho this interest speaks for. Defaults to customer_feedback, which needs requestingContactId. internal_stakeholders is a teammate (set stakeholderRole). competitive_intelligence, market_signal, strategic_directive and support_pattern are other input: no contact, and you are recorded as who added it. Ignored when stakeholderRole is set.
descriptionWhat they want or said, in their words where you have them, e.g. "Needs SSO before the Q3 rollout."
sentimentHow the person feels about the request, when known.
requestingContactIdThe UUID of the customer contact who asked (find it with list-contacts; each row's id is this value). Someone who is not on file yet is added with create-contact, whose id is this value too. Required for a customer interest. The contact's account is attached automatically, so there is no account field. A contact outside this workspace's organization is rejected.
positionTheir stance: supporting, neutral, opposing, or conditional (then say the condition in conditionalNotes). Mostly for teammates and other input.
conditionalNotesThe condition behind a conditional position, e.g. "Only if it ships with SSO."
stakeholderRoleSet this to record a TEAMMATE's interest instead of a customer's: the interest becomes internal_stakeholders, whatever source says. Name the teammate with stakeholderUserId or stakeholderName; with neither, it is recorded as yours.
stakeholderUserIdThe workspace member the teammate interest is from (a user UUID). Takes precedence over stakeholderName.
stakeholderNameThe teammate's name as free text, for someone who is not a workspace member.
weightOptional relative weight of this interest. Leave it unset unless the user gives one.
Add manual interest to a feature request › Responses
Interest added
Link a customer interaction to a feature request
Record a customer meeting or conversation the workspace already holds as interest in a feature request. The interaction's contact, account, sentiment and summary are copied onto the interest, and it links back to the conversation. Find the interaction with list-customer-interactions. Linking the same interaction twice records it twice.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Link a customer interaction to a feature request › Request Body
interactionIdThe UUID of the customer meeting or conversation to record as interest (find it with list-customer-interactions). Its contact, account, sentiment and summary are copied onto the interest.
Link a customer interaction to a feature request › Responses
Interest created from interaction
List feature requests linked to a customer interaction
Returns feature requests that have interests sourced from the specified customer interaction.
path Parameters
workspaceIdWorkspace UUID
interactionIdCustomer interaction UUID
List feature requests linked to a customer interaction › Responses
List of linked feature requests
Update an interest on a feature request
Edit a stakeholder input, competitive intelligence note, or customer interest. Only the original contributor — or a caller holding the member:update capability — may edit stakeholder-attributed rows.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
interestIdInterest UUID to update
Update an interest on a feature request › Request Body
descriptionsentimentpositionconditionalNotesweightUpdate an interest on a feature request › Responses
Updated interest
List logs on a feature request
Returns log entries for a feature request, newest first.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
List logs on a feature request › Responses
List of logs
Add a log entry to a feature request
Post a new log entry on a feature request.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Add a log entry to a feature request › Responses
Log added
Update a log entry on a feature request
Edit your own log entry on a feature request.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
logIdLog UUID
Update a log entry on a feature request › Responses
Log updated
List merged source requests
Returns feature requests that were merged into this target request via MERGED_WITH relationships.
path Parameters
workspaceIdWorkspace UUID
idTarget feature request UUID
List merged source requests › Responses
List of merged source requests
List a feature request's relationships
Returns the Applications and Features linked to a feature request. Only hand-made related_to links — the promoted_to / merged_with rows the promote and merge flows write are reported by the request's linkedEntity instead.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
List a feature request's relationships › Responses
List of relationships
Link a feature request to an application or feature
Create a relationship between a feature request and an Application (where the demand applies) or a Feature (the affected area).
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Link a feature request to an application or feature › Request Body
targetTypetargetIdrelationshipTypeLink a feature request to an application or feature › Responses
Created relationship
Remove a feature request relationship
Delete a link between a feature request and an application or feature.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
relationshipIdRelationship UUID
Remove a feature request relationship › Responses
Relationship removed
Get a feature request by ID
Retrieve a single feature request: its title, description, status, priority and source, its tags, the applications and features it is linked to, what it became (the feature or task it was promoted to, or the request it was merged into), the note or bug report it was created from, and its assignees. It does not include who wants it: read that with list-feature-request-interests.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Get a feature request by ID › Responses
Feature request details
Update a feature request
Modify feature request title, description, or priority.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Update a feature request › Request Body
titledescriptionMarkdown, at most 200,000 characters. Replaces the whole description: send it only with the complete new text. To change part of the description, send descriptionEdits instead.
Change PART of the description without resending it: a list of exact find-and-replace edits the server applies to the stored description, in order, all or none. Each find must be copied exactly (same characters, spacing and line breaks) from the description as it stands, and must occur exactly once there at that point: include enough surrounding text to make it unique. replace is the new text (an empty string deletes the passage). Everything outside the passages is kept as it is. Prefer this over description for any change to a long description, and always when your read of the description was cut. Cannot be sent together with description.
prioritystatussortOrderSet the single USER assignee (legacy-shaped field): replaces the request's user assignees with this one, null unassigns every user. Team assignees are left untouched — use assignees to change them.
REPLACES the item's whole assignee set: every user and team listed becomes an assignee, everything not listed is unassigned. Pass [] to unassign everyone. When both this and the legacy single-user field (assigneeId / ownerId) are supplied, this wins. Find a team's id with list-teams and a person's with list-assignable-users.
Update a feature request › Responses
Updated feature request
Describe a feature request from its screenshots
Trigger the vision agent to read the feature request's attached screenshots and draft an updated description, incorporating the existing description and the interest recorded against the request. Idempotent while a run is in flight. On a blank description the draft is applied automatically; otherwise it is held for review.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
Describe a feature request from its screenshots › Request Body
sourceHow the run was triggered (auto on image upload / manual button)
Describe a feature request from its screenshots › Responses
The queued (or in-flight) description proposal
List a feature request's description proposals
Returns AI-drafted description proposals for a feature request. Pass activeOnly=true for the single in-flight / awaiting-review proposal.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
query Parameters
activeOnlyList a feature request's description proposals › Responses
Description proposals
Apply a feature request description proposal
Write the reviewer-composed markdown (accepted diff blocks) to the feature request's description and settle the proposal.
path Parameters
workspaceIdWorkspace UUID
idFeature request UUID
proposalIdProposal UUID
Apply a feature request description proposal › Request Body
descriptionApply a feature request description proposal › Responses
The applied proposal