Build on the subscription platform with OAuth, API v2 and MCP
Technology partners can let their own users connect a subscription platform account in one step, then work with subscription data inside the partner product instead of switching tools or sharing API keys.
The integration path combines OAuth 2.0 for user-approved access, API v2 for reading and managing data, and the MCP server for AI and developer tools.
Why connect with OAuth 2.0
Instead of asking customers to paste API keys, your product sends them to the platform to approve access. That keeps credentials out of your interface and gives customers control over what is shared. Scopes let you request only the areas you need, such as apps, products, entitlements and offerings, rather than broad access by default.
How the flow works
A practical build can follow four steps:
- Register your client by adding your app details and receiving a client ID.
- Redirect users to the platform, where they approve the scopes your app requests.
- Receive access and refresh tokens after approval, with short-lived access and automatic rotation.
- Use those tokens with API v2 to read and manage subscription data on the customer's behalf.
Checklist before launch: confirm each requested scope maps to a visible feature, test the approval and token-refresh flow, and make sure errors explain what the customer needs to re-approve.
What users can do inside your product
Once connected, your users can stay in your product while doing work that would otherwise require a separate dashboard. Examples include syncing subscription events into analytics tools, automating lifecycle actions such as renewals and cancellations, and managing entitlements and offerings without switching tools. For AI assistants, the same connection lets them query subscription data directly.
For AI and developer tools via MCP
For AI assistants and developer-focused tools, the MCP server provides another route to the same data. Assistants such as Claude, Cursor or Copilot can query and manage subscription setup on behalf of users, including products, entitlements, offerings and paywalls through the Paywalls AI Editor, without leaving the interface where the work is happening. Choose OAuth when you need a user-approved product integration, and MCP when the primary user is an assistant acting inside a coding or AI workflow.