Skip to main content
NiCE CXone Mpower Expert
Expert Success Center

Get a Server API Token

Applies to:
All versions
Role required:
Admin
Generate Server API Tokens to integrate Expert with your server or backend application.

Navigate to the API Token Management dashboard

  1. Navigate to Site tools > Dashboard Integrations API Token Management.
  2. If you cannot find an API token Management link under Integrationscontact your Customer Success Manager to enable the feature.

Generate a Server API token

Server tokens can be restricted by using the API directly on POST:site/developer-tokens and PUT:site/developer-tokens/{id}. Example POST request:
<developer-token type="{type}" >
    <key>{key}</key>
    <name>{name}</name>
</developer-token>
  1. In the Add an API token section, select the Server radio button.
  2. Enter a Name for the token that is easy to track and manage.
    Image showing api token dialog entry fields
  3. Click Generate API token.
  4. Record the API token information and copy your API token secret to a safe location.
    Image of the api token created window including secret

Do not close the "API Token created" window without copying and recording your secret. Your API Token key will not function without your secret, and your secret will no longer be accessible once the window is closed. Both the key and the secret are necessary for integrating with the Expert API, so do not lose them.

 

 

Long-term JSON Web Tokens (OAuth bearer tokens)

When creating Server API tokens, you can generate a one-time long-lived JWT scoped to a specific user.

Only Server tokens can be assigned to a user. Browser and OAuth tokens cannot be assigned to a specific user.

For apps that need it, a long-term JWT (also called an OAuth bearer token) can be created at the same time as the server token key and secret. This allows authentication to be set by user, tenant, or group, which provides flexibility without compromising security.

Upon creation of a new server token, an OAuth bearer token is returned immediately. This is a one-time issuance and the token has a 10-year expiration.

You can see your server tokens in the Dashboard, but because the JWTs are not visible we advise you to name the server token to indicate that an OAuth bearer token is associated with it. If there is an issue with an OAuth bearer token, this indicates the server token should be removed and a new server token / long-term JWT should be obtained.

Create an OAuth bearer token in the Dashboard

To create an OAuth bearer token:

  1. Select Server as the token type.
  2. Enter token name.
  3. Check Generate long‑term JWT (OAuth bearer token).
  4. (optional) Search for and select a user in Restricted to user.
  5. Click the Generate API token button.
  6. Copy the generated JWT.

UI - Dashboard - Integration - OAuth bearer JWT token.png

Create an OAuth bearer token in Postman

You can run similar code in Postman to create a server token at /@api/deki/site/developer-tokens.

<developer-token type='server'>
    <name>foo</name>
    <restricted-by-user-id>1</restricted-by-user-id>
</developer-token>

Example of created server token with JWT:

{"@id":"9","@type":"server","@date":"Wed, 19 Feb 2025 17:20:49 GMT","@href":"https://spencersso.mindtouch.es/@api/deki/site/developer-tokens/9","authorization":"Bearer eyJhbGciOiJIUzUxMiIsImtpZCI6IjkiLCJ0eXAiOiJKV1QifQ.eyJzdWIiOiJhMmFkNDU0YjYwMTI1MTI5NjQ0YjdkYjk0MTZiNWYzY2I3NzE3ZDUwMDAwYzM4OTVlZGI2OGRhZDU1ZTAwYzU3IiwiYXVkIjoiYXV0aC1zZXJ2aWNlLVNlcnZlciIsImV4cCI6IjIwNTU1MTg0NDkiLCJpc3MiOiJodHRwczovL3NwZW5jZXJzc28ubWluZHRvdWNoLmVzLyIsImlhdCI6IjE3Mzk5ODU2NDkiLCJuYmYiOiIxNzM5OTg1NjQ4In0.R7koEcEyFnzTdFQ9APHlaLp8FtVrKP9hQOqou3qiVsi0ClHRRWljtzLOPCrR48QcLQ9GivUh6wJ0sd5Cr7rj9Q","key":"a2ad454b60125129644b7db9416b5f3cb7717d50000c3895edb68dad55e00c57","name":"foo jwt","restricted-by-user-id":"1","secret":"18c19f9b2663d2aefe4170b8346aa3303365382bb09c5f235f5c72310ea8ff6d"}

Here is an example script on GitHub to try out. 

 

  • Was this article helpful?