Skip to main content
The Platform API is the control plane for StackOne. It powers MCP servers and AI Toolset. Use it to execute actions, manage end-user accounts, and build custom integrations.

Execute Actions

Run any of 10,000+ actions via RPC

Manage Accounts

CRUD operations on linked accounts

Onboard End-Users

Generate connect session URLs

​
Execute Actions

The RPC endpoint is the unified way to execute any of StackOne’s 10,000+ actions, the same layer used by MCP and AI Toolset.

Execute Actions Guide

Learn how to execute actions via RPC, discover available actions, and build dynamic agent tooling.

Actions RPC

POST /actions/rpc: Execute any StackOne action.

List Actions

GET /actions: Discover available actions and parameters.

​
Manage Accounts

Linked accounts are your end-users’ connections to their SaaS systems. The Accounts API manages the full lifecycle.

List Accounts

GET /accounts: Get all linked accounts with status, provider, and metadata.

Get Account

GET /accounts/{id}: Get details for a specific account.

Update Account

PATCH /accounts/{id}: Update labels, metadata, or configuration.

Delete Account

DELETE /accounts/{id}: Remove an account and its stored credentials.

​
Onboard End-Users

The Connect Sessions API powers the Integration Hub, the embeddable UI where end-users link accounts.

Create Session

POST /connect_sessions: Generate a connect URL for your app.

Authenticate Session

POST /connect_sessions/authenticate: Authenticate a session programmatically.

​
Typical Flow

​
Discover Connectors

Query metadata about available connectors. Useful for building UIs that show which integrations you support.

List Connectors

GET /connectors: Get all connectors with categories, logos, and capabilities.

Get Connector

GET /connectors/{provider}: Get a connector’s fields and actions.

​
Monitor & Debug

Access detailed logs for every API request. Essential for debugging integrations in production.

List Logs

GET /logs: Query logs with filters for account, status, and time.

Get Log Details

GET /logs/{id}: Get full request/response details for a log entry.

Step-by-Step Execution

GET /logs/{id}/steps: See execution steps (auth, transformation, provider calls).

Platform Logs

GET /logs/platform: Logs for sessions, webhooks, and other platform operations.

​
MCP Endpoint

The MCP (Model Context Protocol) endpoint enables direct integration with Claude, Cursor, n8n, and other MCP-compatible clients. Most users connect via our hosted MCP server, but you can also build custom MCP integrations.

Send Message

POST /mcp

SSE Stream

GET /mcp/sse

End Session

DELETE /mcp/session
For most use cases, use our hosted MCP server at https://api.stackone.com/mcp instead of building a custom integration.

​
Proxy Requests

Bypass the unified layer and make raw requests directly to provider APIs. Useful when you need provider-specific functionality not covered by StackOne actions.

Proxy Request

POST /proxy: Forward requests to the provider API. StackOne handles authentication.
curl -X POST "https://api.stackone.com/proxy" \
  -u "$STACKONE_API_KEY:" \
  -H "x-account-id: customer-bamboohr" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "GET",
    "path": "/api/gateway.php/mycompany/v1/reports/custom"
  }'
Proxy requests bypass StackOne’s unified data model. Use them sparingly for edge cases not covered by standard actions.

​
Platform API vs Unified APIs

I want to…Use
Execute actions from my agent/backendPlatform API → POST /actions/rpc
List all my end-users’ linked accountsPlatform API → GET /accounts
Generate an onboarding linkPlatform API → POST /connect_sessions
List employees from BambooHRUnified API → GET /unified/hris/employees
Create a job posting in GreenhouseUnified API → POST /unified/ats/jobs
Query CRM contactsUnified API → GET /unified/crm/contacts
Rule of thumb: Use the Platform API for managing StackOne itself (accounts, sessions, actions). Use Unified APIs when you want direct REST access to provider data with a standardized schema.

​
Get Started

Authentication

Set up your API key and learn the auth format

Try Actions RPC

Execute your first action

Explore in Playground

Test actions with natural language

View All Endpoints

Browse the full API reference