Hi Trevor,

First of all, could you follow up directly with your account manager to understand where the slow behavior is coming from? Maybe we could improve the response time of this web API call.

Below a couple of options that you could try:

• You mentioned that you need to perform this API call 2 or 3 times per graph. Is it an option to perform the call in advance before a user opens a graph (for example, when the user logs in in the portal)? Assuming that the values of these properties don't change quite often, this could be an option. In that way, when a user opens a graph, your portal will only need to read this information locally. This approach will also required in case there are several concurrent users opening graphs at the same time.
• In case it is not an option to cache information in the portal, maybe you can retrieve this information in another way? Could you check if this information is available in the manager element that provision these services? If it is available, you can query directly this table and perform the filtering on your end.
• Another option is to create a custom API call using User-Defined API. This will allow you to define a custom API that could be tailored to your implementation (e.g. the custom API can already have the list of services with the NPC Service ID, so by the time that you executing the custom API call you can get a faster response).

Hope it helps.