This read-only API is easy for us to implement and easy for people to consume because it avoids that sort of detail. This also means that we can only provide the same data that is available on the website when you visit while logged out. That confines the type of useful data in this part of the API.
We are also planning an Interactive API, which has these very qualities. We already have most of the system in place, and we just need to secure a few things and then we'll start the discussion here about who is interested in the first draft. They will be allowed to create apps and access the same API that our mobile apps do.
During this period, we are starting open and seeing if there are problems. We may need to block things if they are abused. If you are concerned about being blocked, then send a valid user-agent HTTP header that includes some contact information such as an email address. If we find that your program is acting in a way that harms the experience of our other players, then we will contact you and we will figure out how it should work.
Do I need to identify myself, when I am calling your API? Or is it sufficient ie to use the parameter "From:"?
In some API implementations, developers need to register, will get API key and then they use the key in order to utilize APIs. This gives you the possibility to see utilization of your environment by different apps and blocking them if needed.