Build on Triangle
Register OAuth apps, add Connect with Triangle to your product, and call user-authorized health data. Use remote MCP today; a public HTTP API specification is coming soon.
What you can build
Triangle exposes an OAuth 2.1 authorization server so your app can act with the user's consent. Start with an app in the portal, then choose how you call Triangle.
OAuth apps
Create public or confidential clients, set redirect URI bases, and manage consent metadata in the developer portal.
Connect with Triangle
Add a button that sends users through authorize + PKCE, then store access and refresh tokens for your backend.
Remote MCP
Call Triangle tools with the same Bearer access token used by ChatGPT, Claude, and other MCP hosts.
HTTP API
Public REST-style API documentation is coming soon. Prefer MCP for production integrations until the API spec is published here.
Guides
Step-by-step setup for the portal and Connect with Triangle. For ChatGPT, Claude, Perplexity, and other hosts, see Integrations.
Build a Connect with Triangle button for your own product. Register an OAuth app, send users through Triangle consent with PKCE, exchange the code for access and refresh tokens, then call Triangle MCP today — with full HTTP API documentation coming soon.
View setup guide →
Use the Triangle developer portal to create and manage OAuth applications for MCP clients, local tools, and your own Connect with Triangle integrations — with PKCE, prefix-based redirect URIs, and consent metadata you control.
View setup guide →
When to use which registration
Third-party products always register in the developer portal. Many AI platforms use Dynamic Client Registration instead — follow the matching guide under Integrations.
| When to use | OAuth registration |
|---|---|
| Your own app (Connect with Triangle) | Developer portal + Connect with Triangle guide |
| Your MCP app or local tool | Self-serve in the developer portal |
| ChatGPT, Claude, Grok, and others | Platform-specific setup on Integrations |
Public HTTP API docs coming soon
We are preparing documented HTTP endpoints for common patient and care operations behind the same OAuth consent model. Until that guide ships, use remote MCP with a Bearer access token from Connect with Triangle or an MCP client. This section will link to the published API specification when it is ready.
Ready to register an app?
Sign in to Triangle, open the developer portal, and create a Client ID. Then follow Connect with Triangle or plug the credentials into an MCP client.