Skip to main content
Keep your token secret — anyone with it has API access at the permission you grant. A token is shown only once at creation; if lost, create a new one. Use a token dedicated to this integration.

​
Find your Project ID

Every call is scoped to your project. After you sign in you land on the organization dashboard, which lists all of your projects.

1

Copy your Project ID

Sign in at sanity.io/manage. From the organization dashboard (which lists all your projects), click your project to open it.

  • From the organization dashboard at sanity.io/manage, click your project to open it
  • No projects yet? Click + New project in the project selector dropdown at the top of the page to create one first
  • Copy the Project ID shown on the project’s overview / settings page (e.g. abc12xyz)
  • Alternatively, read it straight from the browser address bar while inside the project: sanity.io/organizations/<org>/project/<projectId>/... — the value after /project/ is your Project ID

​
Create a project API token

Tokens are created per project under the API tab.

1

Open the project's API > Tokens

Tokens are created per project.

  • In sanity.io/manage, select your project from the organization dashboard to open it
  • Go to the API tab, then Tokens
  • Click Add API token
2

Name the token, set expiration and pick a permission

The permission is single-select. To use ALL actions in this connector, choose Developer.

  • Enter a Name (e.g. StackOne Integration) and set Expiration (No expiration for a long-lived integration)
  • Developer ← recommended — grants access to every action in this connector (read+write all datasets, manage datasets/tags/projects, and access-control reads + invites)
  • Editor — content + assets only (cannot create datasets) — least-privilege for content authoring
  • Viewer — read-only actions only
  • Click Save
3

Copy the token

The token is shown only once.

  • Copy the token (starts with sk) from the dialog
  • Important: this is your only chance to copy it — store it securely

​
Which permission to select (by resource / operation)

Developer is sufficient for every action in this connector. Pick a lower
permission only if you want to restrict the connection to fewer actions:

  • Developer — ALL actions: documents (read + mutate), assets, datasets (incl. create/delete), tags, projects, invites, and access-control reads (users/roles/permissions/requests)
  • Editor — content + assets read/write, but cannot create datasets or manage tags/projects
  • Viewer — read-only: query/get documents, export, list datasets/projects/tags/roles/users, etc.
  • Note: a few actions are marked preview and additionally require a Business/Enterprise plan (tag writes, dataset copy) or a Media Library (link asset) — but no token permission higher than Developer.

​
Linking the Account from the Hub

1

Navigate to the Hub

Use one of the three Linking Account Methods to access the Hub.
2

Fill out the fields

Fill out the following fields using details from your provider:
  • API Token
  • Project ID
3

Connect

  • Click Connect
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.