Getacute Acute API

Name: Acute API
Brand: Acute API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer 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.

Install Jentic One Beta

Connect the Acute API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acute 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 Acute 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

GET STARTED

Start building with Acute API

Explore with Jentic

View OpenAPI Document

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 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 Jentic?

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

Credential isolation

Your Acute bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list customer feedback cards' or 'link feedback to a GitHub issue', and Jentic returns the matching Acute 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 Acute 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 with Jentic One, the self-hosted execution layer.

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.

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

Yes. Because you run Jentic One yourself, your own rules decide which Acute operations and credentials the agent may use. You can allow it to only read feedback with GET /zapier/cards and GET /zapier/conversations, while withholding write actions like POST /zapier/cards/add-github-issue or POST /intercom/cards/create-tag until you explicitly add them. Since these operations take their target in the request body rather than the path, you scope the agent at the operation level to exactly the calls it needs.

Getacute Acute API

Connect the Acute API to your agent

Capabilities

Start building with Acute API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs