Platform API Reference

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

Endpoints

All endpoints are served from the same base URL:

https://api.stackone.com

Resource	What it does
Accounts	List, retrieve, update, and delete end users’ linked accounts.
Actions	List every available action across your connectors with its metadata, search them by semantic similarity, and execute any of them with an RPC call.
Connect Sessions	Create and authenticate the short-lived tokens that open the account-linking flow.
Connector Profiles	Configure a provider’s authentication and enabled actions, and pin connector versions.
MCP	Serve enabled actions as tools over the Model Context Protocol. Send JSON-RPC messages, stream responses, and manage sessions.
Logs	Inspect per-action, per-step, and platform-wide request logs for debugging and monitoring.

Execute actions

The RPC endpoint runs any action enabled on a linked account. It’s the same layer MCP and the Agent SDK call, so anything your agent can do, your backend can do directly. See RPC/HTTP for the call shape and the discover-then-call flow.

POST /actions/rpc

Execute any action.

GET /actions

Discover available actions and their parameters.

POST /actions/search

Search actions by natural language.

Manage accounts

Linked accounts are your end-users’ connections to their systems. The Accounts API covers the full lifecycle, and origin_owner_id segments them per customer. See Multi-Tenant Accounts.

GET /accounts

List 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

Connect sessions generate the short-lived token that opens the account-linking flow, either the StackOne Hub or an Auth Link. See Connect Session for the request fields and account behavior.

POST /connect_sessions

Generate a connect URL for your end-user.

POST /connect_sessions/authenticate

Authenticate a session programmatically.

Configure connector profiles

A connector profile holds a provider’s authentication and the actions it exposes. Manage them from your own code instead of the dashboard, and pin a connector version so profile behavior stays fixed as connectors evolve.

GET /connector_profiles

List profiles with their authentication type and enabled actions.

GET /connector_profiles/{id}/versions

List the connector versions a profile can pin to.

PUT /connector_profiles/{id}/pinned_version

Set or update the version a profile is pinned to.

Serve actions over MCP

The MCP endpoint exposes a linked account’s enabled actions as tools to any MCP client. Most setups point their client at the hosted server rather than calling these endpoints directly, so start with MCP for the endpoint URL, authentication headers, and tool modes.

POST /mcp

Send a JSON-RPC message.

Monitor and debug

Every request StackOne makes is logged, including the underlying provider calls. See Troubleshooting for the dashboard view and Observability & Log Sync to export logs into Grafana, Datadog, or a warehouse.

GET /logs

Query logs, filtered by account, status, and time.

GET /logs/{id}/steps

See execution steps: authentication, transformation, provider calls.

​Endpoints

​Execute actions