Acute API

Name: Acute API API
Brand: Acute API
Availability: InStock

★ Only Publicly Available SpecCRMCustomer Successbearer4 EndpointsREST

For Agents

Read user feedback cards and conversations from Acute, and link feedback to GitHub issues or Intercom tags so product and support teams can triage signal automatically.

Quickstart

Get started with Acute API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list customer feedback cards from Acute"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Acute API API.

Retrieve all feedback cards captured in Acute and forward them to a roadmap or data warehouse

List feedback conversations to triage open user discussions in bulk

Generate an Intercom tag from an Acute card so support agents can route the conversation

Link a GitHub issue to an Acute feedback card so engineering can track the request

GET STARTED

Start building with Acute API API

Explore with Jentic

View OpenAPI Spec

Use for: List all feedback cards in Acute, Retrieve feedback conversations from the last 30 days, Link a GitHub issue to a piece of feedback, Tag a feedback card in Intercom

Not supported: Does not handle public feedback voting, in-app widget delivery, or roadmap publishing — use for reading feedback cards and linking them to GitHub or Intercom only.

Jentic publishes the only available OpenAPI specification for Acute API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Acute API, keeping it validated and agent-ready. Acute is a customer feedback management tool that helps SaaS teams capture, organise, and triage user-submitted feedback alongside Intercom conversations and GitHub issues. The API exposes feedback cards and conversations for retrieval and provides Intercom and GitHub integration helpers, so external automations can read feedback and link it to engineering tickets. It is most often used to push Acute feedback into a data warehouse or a roadmap tool.

Use Cases

Patterns agents use Acute API API for, with concrete tasks.

★ Feedback-to-GitHub Linking

Product teams want every piece of upvoted user feedback to map to an engineering ticket so progress is traceable. The Acute API lets a workflow create a GitHub issue from a feedback card, then link the issue back to the card so the loop is closed when the issue ships. This eliminates manual copy-paste between Acute and GitHub.

For a feedback card with the highest vote count this week, call `POST /zapier/cards/add-github-issue` with the issue URL and confirm the link is recorded.

Feedback Triage in Intercom

Support teams using Intercom want to tag conversations that originated from Acute feedback so they can be routed to the right team. The API generates an Intercom tag for an Acute card, allowing automation to apply consistent labels across both tools and reducing duplicate triage work.

Call `POST /intercom/cards/create-tag` for each new feedback card and apply the returned tag to the linked Intercom conversation.

Feedback Data Warehouse Export

Analytics teams need feedback in their warehouse alongside product usage data so they can correlate complaints with churn or feature adoption. The Acute API exposes cards and conversations in a structured form, so a scheduled job can pull all records and load them into a destination like BigQuery or Snowflake without scraping the UI.

Call `GET /zapier/cards` and `GET /zapier/conversations`, normalise the records, and load them into a warehouse table partitioned by created date.

Agent-Driven Feedback Reporting

An AI agent embedded in a product manager's workspace can answer 'what are users asking for this week?' by pulling Acute cards through Jentic and summarising them. The agent uses Jentic to discover the cards endpoint, calls it without handling the bearer token directly, and produces a ranked list of themes.

Pull all feedback cards via Jentic's Acute integration, group by theme, and return a top-10 list with vote counts.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for acute api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/zapier/cards

Retrieve all feedback cards

GET

/zapier/conversations

Retrieve all feedback conversations

POST

/zapier/cards/add-github-issue

Link a GitHub issue to a feedback card

POST

/intercom/cards/create-tag

Generate an Intercom tag for a feedback card

GET

/zapier/cards

Retrieve all feedback cards

GET

/zapier/conversations

Retrieve all feedback conversations

POST

/zapier/cards/add-github-issue

Link a GitHub issue to a feedback card

POST

/intercom/cards/create-tag

Generate an Intercom tag for a feedback card

Why though Jentic?

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

Credential isolation

Acute bearer tokens are stored encrypted in the Jentic vault. Agents call Acute operations via Jentic and the platform injects the `Authorization: Bearer …` header at runtime — the raw token never enters the agent's prompt.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list customer feedback cards' or 'link feedback to a GitHub issue') and Jentic returns the matching Acute operation with its input schema.

Time to first call

Direct Acute integration: a few hours per integration target (GitHub, Intercom, warehouse). Through Jentic: under 30 minutes for the first call and reusable across agents.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Canny

Customer feedback and roadmap platform with public boards and richer voting workflows.

Choose Canny when you need a public-facing feedback board with explicit voting and a roadmap view rather than internal triage.

Alternative

Pendo Feedback

Feedback module within the Pendo product analytics platform.

Choose Pendo Feedback when feedback must sit alongside product analytics, NPS, and in-app guides in one platform.

Complementary

Freshdesk

Helpdesk and ticketing platform commonly paired with feedback tools to convert support tickets into product input.

Use Freshdesk alongside Acute when support tickets are the upstream source of feedback and you want to triage there before promoting items into Acute.

FAQs

Specific to using Acute API API through Jentic.

Why is there no official OpenAPI spec for Acute API?

Acute does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Acute 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 Acute API use?

The Acute API uses HTTP Bearer authentication. Through Jentic, the bearer token is stored encrypted and injected at execution time — agents do not see the raw token.

Can I link a GitHub issue to a feedback card with the Acute API?

Yes. Call `POST /zapier/cards/add-github-issue` with the card identifier and GitHub issue URL to attach the issue to the card.

Can I list all feedback conversations through the Acute API?

Yes. Call `GET /zapier/conversations` to retrieve all feedback conversations. The endpoint returns conversation records suitable for export or triage.

How do I tag an Intercom conversation from an Acute card via Jentic?

Search Jentic for `tag an Intercom conversation from Acute feedback`, load the schema for `POST /intercom/cards/create-tag`, and execute with the card identifier. Jentic handles the bearer token automatically.

Does the Acute API support submitting new feedback or upvotes?

No. The current API surface is read-oriented for cards and conversations and integration-helper for GitHub and Intercom. New feedback submission and voting happen through the Acute UI or product widget.