<i>Here&#x27;s an API document I wrote.[1] Comments?</i><p>You asked, so:<p>The organization can be better. Usually when I am looking at an API, the first question I have is, &quot;What is this API, what can I do with it?&quot; There&#x27;s one sentence about that in the header, but it&#x27;s not very clear. Then you jump right into low-level protocol details. Your pictures are good, and help to understand, but they come way late.<p>The broad organization should be something like: 1 &quot;Here&#x27;s what you can do with this API&quot; 2 &quot;Here&#x27;s how to use it&quot; 3 &quot;Here are the fine details&quot; and maybe (4 &quot;Legal garbage&quot;)<p>Nice quote at the bottom.