I'm working on small ticket system. It's very simple and useable already, but I want it to be OOP in every possible way.
So currently I'm at the point when I've started wondering, what might the API of such system look like or what it could offer.
For example there is Twitter API, but twitter is a public service. The ticket system on the other hand is more of the private way of communication between some company and its customer. So as I think you can't ask for someones tickets or data via uri as you can do with twitter.
But my question goes not only for my system, but for those who have small projects as mine and who have similar question, but didn't have time to ask it.
Hope to hear interesting thoughts about it. Thank you all.
UPD: My system currently have an interface of it own. System is intended to find solution to customers question. You might think, that it is similar to SO, but no. SO involves a community. My system is absolutely private. Like peer-to-peer. Customer asks a question and moderator replies to it. The discussion can go on and on, but only between to of them. No one else is involved in it. Also user can change state of the ticket, something like issue feature maybe at Github. Also when customer is not around, but staff answears, customer get notification of it via email.
Any other questions?