What's new 
We reset our Hexnode API key and started getting this response when calling the Hexnode REST API:
{"detail":"Invalid token."}
The API key is enabled under Admin > API. The same automation was working with the previous key. We were testing with a header like this:
Authorization: token
We also tried Basic authentication, but it failed with the same invalid token response. This is for managing Windows devices programmatically, including checking enrollment details and triggering device lifecycle actions. What is the correct authentication format for the Hexnode API after resetting the key?
52 Views
