uqswq (uqswq) asked a question.
API query returns only connection infos though no error
Hi, this probably a stupid question but, as simple as this might be, I was unable to find any understanding about it: Why do my API query returns only connection infos instead of the actual stuff I asked for ?
I litterally copy pasted the code from the API documentation, so I can get an user by its login.
There's apparently no error in the result but only un full page of info about the query and the connection to okta's server, like the ip, all the handshake steps, the certificate, all the elements of my query striped in parts (which shows me that I made no mispells in it), some kind of key, blablaba. Though, no actual error, no warning, just not what I wanted and I don't get why.
Hi @uqswq (uqswq) ,, Thank you for reaching out to the Okta Community!
Just tested this in my environment, and I'm getting all the expected data. Not sure what would cause that for you.
Please try the POSTMAN integration to see what you get there, if you haven't already. Step-by-step here:
https://developer.okta.com/code/rest/
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Community members help others by clicking Like or Select as Best on responses. Try it today.
Hello,
Indeed I do get the expected result in postman afeter tinkering for an hour to figure how to issue an understandable request for the software....
Which doesn't really help me, cause since the query is input in a different fashion (ui for keys instead of plain text query with headers), so I still don't don't know where's my mistake. But maybe I give you my actual command you will see it :
(Run in a bash script)
curl -v -X GET \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Authorization: SSWS $token" \
"https://myorg.url/api/v1/users/$user"
Which is litteraly the code from the documentation. I suspect my api key to be the problem, maybe I generated it wrongly ?
Hi @uqswq (uqswq) , For a simple GET call I would expect most Admin roles that allow API key generation to work, but you can give it a try with a SuperAdmin account just to be sure.
That being said, I recommend opening a case to work with one of our support Engineers to get to the bottom of this.