Skip to main content
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.

​
Base URL

All endpoints are served from the same base URL:
v1 endpoints that are no longer listed here can still be found in the v1 OpenAPI spec.

​
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.

POST /actions/search

Search actions by natural language.

POST /actions/rpc/synced

Read the copy Data Sync stores instead of calling the provider.

POST /unified/check_permissions

Check what a user can access before acting on their behalf.

​
Manage accounts

Linked accounts are your end-users’ connections to their systems. The Accounts API covers the full lifecycle. The origin_owner_id you set on the connect session comes back as owner_id, which is how you filter accounts per customer. See Multi-Tenant Accounts.

GET /v2/accounts

List linked accounts with status, connector, and metadata.

GET /v2/accounts/{id}

Get details for a specific account.

PATCH /v2/accounts/{id}

Change an account’s status and status reasons.

DELETE /v2/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.

GET /connect_sessions/{id}

Check a session and its most recent connection attempt.

POST /connect_sessions/authenticate

Exchange a session token for the session it belongs to.

​
Browse connectors

A connector is the definition StackOne uses to talk to a provider. Read the catalog to discover what is available, what actions a connector exposes, and which versions a connector profile can pin to.

GET /v2/connectors

List the connectors available to the project.

GET /v2/connectors/{id}

Get one connector, with expand=actions for its actions and their parameters.

GET /v2/connectors/{id}/versions

List the versions a profile can pin to.

​
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 /v2/connector_profiles

List profiles with their connector key and environment. Add expand=version for the resolved connector version.

POST /v2/connector_profiles

Create a profile with its authentication, actions, and events.

PATCH /v2/connector_profiles/{id}

Update a profile, including the version it is pinned to.

DELETE /v2/connector_profiles/{id}

Remove a profile and everything configured on it.

​
Sync provider data

Data Sync polls a provider on a schedule and stores the records so Deep Query can search them without a provider call. A sync config binds one action to a connector profile, a schedule runs that action for one linked account, and the sync engine produces the runs.

GET /v2/data_sync/sync_configs

List the actions set up to sync, by connector profile.

POST /v2/data_sync/sync_configs

Bind an action to a connector profile.

POST /v2/data_sync/schedules

Sync one action for one linked account on a schedule.

GET /v2/data_sync/runs

Read run history and status. Runs are read-only.

​
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.

​
Inspect webhooks

A webhook is the HTTPS endpoint your project’s events are delivered to. Create and edit them in the dashboard. These endpoints read back what is registered, including the signing secret you verify payload signatures against.

GET /v2/webhooks

List registered webhooks and their status.

GET /v2/webhooks/{id}

Get one webhook with its signing secret.

​
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.

POST /logs

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

POST /logs/steps

See execution steps: authentication, transformation, provider calls.

POST /logs/provider

Read the raw calls StackOne made to the provider.

POST /logs/stats/aggregate

Aggregate volume, errors, and latency for dashboards.