Getting all the Services with the API in 11.1

Hi,

I use the GET https://tddev.unh.edu/TDWebApi/api/{appId}/services API call to fetch all Services and then check if a correct Service is passed in during ticket creation against this list, and if not, I use the list of Services to warn the user so they can look at the available Services. We upgraded to TDx 11.1 recently in our Dev environment, and now this call only fetches Services that are Public. How can I get the non-public ones? We are planning to upgrade our Test environment next week, but I need to resolve this issue first.

Thanks,

Monika

Tags API services
Asked by Monika Fekete on Mon 6/22/20 3:59 PM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Mark Sayers Tue 6/23/20 9:06 AM

Hello Monika,
I believe that we need more information about what the access level of your API user looks like (the one you're using to authenticate into TDX in these API calls.

  • Does it have Client Portal access?
  • Does its client portal security role have the View Services permission? What about the View All Services permission?
  • What groups is it a part of?
  • Which services are not coming back vs. what you expect? How are these services permissioned?

I am betting you'll find the issue is somewhere in the client portal security role for this user and whether or not it has the proper permissions to view the service catalog and view all permissions. 

No feedback
Hi Mark,

I'm using the Administrative Account for authentication. Our admins are trying to find out if anything changed with that account.
I'm trying to fetch all Services, and the call worked perfectly before we upgraded to 11.1, but now it only gets the Services that are Public. I'm not sure how the services are permissioned, but the ones I'm trying to get are not Public, and those don't come through with this API call.
- Monika Fekete Wed 6/24/20 3:57 PM
I think I suggested this to Amy, but you may need to use an actual User account to call that endpoint successfully. If the endpoint's documentation doesn't specifically note that the Admin user is needed, we heavily suggest you use a regular API user account because the Admin user *is not* guaranteed to work with every single API endpoint, and the fact that it was working previously was likely luck rather than intent. - Mark Sayers Thu 6/25/20 4:37 PM