Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
If you’re running into issues with LogicMonitor’s REST API, this document should help you identify the issue and quickly find a resolution. We’ll make sure this page stays up to date and continue to add possible issues as we come across them. Consider the following:
If you’re attempting and failing to authenticate REST API requests with API Tokens:
HTTP Verb: GET
Resource Path: /dashboard/widgets
If you aren’t getting the correct Authentication Header, here are a couple of intermediate values that may help you troubleshoot (for the same request parameters listed above):
Concatenated Request Variables (HTTP Verb + epoch + data + resource path) : GET1502813538347/dashboard/widgets
HMAC-SHA256 of Request Variables (using Access Key & a Hex digest) : 31febefbe1316b761fa19982eae857d8b97facbc764eb91e5f062af415cbd33a
Base 64 encoded HMAC value: MzFmZWJlZmJlMTMxNmI3NjFmYTE5OTgyZWFlODU3ZDhiOTdmYWNiYzc2NGViOTFlNWYwNjJhZjQxNWNiZDMzYQ==
If you’re using the Windows command prompt to run cURL commands, note that the Windows command prompt doesn’t support single quotes. This can be an issue because JSON data payloads are typically specified with single quotes. As an alternative, you can save the JSON data in a .txt file and use the @filename syntax in your curl command, like so:
curl -u user:password -d @payload.txt -H "Content-Type: application/json" -X POST "https://account.logicmonitor.com/santaba/rest/service/services"
In This Article