> ## 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 Reference

> Manage accounts, execute actions, and control integrations with the Platform API

The Platform API is the **control plane** for StackOne. It powers [MCP servers](/embed/call-actions/mcp) and the [Agent SDK](/embed/call-actions/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**](/platform/api-reference/accounts/list-accounts)                               | List, retrieve, update, and delete end users' linked accounts.                                                                                      |
| [**Actions**](/platform/api-reference/actions/make-an-rpc-call-to-an-action)                 | 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**](/platform/api-reference/connect-sessions/create-connect-session)      | Create and authenticate the short-lived tokens that open the account-linking flow.                                                                  |
| [**Connector Profiles**](/platform/api-reference/connector-profiles/list-connector-profiles) | Configure a provider's authentication and enabled actions, and pin connector versions.                                                              |
| [**MCP**](/platform/api-reference/mcp/send-mcp-json-rpc-message)                             | Serve enabled actions as tools over the Model Context Protocol. Send JSON-RPC messages, stream responses, and manage sessions.                      |
| [**Logs**](/platform/api-reference/logs/list-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](/embed/call-actions/rpc-http) for the call shape and the discover-then-call flow.

<CardGroup cols={3}>
  <Card title="POST /actions/rpc" icon="play" href="/platform/api-reference/actions/make-an-rpc-call-to-an-action">
    Execute any action.
  </Card>

  <Card title="GET /actions" icon="list" href="/platform/api-reference/actions/list-all-connectors-actions-metadata">
    Discover available actions and their parameters.
  </Card>

  <Card title="POST /actions/search" icon="magnifying-glass" href="/platform/api-reference/actions/search-connector-actions-by-semantic-similarity">
    Search actions by natural language.
  </Card>
</CardGroup>

## 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](/features/multi-tenant-accounts).

<CardGroup cols={2}>
  <Card title="GET /accounts" icon="list-ul" href="/platform/api-reference/accounts/list-accounts">
    List linked accounts with status, provider, and metadata.
  </Card>

  <Card title="GET /accounts/{id}" icon="magnifying-glass" href="/platform/api-reference/accounts/get-account">
    Get details for a specific account.
  </Card>

  <Card title="PATCH /accounts/{id}" icon="pen" href="/platform/api-reference/accounts/update-account">
    Update labels, metadata, or configuration.
  </Card>

  <Card title="DELETE /accounts/{id}" icon="trash" href="/platform/api-reference/accounts/delete-account">
    Remove an account and its stored credentials.
  </Card>
</CardGroup>

## Onboard end-users

Connect sessions generate the short-lived token that opens the account-linking flow, either the [StackOne Hub](/embed/account-linking/stackone-hub) or an [Auth Link](/embed/account-linking/auth-link). See [Connect Session](/embed/connect-session) for the request fields and account behavior.

<CardGroup cols={2}>
  <Card title="POST /connect_sessions" icon="plus" href="/platform/api-reference/connect-sessions/create-connect-session">
    Generate a connect URL for your end-user.
  </Card>

  <Card title="POST /connect_sessions/authenticate" icon="key" href="/platform/api-reference/connect-sessions/authenticate-connect-session">
    Authenticate a session programmatically.
  </Card>
</CardGroup>

## Configure connector profiles

A [connector profile](/gateway/concepts/connector-profiles) 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](/connector-building/connector-versioning) so profile behavior stays fixed as connectors evolve.

<CardGroup cols={3}>
  <Card title="GET /connector_profiles" icon="list-ul" href="/platform/api-reference/connector-profiles/list-connector-profiles">
    List profiles with their authentication type and enabled actions.
  </Card>

  <Card title="GET /connector_profiles/{id}/versions" icon="clock-rotate-left" href="/platform/api-reference/connector-profiles/list-connector-profile-versions">
    List the connector versions a profile can pin to.
  </Card>

  <Card title="PUT /connector_profiles/{id}/pinned_version" icon="thumbtack" href="/platform/api-reference/connector-profiles/upsert-connector-profile-pinned-version">
    Set or update the version a profile is pinned to.
  </Card>
</CardGroup>

## 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](/embed/call-actions/mcp) for the endpoint URL, authentication headers, and tool modes.

<Card title="POST /mcp" icon="plug" href="/platform/api-reference/mcp/send-mcp-json-rpc-message">
  Send a JSON-RPC message.
</Card>

## Monitor and debug

Every request StackOne makes is logged, including the underlying provider calls. See [Troubleshooting](/connect/troubleshooting) for the dashboard view and [Observability & Log Sync](/features/observability/observability-and-log-sync) to export logs into Grafana, Datadog, or a warehouse.

<CardGroup cols={2}>
  <Card title="GET /logs" icon="scroll" href="/platform/api-reference/logs/list-logs">
    Query logs, filtered by account, status, and time.
  </Card>

  <Card title="GET /logs/{id}/steps" icon="stairs" href="/platform/api-reference/logs/list-step-logs">
    See execution steps: authentication, transformation, provider calls.
  </Card>
</CardGroup>