Changelogic Web Services API
- Changelogic
- Changelogic API
There are services on two different protocols. The older ones are property-based, and the newer ones are based on SOAP.
Property-based services
Publicly available services
Input
The input parameters should be sent in a single HTTP or HTTPS request, in one of the following flavours:
- a GET request
- a POST request with MIME encoding application/x-www-form-urlencoded
- a POST request with MIME encoding multipart/form-data
The parameters are expected to be encoded in character set ISO-8859–13. Ordering of the input parameters is not important, nor whether they appear in POST or GET part of a request.
Output
Usually, these services returns contents of a property file. The property file format is described in Java SDK.
There are three standard properties for output of any service:
| Property | Explanation |
|---|---|
| devweb.notice | Any informational messages that were generated. If the value is empty, no messages were generated. |
| devweb.warning | Any warning messages that were generated. If the value is empty, no warnings were generated. |
| devweb.error | If this property is present, the action failed. Value is a text message explaining the error that occurred. |
SOAP-based services
You can see the whole WSDL for these services by issuing a HTTP(S) request soap_service_public.php?wsdl to your instance of Changelogic, e.g. https://changelogic.webmedia.ee/soap_service_public.php?wsdl
However, not all the services are meant for public access. The ones meant for public use are listed below; others are subject to change or disappear in future versions without any further notice.
Services for public use:
- Add_task_elapsed_time
- Get_checkout_data
- Get_last_checkpoint
- Get_last_versiojn
- Get_task_priorities
- Get_task_states
- Get_task_types
- Get_tasks
- Get_version_checkout_data