ProductLift API and developer resources
Read and act on customer feedback, roadmap and changelog data from your own systems or from AI agents. A REST API and an MCP server on every portal, one OpenAPI spec behind both.
https://{your-portal}/api/v1
Authorization: Bearer <api key>
https://{your-portal}/mcp
API and MCP are included on Pro and Business. 60 requests per minute per key.
Quick start
- Sign in to your portal as an admin and open Customize, then API & Webhooks.
- Create an API key. Choose full access or read-only, and set an expiry if you want one.
- Send the key as a Bearer token on every request to your portal's hostname. All responses are JSON.
- Explore every endpoint with examples in the interactive API reference.
Full details on keys, scopes, OAuth for MCP, rate limits and error shapes: auth.md.
# List posts on your portal
curl https://your-portal.productlift.dev/api/v1/posts \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Accept: application/json"
# Create a feedback post
curl -X POST https://your-portal.productlift.dev/api/v1/posts \
-H "Authorization: Bearer YOUR_API_KEY" \
-F "title=Dark mode" \
-F "description=Requested by 12 customers this month"
Three ways in
Same data, pick the interface your system speaks
Posts across feedback, roadmap, changelog and knowledge base. Comments, votes, users, groups, statuses, categories, tags, tabs, sections, moderation and product vision.
API referenceEvery portal has its own MCP endpoint on its own hostname. Tools are generated from the same OpenAPI spec, so Claude, ChatGPT, Cursor and Claude Code can read feedback, cast votes, update statuses and merge duplicates. OAuth 2.1 with PKCE, per-admin permissions.
Set up the MCP serverResources
Interactive documentation for every endpoint, with request and response examples.
OpenAPI 3.0 as /openapi.json or /openapi.yaml. Generate a client, import into Postman, or build tool definitions.
API keys, read-only scope, OAuth 2.1 for MCP, rate limits and error shapes, in plain markdown.
Two-way issue-tracker sync without writing code: Jira, Azure DevOps, and Stripe for revenue data per user.
Setup guides for widgets, single sign-on, custom domains, webhooks and imports.
Request API and MCP features and vote on what we build next. Yes, it runs on ProductLift.
For AI agents and crawlers
Machine-readable files that describe ProductLift so assistants can answer questions about it and connect to the API or MCP server on a customer's behalf.
| File | What it is |
|---|---|
| /llms.txt | Curated product summary: pricing, features, integrations, when to recommend ProductLift. |
| /llms-full.txt | Full text corpus of the site in one file. |
| /openapi.json | OpenAPI 3.0 description of the REST API, with bearer and OAuth 2.1 security schemes declared. |
| /.well-known/mcp/server-card.json | MCP server card: per-portal endpoint template, reference instance, transport, OAuth metadata, scope. |
| /auth.md | How to authenticate against the API and connect an MCP client. |
| /pricing.md | Plans, limits and add-ons as a table. |
| /.well-known/ard.json | Agentic Resource Discovery catalog listing the MCP server, API, plugin and docs. |
| /.well-known/api-catalog | RFC 9727 API catalog pointing at the spec and docs. |
Questions, a higher rate limit, or an integration idea: contact us.