Trying to use GET /api/sysinfo call
Friday, July 17, 2020 at 11:03amI was trying below API call and received web page instead of expected Payload
GET /api/sysinfo
HTTP Headers
Accept: application/json
Content-Type: application/json
Authorization: Basic api_key
Example: Response Payload
{
"schema": "16.11.3",
"version": "16.11.4",
"timestamp": "2017-11-01 15:00+0000"
}
Reply to: Trying to use GET /api/sysinfo call
Friday, July 17, 2020 at 11:09amHi Mike,
Which environment are you testing with?
Duo
Reply to: Hi Mike, Which…
Friday, July 17, 2020 at 11:27amhttps://sandbox.esignlive.com
US#2 ( I believe )
Reply to: Trying to use GET /api/sysinfo call
Friday, July 17, 2020 at 12:14pmHi Mike,
Thanks for the information! I've checked the Trust Center and seems there's no down time today in US2 Sandbox. Are you using API Key or API Token to authenticate the call? Does it affect all API calls? From my test, I can only reproduce the issue when I use an API Key with wrong length (either shorter or longer).
Duo
Reply to: Trying to use GET /api/sysinfo call
Friday, July 17, 2020 at 03:26pmThx Duo... I'm using API Key, I will re-confirm length/value.
Reply to: Trying to use GET /api/sysinfo call
Friday, July 17, 2020 at 04:46pmHi Duo, I was trying GET https://sandbox.esignlive.com?api/sysinfo as I assumed there had to be a parameter with GET, The API Key value was ok.
It turned out that https://sandbox.esignlive.com/api/sysinfo seemed to be what was needed, per results below:
{
"schema": "16.38.14.43474",
"version": "16.38.9",
"timestamp": "2020-07-07 23:58+0000",
"git_hash": "6e21bbcfe69c1bad4a9bcc9a9c07f8b887bfa390"
}
Above is correct expected response y/n? Does not seem to include app version ( e.g. 11.35 or 11.36 ) correct y/n?