Sorry, you need to enable JavaScript to visit this website.

You are here

API to get Location history gives 401 error.

3 posts / 0 new
Last post

Prakash's picture
by Prakash

API to get Location history gives 401 error.

Hi,

I am trying to get location history through API as mentioned below but returns the 401 error. I have added serial number of the asset tag 'C0111905278C3329'. Not sure whether i am missing any detail. Please have a look on screenshot below.

 

Vinodh's picture
by Vinodh

Hi Prakash,

Hi Prakash,

I checked the call syntax and did not find issue with it.

In order to understand the issue better, could you please confirm the following:

1.  You have access to the Track & Monitor API within Telstradev portal.

2.  Authentication scope used was "LOT_DEVICES_READ" when acquiring the token.

Also, please read documentation in https://dev.telstra.com/content/track-and-monitor-api#section/Getting-Access-to-the-API for more information.

 

Regards,

Vinodh 

Michelle's picture
by Michelle

Resolved: 401 Track and Monitor API Error

Hi Prakash,

I believe you have resolved this issue offline with our Track and Monitor DevOps experts. 

They found that the API Keys you were using were invalid, which was causing this error. Make sure you are using the production keys under your company profile to access production apps. You can switch from your personal developer profile to your company profile by selecting it in the drop down in the top menu bar. 

There is currently a known issue where developers with multiple companies may not be able to switch company profiles. We are actively working on resolving this ASAP. In the meantime, please reach out if you are unable to switch companies.

There is also a known issue when using the shortcut button to copy your Client Secret from the My Apps and Keys page adds a trailing space which may cause authentication errors (i.e "invalid client" error). Simply check the copied secret and remove any trailing or leading spaces. This is also something our devops team is working on resolving ASAP!

Thanks for your patience and glad to hear the issue was resolved promptly offline! 

Log in or register to post comments