Get issues
Get a list of the issues defined on your system. You can also filter the response to see only the issues corresponding to a certain task.
For security reasons, you need to perform a Login action before making any other public calls to the WorldServer API. The
sessionId in the response is your session token. Use this token in all the other calls that you make.
Also, make sure that you have the appropriate user type permissions to perform this API call. To view or update your permissions, in WorldServer, go to and then select your user type.
API call
<protocol>://<ws-host>:<ws-port>/ws-api/v1/issues?token=<sessionId>
Details
- GET method
- Content-Type in the header:
application/json - Mandatory parameter: the session token (as a query string parameter or as a key-value pair in the header)
Integration tips
For integration purposes, you might want to obtain information only about the issues corresponding to a specific task. If you already know the ID of the task, use the taskId filter.
Available filters
You can add the filters as query string parameters or as key-value pairs in the header:
| Filter | Description |
|---|---|
| fields=<fieldName1,fieldName2,…,fieldNameN> | The names of the fields to be included in the JSON response, separated by commas. Do not use in conjunction with the excludedFields filter. |
| excludedFields=<fieldName1,fieldName2,…,fieldNameN> | The names of the fields to be excluded from the JSON response, separated by commas. Do not use in conjunction with the fields filter. |
| offset=<number> | The zero-based starting index in the entire collection of the first item to return. |
| limit=<number> | The maximum number of collection items to return for a single request. By default, 30. The limit should be greater than or equal to 1. |
| taskId=<taskId> | The ID of the task whose issues you want to get. |
| viewMode=<value> | One of TASKS, ASSIGNED_OR_CLAIMED_TASKS, ASSIGNED, LOCALE_AND_WORKGROUP, or ALLOWED. The default value is ALLOWED. |
| includeClosed=<true/false> | A flag indicating whether closed tasks should be returned. |
Examples:
- <protocol>://<ws-host>:<ws-port>/ws-api/v1/issues?token=<sessionId>&taskId=7689
- <protocol>://<ws-host>:<ws-port>/ws-api/v1/issues?token=<sessionId>&fields=name&includeClosed=true
Response
Error messages
| Message | Status code |
|---|---|
| Limit not provided or invalid (It should be greater than or equal to 1.) | 400 Bad Request |
| Offset not provided or invalid (If the value is negative.) | 400 Bad Request |
| Optional filter taskId is invalid (If the value is not a valid number.) | 400 Bad Request |
Filter value for includeClosed is invalid (If the value is not true or false. ) | 400 Bad Request |
Filter value for viewMode is invalid (If the value is not one of the following: TASKS, ASSIGNED_OR_CLAIMED_TASKS, ASSIGNED, LOCALE_AND_WORKGROUP, or ALLOWED.) | 400 Bad Request |
| Offset out of range. Collection has only n items (If the offset value is greater than n.) | 400 Bad Request |
| No session token provided or invalid token | 401 Unauthorized |
| Resource TASK (ID) not found | 404 Not Found |
Troubleshooting
- Make sure that the endpoint you are calling is correct.
- Make sure that you are using the GET method for the call.
- Make sure that the Content-Type in the header is
application/json. - Make sure that your session token is correct and that it has not expired.