4 ms·
It's not terribly precise but it's not very confusing if you're familiar with the way HTTP APIs are typically constructed nowadays, which presumably would norma
by jameshart 14y ago
It's not terribly precise but it's not very confusing if you're familiar with the way HTTP APIs are typically constructed nowadays, which presumably would normally be the case for the kinds of applicant they want to attract. They want you to HTTP POST a JSON-formatted (yes, you could say 'encoded') JavaScript dictionary - a 'hashtable' (hash is an appropriate abbreviation for this, albeit a confusing one) - i.e. a JavaScript object whose key/value pairs match the keys they specified.
Of course, the question of why they requested the key/value pairs be POSTed in JSON format when HTTP specifies a perfectly simple and widely supported mechanism for POSTing key-value-pairs to a web endpoint, which is application/x-www-form-urlencoded... well that's a different problem.