@phildunlap Makes sense. Thanks for the clarification.
Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
D
Posts made by dstoryQuest
-
RE: Mango 3.5 API session token changeposted in How-To
-
Mango 3.5 API session token changeposted in How-To
After upgrading to Mango 3.5, I discovered that the "MANGO8080" session token, which is documented at https://help.infiniteautomation.com/mango-rest-api-authentication/ is no longer returned in the response.
Instead, a longer token (something like '2-64cb74e4-2ca3-4ea3-aad4-7c36b813c4fb=node019x9glwhysk0q1wxmehnp0qgl6141.node0') is returned and required for subsequent API requests. I don't see any information about this in the release notes.
Could you please provide clarity and confirmation regarding this change to the API authentication method?
-
Bookend point-values for time rangeposted in How-To
Is there a way when retrieving a time range of point-values via the Mango API to include the last logged value prior to the beginning of the time range, and the first logged value after the time range?
This is primarily for graphing purposes, so that data-points with infrequent value changes will have accurate data at the beginning and end of the graph, or even if the selected time range contains no logged values.