Skip to main content
Nintex Community Menu Bar
Solved

Nintex API

  • October 1, 2025
  • 7 replies
  • 71 views

Forum|alt.badge.img+3

We have an application that we’re building and need to expose Nintex API data such as list of tasks assigned to the user for a particular workflow. I see that there are 3 authentication methods. We did not want to use service app token as it gives it access admin to the tenant and we didn’t want to use a personal access token either because of the developer role. 

 

The client app token made the most sense because we can limit the scope to just read only to get the list of tasks. However, we noticed it requires a user to sign in through a pop-up window. Is there another method that won’t involve this pop-up window or is there a way to have the user only do it once? 

Best answer by SimonMuntz

Hi ​@jack54321,

If your app requests a new access token with a refresh token, then the consent flow is only required once.

https://developer.nintex.com/docs/nw-api-docs/auth/oauth#request-a-new-access-token-with-a-refresh-token

7 replies

SimonMuntz
Nintex Employee
Forum|alt.badge.img+23
  • Nintex Employee
  • Answer
  • October 2, 2025

Hi ​@jack54321,

If your app requests a new access token with a refresh token, then the consent flow is only required once.

https://developer.nintex.com/docs/nw-api-docs/auth/oauth#request-a-new-access-token-with-a-refresh-token


Forum|alt.badge.img+3
  • Author
  • Rookie
  • October 16, 2025

Thank you Simon. We’re able to get a list of tasks based on a user. However, how are we able to get the instance ID tied to that task? I noticed that the workflowInstanceId property is not available when using Client app tokens. 


SimonMuntz
Nintex Employee
Forum|alt.badge.img+23
  • Nintex Employee
  • October 16, 2025

Hi ​@jack54321,

That’s strange,

I just tested with a client app and the API testing page for tasks, and all the workflow information was returned.
 

 


Forum|alt.badge.img+3
  • Author
  • Rookie
  • October 17, 2025

@SimonMuntz  what scope did you turn on for the client app? 


SimonMuntz
Nintex Employee
Forum|alt.badge.img+23
  • Nintex Employee
  • October 19, 2025

Hi ​@jack54321,

The api document states that you need. nc:task:read.
I just used a client app that I had created a while ago.
It has most options ticked, so I don't think it will be much use to you.

The document also states that the workflow ID is not returned when using a personal access token.

When used with Application Tokens,

  • returns all tasks that match the filters from the tenant
  • includes the workflowInstanceId property

When used with Personal Access Tokens (PAT),

  • returns all tasks that match the filters and meet these conditions:
    • The tasks that are generated from the 100 most recent workflows in which the workflow owner is the token creator.
    • The tasks which are assigned to the token creator.
  • does not include the workflowInstanceId property

Forum|alt.badge.img+3
  • Author
  • Rookie
  • November 4, 2025

Hi ​@SimonMuntz,

 

Thank you so much for the information. We did some more testing. While using the client app token, the workflowinstanceID is only available in the JSON if the user credentials being passed through is an admin. If you could try your test again but this time lower your account level to just participant, you will see that the workflowinstanceID does not appear in the JSON. 


SimonMuntz
Nintex Employee
Forum|alt.badge.img+23
  • Nintex Employee
  • November 4, 2025

Hi ​@jack54321,

What you are seeing is expected behavior.
When creating a client app, the page advises using an account with administration rights.