CMS API cannot connect; 400 bad request.

[jaheshkhan]

whenever i tried to access CMS API  it ended up with error 400 BAD request. reason is syntax error. 

what syntax error for this https://172.17.58.17:445/api/v1/callProfiles/

or https://core.test.lab:445/api/v1/callProfiles/

172.17.58.17=core.test.lab= webadmin ipv4

There is a firewall between the webadmin and PC im trying to access. 445 is open. i can reach the home page of webadmin. even authentication is 200 OK. but cannot access to api.

xmpp is registered and connected.

is it because no DNS entry of XMPP domain in DNS? 

[Gregory Brunn]

Last time I had something like this it was with the encoding I was sending it. Can you screen shot your postman settings. 

[Gregory Brunn]

Well to be clear you are just doing get request right? 

[jaheshkhan]

yes im doing GET request.
yesterday xmpp service was not connected. today i used internal CA. generated new certificate and applied. callbridge and xmpp shows connected.

but API still do the same.
I cannot take a screenshot now. ill try tomorrow. but may i know why API not showing any thing. only authentication works. its CMS 2.1. once activated smartnet we will upgrade it. now its not activated it.

Im trying for RECORDER configuration.

[jaheshkhan]

is there any thing that xmpp should be active to do API connection?

is there any port other than https between postman client and webadmin? we have a firewall in between.

[jaheshkhan]

its a fresh CMS.

today i didnt try to use POST request. only GET I tried.

[jaheshkhan]

do i need to install root CA certificate in my client machine where postman is installed?

[jaheshkhan · Accepted solution]

my god.
what a mistake i was doing.

it was just because of case sensitive issue of url

https://172.17.58.11:445/api/V1/

instead of v1 i was typing V1. case sensitive.