Productmind API

Productmind API

The Productmind REST API is the API the Productmind app itself runs on: everything you can do in the app, you can do here.

  • Workspace-scoped. Almost every endpoint lives under /workspaces/{workspaceId}/....
  • OAuth 2.1 with PKCE. Requests carry an access token in Authorization: Bearer <token>. There are no API keys or personal tokens - see API access and authentication for how to get a token.
  • The same permissions as the app. A token acts as the person who authorized it, with that person's role in the organization.
Tags
Workspaces
A workspace holds one product's work: its feedback, features, tasks, sessions and settings. List the workspaces you can use in your organization, create one, change its name or description, or delete it with all its data. You can also read and change a workspace's product configuration: when a status change on a feature or feature request asks for or requires a decision, and what evidence a feature request needs before it can be promoted to a feature. See Organizations and workspaces.
Dashboard
The Dashboard shows your workspace's pipeline, from customer feedback to release. Read the count at each step, the most recently changed sessions, tasks, bug reports and feature requests, how many items arrived each day over the last 8 weeks, and what needs your attention. The counts behind the sidebar's badges and status dots are here too. See Dashboard.
Chats
Chats are your conversations with the PM agent. List your chats, read one with its messages, start a new one, and stop a reply that is still being written. When the assistant has handed a chat over to a coding session, release the chat so your next message goes to the assistant again. See Finding your way around.
Sessions
Sessions are coding sessions: an AI coding agent plans and builds work from your tasks or bug reports in your repositories, then opens pull requests. Start a session and choose its repositories, have the agent draft a plan and build it, answer its questions or approve its plan, and review, merge or close its pull requests. Read a session's conversation, start or stop its live preview, or let your own coding agent pick up a session, read its context and ask you questions. See Code.
Tasks
Tasks are your engineering backlog. Create, update and delete tasks, keep a log of progress on each, and have AI describe a task from its screenshots. A coding agent working on tasks in a session also reports here: when it starts, its plan, its progress, how it verified the work and the pull request it opened. See Tasks.
Bug reports
Bug reports track defects in your product. Create, triage and delete reports, record who reported each one, merge duplicates, and link a report to the applications, features and tasks it affects. Have AI describe a report from its screenshots, see the customer conversations that surfaced it, and convert it into a task, feature or feature request. See Bug reports.
Notes
Notes are the quick write-ups on your workspace's notes wall: a customer quote, an idea, a reminder. Create, edit, pin and delete notes, have AI summarize one, and convert a note into a feature request, feature, task or bug report. See Notes.
Internal meetings
Internal meetings are your team's own meetings, such as debriefs, roadmap discussions and retros. Log a meeting with its agenda and notes, have an AI notetaker join the call or dismiss it, and get an AI summary with decisions and action points. Link a meeting to the features, feature requests and tasks it was about. See Internal meetings.
Knowledge base
The knowledge base holds your workspace's reference documents. Create, edit, organize and delete documents, add a website or pages from a connected tool, have AI regenerate a system document, and link a document to the applications and features it describes. Search it or ask it a question, review changes the AI proposes, and browse or restore a document's earlier versions. See Knowledge base.
Features
Features are your product catalog: a tree of what your product does, where each feature has a specification. Create, update, move and search features, link them to the applications that implement them and to the features they depend on, and read their business rules and document history. Have Productmind draft a specification, refresh it from the linked code for your review or suggest tasks, and find the features that own the files a change touched. See Features.
Feature map
The feature map is your feature catalog drawn as a tree, with the applications each feature spans. Read the map, run feature discovery across your repositories to build or rebuild the catalog, follow the scan's progress or stop it, and deep scan selected features across every service they span. See Features.
Feature requests
Feature requests collect what customers and your team ask for, with the evidence of who wants each one. Create, update and search requests, record interests and link the customer interactions behind them, and merge duplicates. When you decide to build one, promote it into a feature or a task. See Feature requests.
Decisions
A decision records what your team decided about a feature request or a feature, and why: the outcome (approved, rejected, deferred or conditional), the rationale and the interests it cites. List the decisions on a feature request or a feature, newest first, or record a new one. Decisions are never edited: a new decision can supersede an earlier one. See Decision records.
Lineage
Lineage traces how your product work connects, from the customer conversations and feature requests behind a feature to the tasks, sessions and releases that delivered it. Read the lineage of every feature at once, or the full graph around one customer conversation, feature request, bug report, feature, task, session or release. See Lineage.
Releases
A release ships your code: for each application, Productmind compares the development branch with the production branch, lists the commits and opens a pull request. Create a release and prepare it, follow its checks, draft the release notes, curate the work it contains, then ship it to merge every pull request and tag the result. When your deployment pipeline records a production deployment, the release becomes Released and the features it shipped move to Stable. See Releases.
Marketing
Marketing turns a release into what you tell your customers. Draft a release's customer-facing release notes from what shipped and the customer feedback behind it, edit them, then approve and publish them once the release is Released. Every publish keeps a numbered copy of exactly what customers were told. Unpublish takes the live notes down and keeps every version; Republish puts the newest version back. See Marketing.
Applications
An application is one of your code repositories, with what Productmind needs to run it: commands, services, ports and environment variables. Create applications, import them from your repositories or start one from a template, update their configuration, and read their linked features, documentation and repository files. Run the documentation, feature discovery and agentic readiness scans on one application or across all of them, and stop a scan while it runs. Estimate what scanning your repositories will cost before you start, and resume a scan that paused when your pay-as-you-go balance ran out. See Applications.
Environments
An environment is somewhere your applications deploy to: Development and Production in every workspace, and any your workspace adds. List, create, rename and delete environments, and read or set the branch each application deploys to an environment from. An application's Development and Production branches are its own branch fields, else the workspace's Git workflow defaults. See Applications.
Cloud accounts
A cloud account is an AWS account a workspace deploys into: one Productmind creates and manages for you, or one you own and connect. List the workspace's cloud accounts and read one: its kind, tier and status, and its AWS account id once known. Reading them needs permission to read cloud accounts, which Owners and Admins have.
Architecture map
The architecture map shows which of your services depend on which, including across repositories, and the databases, queues, caches and third-party APIs they use. Read the map, map your service architecture from your applications or from repositories that aren't applications yet, and follow the scan's progress or stop it. Productmind creates an application for each scanned repository that isn't one yet. See Applications.
Sandboxes
A sandbox is the container a coding session runs in: which applications it clones and starts, in what order, and its image, size and environment variables. Create, update and delete sandboxes, choose the workspace's default, and set the attached applications and their startup order. See Sandboxes.
Git
Git covers the repositories your workspace reaches through a connected Git provider, such as GitHub. List a repository's branches, with your workspace's development branch marked as the default. After you reinstall a Git provider or change Productmind's access, repair repository links so your applications, sessions, releases and channel notifications use the current connection, and see which repositories it still can't reach. See Integrations.
Agent context
The agent context is standing background about your product that the PM agent, the interview agent and the generators always read. Skills are named procedures an agent loads when a job calls for one. List, create, update and delete the context and skills, generate the context from your product overview (this replaces the one you have), and fetch a skill by its name. See Agents.
Agent definitions
An agent definition describes an agent that an automation can run: its instructions, model and tools. List Productmind's standard agents and your own, create, update and delete definitions (deleting a customized standard agent resets it), list the tools an agent may use, and queue a run of one. Creating, changing and running definitions needs automations to be available to your organization. See Definitions.
Model classes
A model class is a tier of AI model: Quick, Standard, Top or Ultra. Read, for each class and provider, the ordered list of models your workspace's coding sessions and AI agents use: Productmind's default, or your workspace's own list once it is customized. Customizing a list needs a plan that includes Agent customization. See Model classes.
Templates
Document templates set the shape of what Productmind's agents write. Read the feature description and feature request description templates your workspace uses: your team's version if someone has edited it, otherwise Productmind's default. See Templates.
Automations
An automation is a rule that runs one of your agent definitions when something happens in your workspace, on a schedule, or only by hand, where automations are available to your organization. List and create automations, which start disabled, then enable, update or delete them, check whether one would fire on a given item, and run one now to test it. List, filter and delete runs, and read the model and tool steps of each run. See Automations.
Customer research
A research is a study with objectives and questions, and every agentic interview belongs to one. List and create researches, change their title, description, objectives and questions, read one with its interview counts, sentiment and summary, and list the feature requests its interviews brought up, with how many interviews mention each. Deleting a research also deletes its interviews, which you manage as customer interactions. See Agentic interviews.
Customer interactions
A customer interaction is one conversation with a customer: a customer meeting, a support case, an agentic interview or a feedback widget conversation. List, create, update and delete interactions, change their status, read and add messages, and summarize one, which also files what the customer asked for as feature requests and the problems they hit as bug reports. You can also have Productmind read an interaction's screenshots into a draft analysis, then append it to the notes or dismiss it. See Customer meetings.
Support import
Support import files tickets from your helpdesk as support cases, or as customer meetings if you choose. Preview a batch of tickets to see which contact and account each would link to, then import them; importing a ticket again updates the conversation it created instead of adding another. You can also turn automated ingestion on or off for each helpdesk, set its ingestion filters, and list recent ingestion events. See Freshdesk and Zendesk.
Contacts
Contacts are the people your feedback comes from, and each belongs to one account. List and search contacts across accounts, create and update them, move one to another account, delete one or many at a time, and match a list of email addresses to existing contacts. Creating a contact with an email address you already have returns the existing contact instead of adding a duplicate. See Contacts.
Accounts
Accounts are the companies your feedback comes from, and every contact belongs to one. List, create, update and delete accounts, read one with its contacts, and add, change or delete the contacts under an account. Deleting an account also deletes its contacts. See Contacts.
Users
Users covers your own account. Get your profile, list the browsers, devices and apps signed in to your account, and sign out one of them or every one except the one you're using. The Productmind agent on your machine uses it too: list your online agents, get the address an agent connects to, report and read back the models it can run, and pick up the work and live previews sent to it. See Profile and notifications.
Teams
Teams are groups of your organization's members that work can be assigned to as a whole, and a member's team role adds permissions to their own role. List your organization's teams and who is in each, create a team, and add a member to a team, change their team role or remove them. You can also list the people who can be assigned work, and the roles a team member can have. See Teams.
Settings
Workspace settings are the rules that apply to everyone in a workspace, such as the Git branches coding sessions work from, grouped by area. Read one setting or every changed setting in an area, change a setting, or reset it to its default. You can also preview the default MCP workflow skill with your workspace's details filled in, and read and change your own settings, such as whether your notifications go to Slack instead of email. See Settings.
Billing
Your organization's plan can cap how many features and knowledge base sources each workspace holds. Get a workspace's current count, cap and percentage used for each one. A limit your plan leaves unlimited is left out of the response. See Plans and limits.
Audit log
The audit log records who created, changed and deleted what in your workspace, and every change to your organization's members, roles, teams and sign-in settings. List events, open one to see each field's value before and after, or read one record's whole history. You can also export the events that match your filters as CSV or JSON, and read or change how long events are kept. See Audit log.
Productmind support
A Productmind support request asks the Productmind team for help: a question about using Productmind or its API, a bug report, a feature request, or a Productmind Architect's review of a coding session's pull requests. Open a request, follow and reply in its conversation, attach screenshots to it and its replies, cancel it, approve or reject a review's quotes, and choose which features, tasks and bug reports a review shares. Your organization can also see, revoke and turn off the architects' access to its sessions. These operations work only from a signed-in browser session: a request made with an API key or an agent's token is refused. See Support center.
Notifications
Notifications are the messages Productmind sends you, for example when someone mentions you or assigns you work. List yours, count the unread ones, and mark one or all of them as read. You can also post a workspace's activity to Slack channels: check the Slack connection, choose a channel and the events it receives, then pause, edit or remove it. See Profile and notifications.
Comments
Comments are the discussions on your records, such as features, feature requests, tasks, bug reports, sessions and knowledge base documents. List a record's comments, add a comment or a reply, attach it to a passage of text, and edit, delete or resolve it. A comment that mentions a teammate notifies them.
Attachments
Attachments are the files on your records, such as screenshots and documents on a task, a bug report, a session or a note. List a record's attachments with a download link for each, upload a file by requesting an upload link and sending the file to it, edit an attachment's description, and delete it.
Tags
Tags label your records, such as features, tasks, bug reports, releases and knowledge base documents, so you can group and filter them. List, add and remove the tags on a record, or list the tag names in use across your workspace. Ask Productmind to suggest tags from a record's content, then accept or reject the suggestions one by one, per record, or by name across the workspace.
Search
Search finds records across a workspace in one ranked list: tasks, features, bug reports, feature requests, sessions, applications and sandboxes. Search by an ID such as TASK-12 to find that record, by a bare number to match it across every kind of record, or by any other text to match titles. Results include only the kinds of records you can read.
Public
Public operations need no access token. Get the plans you can subscribe to, with their monthly and annual prices in euros, the limits and features Productmind's pricing page compares them on, the price of AI credits (per 1M credits and per typical task) and the unit price of everything billed pay as you go. See Plans and limits.