Using Services86 you will be able to access the TicketAgent
There are two known bugs that will be solved in the upcoming release R05 (both Online and Onsite) which will give you an error like:
"SuperOffice.Exceptions.SoException: WCF Method failed ---> System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (502) Bad Gateway. ---> System.Net.WebException: The remote server returned an error: (502) Bad Gateway."
This happens if you have a ticket status with -1 in the time_counter field or if you try to save a ticket entity (SaveTicketEntity) where the replied_at field IS NULL.