Sign inGet started
Docs
Get started

SeaTable API Authentication

How to authenticate SeaTable API requests: one Bearer API key plus a connectionId. MindCloud stores your API key securely — set it once, never resend it.

Every SeaTable API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your SeaTable account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a SeaTable connection in Connections. SeaTable uses an API key. You generate the key in your SeaTable account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
  4. Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected SeaTable account that should run the action. MindCloud stores and refreshes the SeaTable credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Get Base Token With API Token with an SeaTable connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/seaTable/actions/get-base-token-with-api-token/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which SeaTable account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect SeaTable with an API token

You need access to the SeaTable base you want this connection to control. SeaTable base operations require a short-lived Base Token and the Base UUID in addition to your long-lived API token.

  1. Create or copy a SeaTable API token for your base

    In SeaTable Cloud, create an API token for the specific base you want to use. Give it the permission level this wrapper needs.

  2. Generate a Base Token from that API token

    Use SeaTable's documented Get Base-Token with API-Token endpoint to exchange your API token for a temporary Base Token.

  3. Copy the values into this MindCloud connection

    Paste your long-lived API token into the API key field. Paste the returned access_token into Base Token and the returned dtable_uuid into Base UUID.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.