loginByLoginId using JSON content type returns USER_WRONG_PASSWORD

I am making loginByLoginId call using json as input, but it returns USER_WRONG_PASSWORD. Can see all my input details are correct. Same API works with form-data input. Did anyone experience issue with json input.
Request :

Hello @arul,

Please provide the full request, including the endpoint (while masking your credentials, of course).
Also, are you using the Kaltura SaaS or a self hosted instance? If the latter, you should inspect the request as logged in /opt/kaltura/log/kaltura_api_v3.log.

Hello @Jess,

I am using SAAS Kaltura and testing using postman. Same credentials works when I use input as form-data.
URL : https://www.kaltura.com/api_v3/service/user/action/loginByLoginId
Request body:{
“expiry”: 86400,
“loginId”: “user@company.com”,
“partnerId”: 123,
“password”: “******",
“privileges”: "



<?xml version="1.0" encoding="utf-8"?> KalturaAPIException USER_WRONG_PASSWORD Wrong password supplied 0.0011179447174072


This works correctly for me:

curl -v “https://www.kaltura.com/api_v3/service/user/action/loginByLoginId” -H “Content-Type: application/json” -d ‘{“loginId”: “user@example.com”,“partnerId”: 7373,“password”: “SomePasswd”,“privileges”: “”}’

Please check whether it does for you as well. If it doesn’t, since you’re using the Kaltura SaaS, please submit a support ticket and include the above request as well as the full response you’re getting, including the headers.
Sample response:

  • Mark bundle as not supporting multiuse
    < HTTP/1.1 200 OK
    < Date: Mon, 14 Oct 2019 09:02:15 GMT
    < Server: Apache
    < X-Me: pa-front-api6
    < Access-Control-Expose-Headers: Server, Content-Length, Content-Range, Date, X-Kaltura, X-Kaltura-Session, X-Me
    < X-Kaltura-Session: $SESSION_ID
    < Access-Control-Allow-Origin: *
    < Expires: Sun, 19 Nov 2000 08:52:00 GMT
    < Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
    < Pragma: no-cache
    < Vary: Accept-Encoding
    < Content-Length: 257
    < Content-Type: text/xml;charset=UTF-8


Thanks Jess, will raise with support.