[episod]

As someone who writes a bit of documentation for dev.twitter.com, I admit that a full accounting of every field that passes through the API is certainly missing. The reasons are boring and mostly historical, related to the organic growth of the API & its documentation; for much of the existence of the API, deep pre-existing understanding of Twitter itself was assumed and required for success. That combined with the majority of developers using scripting languages with loose typing meant that devs could fill in the blanks pretty easily.

A more exhaustive index of the fields, a kind of bird watcher's guide for the fields of the Twitter API, should make an appearance in the coming weeks.