Kintone API Authentication

How to authenticate Kintone API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes Kintone tokens for you.

Every Kintone API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Kintone 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

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a Kintone connection in Connections. Kintone uses OAuth. When you create the connection, you are redirected to sign in to Kintone and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
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 Kintone account that should run the action. MindCloud stores and refreshes the Kintone 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 List Apps with an Kintone connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/kintone/actions/list-apps/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 Kintone account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Kintone with OAuth 2.0

You need admin access to the Kintone tenant you plan to connect. The Base URL in the connection form must be the same Kintone tenant that owns the OAuth client configured for this app.

Open Kintone OAuth client settings
In Kintone administration, open OAuth settings and create a new OAuth client or open the existing one used for this app.
Kintone administration → OAuth
Set the redirect endpoint
Add this callback URL to the OAuth client exactly: https://api.mindcloud.co/v1/oauth/kintone/callback.
Allow the right users to authorize
In Configure users, allow the Kintone users who should be able to complete the OAuth consent flow.
OAuth client → Configure users
Grant the required scopes
Grant these scopes on the OAuth client: k:app_settings:read, k:app_record:read, k:app_record:write, k:file:read, and k:file:write.
Kintone Developer Program → Authentication → OAuth Permission Scopes
Enter the tenant Base URL in the connection form
In the connection form, enter the full tenant URL in the format https://your-subdomain.kintone.com, making sure it is the same tenant where the OAuth client was created, then click Connect.

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.