Hi, It was more a case of there was demand for an API, we didn't really have the time to dedicate that would be required for a fully functional API. In our discussions we felt that rather than push the deadline forward for many months we would try and get a basic API out there, see what the demand was like, see what features people wanted and then try and develop the API over the months to meet those demands where possible.
To be honest there hasn't been a huge demand for this and it might be as you say that until we have a full functional API then more people might become interested. You reply and others gives weight to that suggestion.
If you put together a rough outline of what you plan to use it for and what type of features you will need then i can go to the developers and put a case forward for this. I do agree you have a point that tournament support shouldn't be an after-thought and it is a valid point but there are also things in the cash API that are lacking that we haven't expanded on due to time constraints so the decision was based on what could we add that would benefit the most people with the time we had.
On the other side of the coin, we had lots of people before in threads where we explained putting together an API was a massive job and the overwhelming response was it doesn't need to be a rounded solution, just give us something basic we can work with initially and you can build from there. That is the approach we went with in the end.
But like i said if you can get me an outline of the needs and features you want for tournament support ill put it forward to developers and see if its something we can get on the feature list.
Thanks
Morny