Please add a section for Search API HTTP return codes and Error Messages, and please make sure each set of codes/errors (REST v. Search) is clearly indicated.
Also a Search Return Values page would be nice :) -Chad On Mon, Apr 13, 2009 at 7:11 PM, Doug Williams <[email protected]> wrote: > Coderz, > I am refactoring the API documentation [1] to make it friendlier on the eyes > and easier on new developers. Please give it a once over and reply with any > of errors, addition requests, or suggestions. We will be using these new > docs officially in a few days (linked from the apiwiki.twitter.com) once any > glaring omissions and/or errors are addressed. > > My goal is to make the documentation more robust and example laden to help > new developers get going without needing help. Suggestions and critism along > those lines is welcome. > > A final plea for help: > If you have some spare time and examples to borrow from, please send > [email protected] any code/instructions that I can then paste into method body > to help new devs get started. Basic Hello World! style usage examples for > each method would go a long way to curbing new developer problems. Be sure > to include a link to any libraries your example is using. Working full > length example code hosted on github would be preferred. > > 1. http://apiwiki.twitter.com/Twitter-API-Documentation > > Thanks, > Doug Williams > Twitter API Support > http://twitter.com/dougw
