SleekplanSleekplan
All ideas

API sleekplan and Integration

Description: When the Sleekplan ↔ Azure DevOps integration (or any third-party integration) is active, the Sleekplan API responses do not include the linked external item identifiers (e.g. ADO work item IDs, feature IDs). Problem: Teams that use both Sleekplan and a third-party tool like Azure DevOps rely on the integration to link feedback posts or roadmap items to their backlog. However, when querying the Sleekplan API, the linked external identifiers are not returned in the payload. This makes it impossible to programmatically trace a Sleekplan item back to its corresponding work item — the only viable workaround is to query the third-party system itself and cross-reference from that side, which is indirect and fragile. Benefit: Exposing third-party integration identifiers (e.g. ADO work item ID, external issue key) in Sleekplan API responses would unlock bidirectional traceability. Teams could build automations, dashboards, or AI-powered workflows that seamlessly bridge Sleekplan and their backlog tool — without having to maintain complex reverse-lookup logic on the external side.

Activity · 2
Sleek Intelligence
Sleek Intelligence
Specify the API surface: which endpoints/resources and API version should expose external IDs (e.g., posts, roadmap items), plus a minimal sample request. Provide a minimal current vs desired response snippet showing exact field names/structure for an item linked to Azure DevOps. Confirm scope: which integrations and identifier fields to support first (e.g., Azure DevOps work item ID and URL; others like Jira issue key?). Thanks!
Caroline MONIN
Caroline MONIN
@sleekintelligence Thanks for the follow-up — happy to clarify. Endpoints concerned All three operations should expose the external integration fields: GET /posts/{id} — to read the linked external item when fetching a post POST /posts — to set the external link at creation time PUT /posts/{id} — to update or add the external link on an existing post Same applies to roadmap items if they have a dedicated endpoint. Current vs desired response (Azure DevOps example) Current GET /posts/{id} response (simplified): { "id": 1234, "title": "Filter changelog subscriptions by category", "status": "planned" } Desired: { "id": 1234, "title": "Filter changelog subscriptions by category", "status": "planned", "integrations": { "azure_devops": { "workitemid": "32768", "workitemurl": "https://dev.azure.com/org/project/_workitems/edit/32768" } } } Scope Our primary need is Azure DevOps (work item ID + URL). That said, exposing a generic integrations object keyed by provider name would make the structure future-proof for other tools (Jira, Linear, etc.) without breaking changes. Context We use the Sleekplan API with an AI layer (Claude) to automate summaries of customer feedback, create roadmap posts, and link them directly to Azure DevOps PBIs and Features. Without the integration fields in the API, this traceability is broken — we can't programmatically confirm or retrieve which backlog item a Sleekplan post is linked to.

More in Improvement