Feature requests & boards
Collect customer ideas and show their progress from your own interface.
Submit a customer idea
Grant feature_requests:write and POST /feature-requests with customer_id, title and description. An optional board_id selects a workspace board; otherwise TruCom uses the default board.
New requests start with status new, visibility private and source api. They enter the team’s normal review flow. This keeps a customer submission from being published automatically. Your team can review and publish it through the workspace.
Titles are limited to 180 characters and descriptions to 10,000. An Idempotency-Key is required.
curl -X POST "https://trucom.app/api/v1/rest/feature-requests" \
-H "Authorization: Bearer $TRUCOM_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: idea-scheduled-exports-1" \
-d '{"customer_id":"CUSTOMER_ID","title":"Scheduled exports","description":"We need a weekly report for our team."}'Fetch requests and progress
feature_requests:read grants the list, individual request, customer submissions and board endpoints. GET /customers/{customer}/feature-requests lists that customer’s ideas. GET /feature-requests supports customer_id, board_id, status and visibility filters.
Use visibility=public for visible requests on public boards. The response contains the reference, title, description, status, visibility, customer, board, vote count and timestamps. Internal priority, staff assignment and moderation reasons are excluded.
Use GET /feature-request-boards to obtain board IDs and their public/submission preferences. All lists use cursor pagination. Private customer submissions should be returned only to users your application authorizes.