Aha! API

Name: Aha! API
Brand: Aha! API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject Managementbearer47 EndpointsREST

For Agents

Manage products, features, releases, ideas, goals, and initiatives in an Aha! workspace - full CRUD across the product hierarchy plus comments, tags, and workflow state.

Install Jentic One Beta

Connect the Aha! API to your agent

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

Create and update features, releases, and requirements within a product

Promote ideas into features and link them to releases or initiatives

Track goals and initiatives across products with progress and status

Manage epics that group features across releases

GET STARTED

Start building with Aha! API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Aha! API for, with concrete tasks.

★ Idea Triage and Promotion

Product managers triage incoming ideas and convert the strongest into features against a target release. The API exposes the full create/update lifecycle for ideas at /api/v1/products/{product_id}/ideas and lets the same agent promote an idea into a feature with one further call. Tagging and commenting endpoints round out the triage workflow.

GET /api/v1/products/{product_id}/ideas filtered by tag 'enterprise', then PUT each idea status to 'reviewed'

Roadmap Build-Out

Product teams script the creation of features, requirements, and dependencies for an upcoming release rather than clicking through the UI. POST /api/v1/products/{product_id}/features creates a feature, while requirements, to-dos, and tags can be attached in follow-up calls. The endpoints accept the company subdomain via the {company}.aha.io host so multi-tenant integrations work cleanly.

POST /api/v1/products/{product_id}/features for each backlog item, then PUT release_id on each to schedule

Goal and Initiative Tracking

Engineering and PMO teams keep an external dashboard in sync with Aha! by polling the goals and initiatives endpoints. /api/v1/products/{product_id}/goals returns the goals associated with a product and /api/v1/products/{product_id}/initiatives returns the strategic initiatives, both of which can be updated through the matching PUT endpoints to reflect progress.

GET /api/v1/products/{product_id}/initiatives and PUT progress=75 for initiative INIT-3

AI Agent Product Operations via Jentic

An agent built on Jentic can maintain Aha! state in response to natural language - 'add a feature for SSO support to our July release' - by chaining product lookup, feature creation, release assignment, and tag application. Jentic injects the bearer token from the vault, and the documented 300/min limit is applied per account so an agent can run many concurrent operations safely.

Use Jentic to search 'create a feature in Aha', load the schema, and create a feature with name and release_id

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/api/v1/products

List all products

POST

/api/v1/products/{product_id}/features

Create a feature

PUT

/api/v1/features/{feature_id}

Update a feature

POST

/api/v1/products/{product_id}/releases

Create a release

POST

/api/v1/products/{product_id}/ideas

Create an idea

POST

/api/v1/products/{product_id}/goals

Create a goal

POST

/api/v1/products/{product_id}/initiatives

Create an initiative

GET

/api/v1/releases/{release_id}/features

List features in a release

GET

/api/v1/products

List all products

POST

/api/v1/products/{product_id}/features

Create a feature

PUT

/api/v1/features/{feature_id}

Update a feature

POST

/api/v1/products/{product_id}/releases

Create a release

POST

/api/v1/products/{product_id}/ideas

Create an idea

Why Jentic?

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

Credential isolation

Your Aha! bearer token is stored once, encrypted, by your own Jentic One instance and attached 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 feature in Aha', and Jentic returns the matching operation with its path parameters and body fields, including the company subdomain, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Aha! API through Jentic.

Why is there no official OpenAPI spec for Aha! API?

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

The API uses a bearer token in the Authorization header. Tokens can be generated as personal API keys or via OAuth2 in the Aha! account. Jentic stores the token in its vault and injects it on each request, so the secret never enters agent context.

What are the rate limits for the Aha! API?

The Aha! API is limited to 300 requests per minute and 20 requests per second per account. Plan batched workloads with backoff; 429 responses include retry guidance and should be honoured before retrying the call.

How do I create a feature in a release through the Aha! API?

POST /api/v1/products/{product_id}/features with the feature name, status, and an initial assigned_to_user. To attach the new feature to a release, follow up with PUT /api/v1/features/{feature_id} setting the release_id field.

How do I promote an idea to a feature through Jentic?

Search Jentic for 'promote an Aha idea to a feature'. Load the matching POST schema, supply the idea_id and target release_id, and execute. Jentic adds the bearer token before the call and returns the new feature record.

Can I list all goals and initiatives across products?

Yes, but the listing endpoints are scoped per product - call GET /api/v1/products/{product_id}/goals and /api/v1/products/{product_id}/initiatives for each product, then aggregate. Use the fields query parameter to keep responses small if you only need name and status.

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

Yes. Because you run Jentic One yourself, your own rules decide which Aha! operations and credentials the agent may use, and anything you leave out stays unreachable. You can grant only the calls you intend, such as reading products with GET /api/v1/products or creating features with POST /api/v1/products/{product_id}/features, while withholding write operations you do not want. Since Aha! carries the product id and feature id in the URL path (/products/{product_id}/..., /features/{feature_id}), a rule can also pin the agent to a single product so it never touches others.

Aha! API

Connect the Aha! API to your agent

Capabilities

Start building with Aha! API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs