API version checking
I was testing my understanding of the endpoints for getting/checking API version support on Postman. All of the GET endpoints work just fine, but when I try the POST endpoint,
/d2l/api/versions/check
I keep getting a 302 error whenever I try. (I am using core:*.* oath2 scope and have authenticated as myself (Administrator — not that it should be needed).
This is my body (raw/JSON)
[
{
"ProductCode": "lp",
"Version": "1.29"
}
]
I have also tried without the array braces.
I have checked my Content-Type
I even tried using x-www-form-urlencode despite it not using the correct Content-Type
No matter what I try, It keeps giving me 302.
I even tried /d2l/api/versions/check/ instead of /d2l/api/versions/check (who knows the docs might have a typo, right?)
All with the same effect. I could provide a screenshot of the console, but it just says the same thing
Response body:
with nothing you wouldn't expect in the response header with this body.
I have even tried removing all extraneous space from the body to no effect.
Does anyone know what I am doing wrong?
Reacties
-
@Randall.S.394 I'm wondering why you would be sending a POST command in the first place. The versions API call is used to get the current version of the API to use to call other API's. But what ever reason, I was able to run it successfully. - You shouldn't need any special authentication, permissions or special scopes to run this one. I'm not sure what that error code means. Give it another try.
[
{
"ProductCode": "lp",
"Version": "1.85"
},
{
"ProductCode": "le",
"Version": "1.85"
}
]
-
Thank you for confirming it should work. I must have gremlins in there so I will try retyping it. The reason for using POST was I just wanted a harmless route to debug my POST construction in my script. I really didn't care what it was.
