200 error: missing username when logging in using Parse and LiveCode <p>I am trying to login to Parse through LiveCode but keep getting this error:</p> <blockquote> <p>{"code":200,"error":"missing username"}</p> </blockquote> <p>I have been able to create users, even validate user's email (through the REST API in Parse) but when I try to login I keep getting an error. I think there is something wrong with my JSON formatting or the GET call but I can't figure it out. </p> <pre><code>command mainLogin local tLoginA, tLoginJson, tReturn, tLogin setHeaders put fld "username" into tLoginA [ "username" ] put the cPassword of fld "password" into tLoginA [ "password" ] put urlEncode ( JSON_stringified ( tLoginA ) ) into tLogin put urldecode ( tLogin ) --testing get url ( "https://api.parse.com/1/login?" &amp; tLogin ) put it --testing put JSON_parsed ( it ) into tReturn if ( tReturn [ "error" ] &lt;&gt; empty ) then answer "Please try again: " &amp; tReturn [ "error" ] end if if ( tReturn [ "sessionToken" ] is NOT empty ) then //user logged in successfully put tReturn [ "sessionToken" ] into sSessionToken put tReturn [ "objectid" ] into sObjecteID answer "Welcome " &amp;&amp; tLoginA [ "username" ] mainClearFields end if end mainLogin </code></pre> <p>The functions <code>JSON_parsed()</code> and <code>JSON_stringified()</code> are from a JSON library by Andreas Rozek.</p> <hr> <p><strong>Update</strong></p> <p>I pulled this from the Parse.com REST API documentation on logging in:</p> <blockquote> <p>After you allow users to sign up, you need to let them log in to their account with a username and password in the future. To do this, send a GET request to the /1/login endpoint with username and password as URL-encoded parameters...</p> </blockquote> <p>I get that conceptually but I can't get it to work.</p> <p>Thanks Mark for your comment. I see that I was using the Post header handler which has the <code>Content-Type: application/json</code> added but that doesn't change much. According to the Parse.com docs the GET verb is the proper one (I changed the code to show the new header handler).</p>