question

Best Answer
Brendan Vanous said on Wed, 22 April 2015 at 5:10 PM

This issue has been resolved - please do let us know if you're still seeing any issues.

Brendan

---

5 Comments
jonnybee12345 said on Wed, 22 April 2015 at 12:51 AM

Had the same problem myself this morning, something was definitely changed overnight.

I fixed my end to account for changes, though it would good to get a heads up when something as critical as the login api gets updated.

To Fix,

Make sure your sending your login request with json encoded string (this was not the case yesterday)

Make sure you declare the content type in the request headers 'content-type','application/json'.

The response will now be a json encoded string - you need to parse this, (this was also not the case yesterday).

Totally understand the changes - as all the other api requests required the above apart from login.

---

dragongamestudio said on Wed, 22 April 2015 at 1:35 AM

ya, most of the API require sessionticket,
and there is no news or even a notification
and also the API documentation still same, when i do copy paste the example
in the documentation, it still say the header was not correct
:(

---

dragongamestudio said on Wed, 22 April 2015 at 4:50 AM

here is more detail about the error

Request "Content-Type: application/json; charset=UTF-8" HTTP header does not match required value: application/json

body is
{Username:"username",Password:"password",TitleId:"mytitle id"}

i am not added "charset=UTF-8" in the header, but it still say that i added it,
hmm... hope some one can help

---

Brendan Vanous said on Wed, 22 April 2015 at 5:10 PM

This issue has been resolved - please do let us know if you're still seeing any issues.

Brendan

---

dragongamestudio said on Wed, 22 April 2015 at 6:35 PM

thank you, i have try it again and it works,
thank you :)