O365/ SharePoint Online - Getting User Image URL Without Callback In JSOM

In this article, I’ll share one little finding, which I recently found. This is related to the current user profile image, which we need to show on our SharePoint Online site in our custom master page. Generally in JSOM, whenever we call/ load something, we need call backs. Thus, we need to depend on either respective success or failure method. Here, I’ll share how we can get current user or any user profile image without Callback.


In our one of SharePoint Online sites, we need to show current logged in user profile image. We have our custom master page. Thus, we need to basically get the current user property – “Picture URL” and render. Since there is not another option we can find, we have implemented it, using JSOM. Thus, code is really simple, as shown below.


Here, I only shared sample code and not the complete one.

We have written one method fetchUserDetails, which loads the user details, as shown below. 

  1. SP.SOD.executeOrDelayUntilScriptLoaded(fetchUserDetails, 'SP.UserProfiles.js');  
  2. var userProfileProperties;  
  4. function fetchUserDetails() {  
  5.     //Get Current Context  
  6.     var clientContext = new SP.ClientContext.get_current();  
  7.     //Get Instance of People Manager Class  
  8.     var peopleManager = new SP.UserProfiles.PeopleManager(clientContext);  
  9.     //Get properties of the current logged in user  
  10.     userProfileProperties = peopleManager.getMyProperties();  
  11.     //Load all the properties.  
  12.     clientContext.load(userProfileProperties);  
  13.     //Execute the Query.  
  14.     clientContext.executeQueryAsync(onfetchUserDetailsSuccess, onfail);  
  15. // fetchUserDetails  
  16. Success method as below  
  18. function onfetchUserDetailsSuccess() {  
  19.     //Get picture URL  
  20.     var pictureUrl = userProfileProperties.get_pictureUrl();  
  21.     //Currently just showing in alert  
  22.     alert(pictureUrl);  
  23. // onfetchUserDetailsSuccess   

Disadvantage of above approach

There is nothing wrong in the approach given above but then we need to wait for the Callback and then we get the profile image for the current user. It’s not like that we will directly get the current user profile image, so it’s also a bit like lazy loading.

New approach

While Googling for some issue, I found that there is Delve Service, which directly returns any user profile image without call back. Service name is DelveApi.ashx and way to call is given below.

  1. // Get current site URL  
  2. var currentSiteURL = _spPageContextInfo.siteAbsoluteUrl;  
  3. //Form the delve service URL  
  4. var delveServiceURL = currentSiteURL + "/_vti_bin/DelveApi.ashx/people/profileimage?userId=" + _spPageContextInfo.userLoginName + "&size=L";   

We can also mention the size (L, M and S). Actually, this Service downloads the respective image, as per the specified size. Hence, we can either use “div” tag or “img” tag and set the “src” property of them. No dependency on Callback or there is no need to handle the failed method.

One more benefit of using this approach is, if we know the login name of the user, we can easily download the profile image by specifying respective login name to the userId parameter. Currently, we are passing current logged in user’s login name. This is useful where in some scenarios; we need to show the users' listing.

I hope, you will find this little finding useful.