Strange behavior with the API calls

3 posts / 0 new

Tue, 05/09/2023 - 09:29

jbalzac

Hello, I am hoping that there's someone around to help me understand what is happening. Currently I am trying to create a report utilizing API for my company, but I am running into some issues. First I tried creating an inventory report using the tenantDeviceInventory endpoint, but I found that the data was actually not showing all of the headsets certain users within the company were actually using. Several users actually were using plantronics products, but they were not appearing in the report. When I ran the same "inventory" report within Plantronics Manager Pro it showed them, so I thought maybe the Plantronics Manager Pro report was using a combination of endpoints to get its dataset. I then tried the tenantDeviceDistribution endpoint, and this one seemed to include some headsets that certain people were using. I specified the users that I knew had missing headsets from the previous report (username query parameter) to see if this distribution report would show the headsets and it seemed to be working, but when I created the logic to pull down all 20,000+ records of the data and analyzed it, some of these users I had searched for individually utilizing the same endpoint were missing entirely. Furthermore, as my application is looping through the dataset to pull down all the records, the API calls seemingly start to fail. Lets say I am pulling 500 records per page, some pages within the pagination come back completely blank, others come back with repeated data. The result is an over-inflated dataset of somewhere near 30,000+ to 40,000+ records with tons of repeated rows of data and also missing data. I have spent days analyzing my application to ensure that this isn't an issue on my end and I have noticed the same behavior of repeated data and blank pages appearing when I simply use POSTMan to query the endpoints! Am I hitting some sort of API transaction limit (I cannot find any information usage limitations) or is this a bug ocurring on your end? I appreciate any help I can get! Thank you, John Balzac

Mon, 05/15/2023 - 08:05

jbalzac

Seeing as the last activity was almost 2 years ago I am going to assume this forum is dead. Quite unfortunate. Support for this product does not seem to be available at all. To anyone reading this, you're probably out of luck.

Tue, 05/16/2023 - 04:09

(Reply to #2) #3

AWhite

Good Morning John, Thank you for reaching out to us. We have asked our support team to raise a case on your behalf. We will let you know the ticket number via direct email. For reference, Poly support can be reached through this page: https://www.poly.com/contactsupport/ Regarding your API queries, When you receive blank pages through POSTMan, do you recieve any errors at all? Is the POSTMan test iterating through the pages automatically? How many POSTman queries do you need to run before experiencing a blank page, or repeated data? Since when have you been having issues? Has this report ever worked as expected? I will reach out to you via direct email so you can let us have some POSTMan examples where you experience the error. Additionally I will reach out to our Platform team to see if they can see any errors occurring. Regards, Alasdair

Add new comment