"Get a Specific User" API

Joaquin Margarido

04. tammik. 2023, 10.19

Hello

From the intranet we want to use the "Get a Specific User" API to find out the risk of a specific user, but the input parameter is the 'user_id', internal data from KB4 and not known a priori, unless a call is made to the "Get a List of All Users" API, which returns a very large number of information with many pages and time dilates.
Our request is that the "Get a Specific User" API may require as an input parameter, another piece of information known as the email or the employee number. This is important to our client.

regards

0

• 

  Christian Nostrom 04. tammik. 2023, 17.32

  Hello Joaquin,

  Thanks for posting to the Community Board regarding the "Get a Specific User" via API.  The call to retrieve the risk score will return all users information at this time.  If you would like specific users, it does have to be based on a user's ID. You do have the ability to obtain all of the user ID's from the https://developer.knowbe4.com/rest/reporting#tag/Users/paths/~1v1~1users/get call.  From there you can gather all the users ID’s to pinpoint specific users.

  I can understand how this would be beneficial based on an email or employee number and I have gone through and sent a feature request directly to our development team for further consideration. While I can’t provide a timeline or guarantee that this feature request will be implemented, our team always appreciates this information.

   In the meantime, please be sure to keep an eye out for our latest changes here: https://support.knowbe4.com/hc/en-us/articles/115009454228-Security-Awareness-Training-Platform-KMSAT-Change-Log.

  Thanks,

  0

  Kommenttitoiminnot Pysyvä linkki
• 

  Joaquin Margarido 09. tammik. 2023, 16.58

  I have made the mistake of including this issue in this section and I think it would be better in the 'Security Awareness Training Platform: Feature Requests' section. Please move it if possible. Thank you

  0

  Kommenttitoiminnot Pysyvä linkki
• 

  Jaclyn Turko 10. tammik. 2023, 14.28

  Hello Joaquin,

  Thank you for your follow-up! Christian has submitted your feature request with the appropriate labels so there is no need to move this post. We appreciate your concern and we are thankful for your suggestion!

  Best,

  0

  Kommenttitoiminnot Pysyvä linkki

Kirjaudu sisään jättääksesi kommentin.