Canny API
★ Only Publicly Available OpenAPI DocumentProductivityForms SurveysapiKey38 EndpointsREST
For Agents
Read and write Canny boards, posts, comments, votes, tags, and users to keep customer feedback portals in sync with internal product and CRM systems. Supports status changes, post merges, and user provisioning.
Use for: Create a Canny feedback post on the Roadmap board for a customer request, I want to change the status of a feature request to 'in progress' and notify voters, List all open posts on the Bugs board sorted by votes, Merge two duplicate posts into one and preserve the vote count
Not supported: Does not handle in-app messaging, ticketing, or roadmap publishing — use for feedback boards, posts, comments, and Canny user sync only.
Jentic publishes the only available OpenAPI specification for Canny API, keeping it validated and agent-ready. The Canny API manages customer feedback boards, posts, votes, comments, tags, categories, and users for product teams running public or private feedback portals. It supports the full feedback lifecycle: capturing requests, organising them by board and category, tracking status changes, and syncing user records with internal systems. Product, success, and engineering teams use it to keep Canny in sync with their own roadmap and CRM tools.
Install Jentic One Beta
Connect the Canny API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Canny API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Canny API.
Create new feedback posts on a specified board with author and details metadata
Change a post's status and optionally notify voters when shipping or rejecting it
Merge duplicate posts into a single canonical post and re-attach votes
Provision or update users in Canny so feedback ties back to authenticated CRM contacts
Tag and categorise posts to keep boards organised by theme or feature area
List and paginate comments across a board for digest or moderation workflows
Use Cases
Patterns agents use Canny API for, with concrete tasks.
★ CRM-to-Canny User Sync
Product teams want feedback authors to match their authenticated CRM users instead of being anonymous. The createOrUpdateUser endpoint keeps Canny user records in lockstep with the source CRM, so when a customer files a post or comment it carries the right identity, company, and email. Sync runs nightly or on CRM webhook events with low write volume.
POST /v1/users/create_or_update with the user's email, name, and external id whenever a new contact is created in the CRM.
Roadmap Status Automation
When engineering closes a Jira issue tied to a Canny post, an automation calls changePostStatus to mark the post 'complete' and notify everyone who voted for it. This closes the loop with customers without a manual triage step. The same workflow handles 'in progress' transitions when work begins.
POST /v1/posts/change_status with the postID, changerID, status='complete', and shouldNotifyVoters=true when the linked engineering ticket closes.
Duplicate Feedback Cleanup
Public boards accumulate near-duplicate posts. A weekly cleanup job lists posts, scores semantic similarity, and calls mergePosts on confirmed duplicates so vote counts roll up to the canonical request. The result is a cleaner board where the most-voted posts surface accurately.
POST /v1/posts/merge with mergePostID, intoPostID, and mergerID to fold one post into another.
AI Agent Feedback Triage
An AI agent reads incoming support tickets, identifies feature requests, and creates Canny posts on the right board. Through Jentic, the agent searches by intent, loads the createPost schema, and submits the post with the support contact as the author so the customer is credited.
Search Jentic for 'create a Canny feedback post', load the createPost schema, and execute POST /v1/posts/create with boardID, authorID, title, and details.
Key Endpoints
38 endpoints — jentic publishes the only available openapi specification for canny api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/posts/create
Create a feedback post
POST
/v1/posts/list
List posts with filters and pagination
POST
/v1/posts/change_status
Change post status with optional voter notification
POST
/v1/posts/merge
Merge duplicate posts
POST
/v1/comments/create
Create a comment on a post
POST
/v1/users/create_or_update
Create or update a Canny user
POST
/v1/boards/list
List all boards
POST
/v1/posts/create
Create a feedback post
POST
/v1/posts/list
List posts with filters and pagination
POST
/v1/posts/change_status
Change post status with optional voter notification
POST
/v1/posts/merge
Merge duplicate posts
POST
/v1/comments/create
Create a comment on a post
POST
/v1/users/create_or_update
Create or update a Canny user
POST
/v1/boards/list
List all boards
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Canny's API key is stored encrypted in the Jentic vault and injected into the apiKey field of each request body at execution time. Agents never see the raw key in their prompt context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'create a Canny post' or 'merge Canny posts') and Jentic returns the matching operation with its input schema, so the agent picks the right one of the 38 endpoints without reading the API reference.
Time to first call
Direct Canny integration: 1-2 days to wire up auth, build request envelopes, and handle errors. Through Jentic: under an hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Canny API through Jentic.
Why is there no official OpenAPI spec for Canny API?
Canny does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Canny API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Canny API use?
Canny uses an API key passed in the JSON request body as the apiKey field on every operation. Through Jentic, the key is stored encrypted in the vault and injected at execution time so it never enters the agent's prompt context.
Can I change a post's status and notify voters with the Canny API?
Yes. Call POST /v1/posts/change_status with postID, changerID, status, and shouldNotifyVoters=true. Canny emails subscribed voters about the status change.
How do I merge duplicate Canny posts through Jentic?
Search Jentic for 'merge Canny posts', load the mergePosts operation, and execute POST /v1/posts/merge with mergePostID, intoPostID, and mergerID. Votes from the merged post roll up into the target post.
What are the rate limits for the Canny API?
Canny does not publish rate limits in the OpenAPI spec. Plan for moderate write volume (a few requests per second) and back off on 429 responses; check the Canny dashboard for your account-specific limits.
Can I sync external users into Canny?
Yes. POST /v1/users/create_or_update with an external id, email, name, and optional companyID upserts a Canny user, so feedback authored on their behalf carries the right identity.
GET STARTED