New answers tagged support
The page where you can find the API key for your registered application says that the key doesn't need to be kept secret: [The key] is not considered a secret, and may be safely embed [sic] in client side code or distributed binaries. Abuse is typically an issue for the end-user, so you shouldn't be concerned about it beyond recognizing backoff ...
See http://api.stackexchange.com/docs/vectors, which allow requests to be made in batch. (I don't recall this article existing at the time of asking.)
The code in question was not generated by Stack Exchange. It was generated by a user. So, yes, quite often, the HTML (and all other code samples generated by users) will be malformed. However, in this case, note that <li> tags are not required to have closing tags. I agree that it is bad form to leave them off, though.
figured it out. api.php has a field 'key' in it. It's not well advertised since a lot of the documentation focuses around the pure api, but after you register, just put you key into that tha variable and conduct your searches the way you normally would and stackphp will take care of the rest.
Looking at the API 2.0 docs it looks like you can only pull favorites for a set of users - see http://api.stackexchange.com/docs/favorites-on-users#order=desc&min=2011-12-01&max=2012-01-01&sort=added&ids=29407&filter=default&site=stackoverflow&run=true It explains how the list of users is currently constrained to 100 entries, so ...
The 2.0 API provides support for /search: http://api.stackexchange.com/2.1/search?site=[site]&intitle=[search string] If you want to constrain this to your posts, 2.0's /search/advanced path allows you to filter by user, or by basically anything else: http://api.stackexchange.com/2.1/search/advanced?site=[site]&title=[search string]&user=[your user ID] ...
Top 50 recent answers are included