Skip to main content
Create the token while signed in as an administrator of the sipgate account. sipgate has two roles, admin and user, and StackOne refuses a token whose owner is not an admin, because it reads every user of the account.

​
Find your account type

sipgate runs two products, sipgate classic and sipgate neo. Both sign in at the same address and use the same token.

  • To see which one you have, sign in and click your user avatar at the top right to open the profile menu.
  • StackOne reads groups and channels together, because a classic account can have both and neo uses channels.

​
Create the Personal Access Token

A Personal Access Token is a token ID and token pair that replaces a username and password for the sipgate REST API. It reads the one account it was created in.

1

Sign in to sipgate

Sign in to your sipgate account as an administrator.

  • If you are not an admin, ask an admin to open Phone system > Users, open your user, and switch on the toggle for administration rights in Rights management.
  • Open User Settings, then Personal Access Token, or open the Personal Access Token page directly.
  • Check that Settings for shows your own name.
2

Add a token

Click Add token.

  • Token name: StackOne Integration
  • Click Continue.
3

Select the scopes

On Choose OAuth2 scopes, select these four scopes, then click Continue. StackOne only reads.

  • users:read lists the users and their admin or user role.
  • groups:read lists the groups.
  • groups:users:read lists the members of each group. StackOne checks it as soon as the account has a group.
  • channels:read lists the channels, which are the groups on sipgate neo.
  • If one of these scopes is missing, StackOne refuses the connection. Add a new token with all four scopes and paste it into StackOne Hub.
  • Add account:read only if you also use the Get Account action, which reads the company and contact details of the account. The user, role and group reads do not need it.
  • Leave every other scope unselected. Do not select all scopes, which sipgate marks as insecure.
4

Copy the token and the token ID

On Save token, copy the Personal Access Token ID and the Personal Access Token with the copy icon next to each field, and store them securely for use later.

  • The token is only shown once and never again. If you lose it, add a new token.
  • Format: the token ID starts with token-, and the token is 36 letters, digits and hyphens
  • Example: token ID token-FQ1V12
  • Paste the Personal Access Token ID into the Token ID field and the Personal Access Token into the Token field in StackOne Hub.
  • Select I saved the created token and click Close.
  • The token ID stays visible in the Personal Access Token settings.

​
Know how long the token lasts

sipgate does not ask for an expiry date when you add the token.

  • To stop StackOne from reading your account, delete the token in the Personal Access Token settings.
  • After a delete, the connection stops working until you paste a new token ID and token into StackOne Hub.
  • If the person who added the token loses admin rights, StackOne refuses the token when it reads users. Add a new token as an admin and paste it into StackOne Hub.

​
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:
  • Token ID
  • Token
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 on your Accounts page.