> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Platform API Overview
> Manage accounts, execute actions, and control integrations with the Platform API
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.
Run any of 10,000+ actions via RPC
CRUD operations on linked accounts
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.
Learn how to execute actions via RPC, discover available actions, and build dynamic agent tooling.
**`POST /actions/rpc`**: Execute any StackOne action.
**`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.
**`GET /accounts`**: Get all linked accounts with status, provider, and metadata.
**`GET /accounts/{id}`**: Get details for a specific account.
**`PATCH /accounts/{id}`**: Update labels, metadata, or configuration.
**`DELETE /accounts/{id}`**: Remove an account and its stored credentials.
***
## Onboard End-Users
The Connect Sessions API powers the [Integration Hub](/guides/embedding-stackone-hub), the embeddable UI where end-users link accounts.
**`POST /connect_sessions`**: Generate a connect URL for your app.
**`POST /connect_sessions/authenticate`**: Authenticate a session programmatically.
### Typical Flow
```mermaid theme={null}
sequenceDiagram
participant App as Your App
participant API as Platform API
participant Hub as Integration Hub
participant User as End-User
App->>API: POST /connect_sessions
API-->>App: { connect_url, token }
App->>User: Redirect to connect_url
User->>Hub: Selects provider & authenticates
Hub->>API: Creates linked account
API-->>App: Webhook: account.created
```
***
## Discover Connectors
Query metadata about available connectors. Useful for building UIs that show which integrations you support.
**`GET /connectors`**: Get all connectors with categories, logos, and capabilities.
**`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.
**`GET /logs`**: Query logs with filters for account, status, and time.
**`GET /logs/{id}`**: Get full request/response details for a log entry.
**`GET /logs/{id}/steps`**: See execution steps (auth, transformation, provider calls).
**`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.
} href="/platform/api-reference/mcp/send-mcp-json-rpc-message">
**`POST /mcp`**
} href="/platform/api-reference/mcp/open-mcp-sse-stream">
**`GET /mcp/sse`**
} href="/platform/api-reference/mcp/delete-mcp-session">
**`DELETE /mcp/session`**
For most use cases, use our [hosted MCP server](/mcp/quickstart) 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.
**`POST /proxy`**: Forward requests to the provider API. StackOne handles authentication.
```bash theme={null}
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/backend | **Platform API** → `POST /actions/rpc` |
| List all my end-users' linked accounts | **Platform API** → `GET /accounts` |
| Generate an onboarding link | **Platform API** → `POST /connect_sessions` |
| List employees from BambooHR | **Unified API** → `GET /unified/hris/employees` |
| Create a job posting in Greenhouse | **Unified API** → `POST /unified/ats/jobs` |
| Query CRM contacts | **Unified 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
Set up your API key and learn the auth format
Execute your first action
Test actions with natural language
Browse the full API reference