Canny API

Name: Canny API
Brand: Canny API
Availability: InStock

★ 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.

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with Canny API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Canny API key is stored once, encrypted, by your own Jentic One instance and injected into the request body's apiKey field at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Canny post' or 'merge duplicate posts', and Jentic returns the matching Canny operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Canny API?

Yes. Because Jentic One is self-hosted, you decide which Canny operations your agent may call, and your own rules are enforced when it runs. Since Canny passes its targets in the request body rather than in the URL path, you can grant read-only operations like listing posts and boards while withholding writes such as creating posts, merging posts, or updating users. Those operations are only available to the agent if you add them, and your stored API key is injected at execution time so it never enters the agent's context.

Canny API

Connect the Canny API to your agent

Capabilities

Start building with Canny API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs