airfocus API
Agent-ready OpenAPI document · curated by JenticProductivityTask Managementbearer20 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create roadmap items, capture insights, manage statuses and fields, and pull workspace data from the airfocus product management platform.
Use for: Create a new roadmap item in a workspace, I want to add an insight from customer feedback, List all items in a specific workspace, Update the status of a feature in airfocus
Not supported: Does not handle engineering issue tracking, time logging, or document collaboration - use for roadmap items, prioritization, and customer feedback insights only.
Jentic publishes the only available OpenAPI specification for airfocus API, keeping it validated and agent-ready. airfocus is a modular product management platform combining roadmaps, prioritization, and customer feedback. The API exposes 20 endpoints across workspaces, items (features, ideas, and tasks), custom fields, statuses, voting portals, insights, and team members. Authentication is via bearer token issued from the airfocus account settings.
Install Jentic One Beta
Connect the airfocus API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the airfocus 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fairfocus.com%2Fairfocus" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fairfocus.com%2Fairfocus" | 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 airfocus API.
Create, update, and delete items (features, ideas, tasks) within a workspace
Define custom fields on a workspace to capture business-specific item attributes
List statuses and move items through prioritization stages
Capture insights from customer feedback and link them to roadmap items
List and inspect voting portals where customers prioritize requests
Pull team member rosters for assignment workflows
Use Cases
Patterns agents use airfocus API for, with concrete tasks.
★ Customer Feedback to Roadmap
Capture customer feedback as an insight, then promote it to a roadmap item once it has enough signal. POST /api/workspaces/{workspace_id}/insights records the raw feedback, and creating an item via POST /api/workspaces/{workspace_id}/items places it on the prioritized backlog with linkage back to the source insight.
Create an insight in workspace ws_42 with the customer quote 'Need bulk export', then create a feature item titled 'Bulk CSV export' linked to that insight
External Tool Sync
Sync items between airfocus and other tools (Jira, GitHub, Linear) by listing workspace items, mapping fields, and updating status as work moves. GET /api/workspaces/{workspace_id}/items returns the current backlog, /fields exposes custom field definitions, and PUT on items keeps statuses aligned with engineering progress.
List items in workspace ws_42 with status 'In Progress', map them to Jira issue keys via the custom field 'jira_key', and update each airfocus item with the latest Jira status
Voting Portal Insight Aggregation
Aggregate customer votes from a public airfocus portal into product analytics. GET /api/workspaces/{workspace_id}/portals lists active portals, then list portal-linked insights and items to surface the most-requested ideas in an internal dashboard.
List portals for workspace ws_42, then fetch the top 10 insights by vote count and post them as a weekly digest to a Slack channel
AI Agent Roadmap Assistant
An agent embedded in a product team chat can capture spoken or written feedback, create insights, and propose roadmap items via Jentic. The bearer token stays in the vault and only scoped airfocus operations are exposed to the agent.
Search Jentic for 'create an airfocus item', load the POST /api/workspaces/{workspace_id}/items schema, and create a feature in workspace ws_42 titled 'OAuth login' with description from the conversation context
Key Endpoints
20 endpoints — jentic publishes the only available openapi specification for airfocus api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/workspaces
List workspaces
GET
/api/workspaces/{workspace_id}/items
List items in a workspace
POST
/api/workspaces/{workspace_id}/items
Create an item
PUT
/api/workspaces/{workspace_id}/items/{item_id}
Update an item
GET
/api/workspaces/{workspace_id}/insights
List insights
POST
/api/workspaces/{workspace_id}/insights
Create an insight
GET
/api/members
List team members
GET
/api/workspaces
List workspaces
GET
/api/workspaces/{workspace_id}/items
List items in a workspace
POST
/api/workspaces/{workspace_id}/items
Create an item
PUT
/api/workspaces/{workspace_id}/items/{item_id}
Update an item
GET
/api/workspaces/{workspace_id}/insights
List insights
POST
/api/workspaces/{workspace_id}/insights
Create an insight
GET
/api/members
List team members
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring airfocus by hand means handling its bearer token, threading workspace and item ids through nested paths, and writing your own retry logic. Through Jentic you install once, import airfocus from the API Directory, store the token once, and your agent calls it.
Permission scoping
airfocus puts the workspace and item ids in the URL path (/workspaces/{workspace_id}/items/{item_id}), so a rule can pin your agent to one workspace. You choose the operations it may call, so updating an item is only included if you add it.
Credential isolation
Your airfocus bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an airfocus item', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using airfocus API through Jentic.
Why is there no official OpenAPI spec for airfocus API?
airfocus does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call airfocus 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 airfocus API use?
airfocus authenticates via HTTP bearer tokens generated from the account settings page. Jentic stores the token encrypted in the vault and applies the Authorization header on every call, so the agent never handles the raw token.
Can I create a roadmap item with the airfocus API?
Yes. POST /api/workspaces/{workspace_id}/items creates an item with title, description, status, and any custom field values defined on the workspace. Items can later be updated with PUT or removed with DELETE.
What are the rate limits for the airfocus API?
The spec does not declare formal rate limits. Treat the API as an interactive product-management surface; for bulk imports, paginate item creation rather than firing concurrent requests against a single workspace.
How do I capture customer feedback as an insight with the airfocus API through Jentic?
Run pip install jentic, search Jentic for 'create airfocus insight', load the schema for POST /api/workspaces/{workspace_id}/insights, then execute with the workspace ID and the feedback content. Jentic applies the bearer token automatically.
Can I list voting portals via the airfocus API?
Yes. GET /api/workspaces/{workspace_id}/portals returns the active voting portals for that workspace, suitable for showing aggregated request counts in an internal dashboard.
Can I limit what my agent is allowed to do with the airfocus API?
Yes. Jentic One runs self-hosted, so your own rules decide which airfocus operations and credentials the agent may use. Because airfocus puts the workspace and item IDs in the URL path (/workspaces/{workspace_id}/items/{item_id}), you can pin the agent to a single workspace, and you pick the exact operations it can call, so an action like updating an item via PUT is only reachable if you include it. Read-only setups can expose just GET /api/workspaces/{workspace_id}/items while withholding create and delete.
GET STARTED