ActivityTimeline REST API
We’ve Moved!
You’re viewing an old version of our documentation, which is no longer being updated.
Please visit our new and improved Help Center here: ActivityTimeline
All API requests can be made by ActivityTimeline user with Administrator permission only.
ActivityTimeline REST API is turned off by default. You must turn it on before the first use.
ActivityTimeline REST API can be turned on by changing ActivityTimeline REST API setting at AT REST API page in Configuration:
How to Use REST API
Create a unique AT REST API authorization token in ActivityTimeline configuration
Call API methods with specifying that auth-token as a request Header or URL parameter (or auth_token before AT v8.3.0).
Sample Java/C# code of AT REST API usage
Sample Java project that demonstrates how to call AT REST API can be downloaded here (all API methods):
Sample .NET (C#) project that demonstrates how to call AT REST API can be downloaded here (some API methods):
Important Note when calling AT REST API from JavaScript/Node.js code.
ActivityTimeline uses number identifiers that could be larger than JavaScript number type supports.
As a result, some JavaScript JSON parsers replace the last few digits of an 'id' with zeros making that 'id' invalid.
Example: Actual 'id' of 1235598463805867311 becomes 1235598463805867300
Authorization
You can authorize into the REST API by specifying a unique Authorization Token in one of 4 supported ways:
Authorization Token can be generated at ActivityTimeline Configuration → AT REST API page. Handle it with the same security as you would a password. |
|---|
You can authorize into the REST API by specifying a unique Authorization Token in one of 4 supported ways:
Authorization Token can be generated at ActivityTimeline Configuration → AT REST API page. Handle it with the same security as you would a password. |
|---|
Methods:
Timeline Schedule & Workload v4.2.0+
Returns information about user and events (Jira issues and custom events) for specified user for specified period of time.
Request
GET /rest/api/1/timeline?auth_token=YOUR_AUTH_TOKEN
QUERY PARAMETERS
Parameter | Type | Description |
|---|
Parameter | Type | Description |
|---|---|---|
start * | string | Start of the period formatted in "yyyy-MM-dd" format |
end * | string | End of the period formatted in "yyyy-MM-dd" format |
teamId * | long | Id of a specific team |
eventType | string | Optional If specified then the system will filter returned items to the specified type.
|
jql | string | v10.4.0+ Optional If specified then the system will filter the issues based on the provided JQL filter query. Also, you may specify |
* indicates required parameters
Example
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline?teamId=1234567890&start=2016-07-11&end=2016-07-18&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline?teamId=1234567890&start=2018-11-30&end=2019-01-01&eventType=HOLIDAY&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline?teamId=1234567890&start=2018-11-30&end=2019-01-01&eventType=BOOKING&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline?teamId=1234567890&start=2018-11-30&end=2019-01-01&eventType=ISSUE&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline?teamId=1234567890&start=2018-11-30&end=2019-01-01&eventType=WORKLOG&auth_token=YOUR_AUTH_TOKENResponses
|
|---|
|
|---|
Returns information about user and events (Jira issues and custom events) for specified user for specified period of time.
Request
GET /rest/api/1/timeline/$username?auth_token=YOUR_AUTH_TOKEN
QUERY PARAMETERS
Parameter | Type | Description |
|---|
Parameter | Type | Description |
|---|---|---|
start * | string | Start of the period formatted in "yyyy-MM-dd" format |
end * | string | End of the period formatted in "yyyy-MM-dd" format |
username * | string | Username or accountId of specific user |
eventType | string | Optional
|
jql | string | v10.4.0+ Optional If specified then the system will filter the issues based on the provided JQL filter query. Also, you may specify |
* indicates required parameters
Example
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline/admin?start=2016-07-11&end=2016-07-18&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline/admin?start=2018-11-30&end=2019-01-01&eventType=HOLIDAY&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline/admin?start=2018-11-30&end=2019-01-01&eventType=BOOKING&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline/admin?start=2018-11-30&end=2019-01-01&eventType=ISSUE&auth_token=YOUR_AUTH_TOKEN
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/timeline/admin?start=2018-11-30&end=2019-01-01&eventType=WORKLOG&auth_token=YOUR_AUTH_TOKENResponses
|
|---|
|
|---|
Returns information about Jira issues and custom events scheduled on the Team Panel (not users) for a specified period of time.
Request
GET /rest/api/1/team/$teamId/timeline?auth_token=YOUR_AUTH_TOKEN
QUERY PARAMETERS
Parameter | Type | Description |
|---|
Parameter | Type | Description |
|---|---|---|
start * | string | Start of the period formatted in "yyyy-MM-dd" format |
end * | string | End of the period formatted in "yyyy-MM-dd" format |
teamId * | long | Id of a specific team |
* indicates required parameters
Example
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/team/1234567890/timeline?start=2025-07-11&end=2025-07-18&auth_token=YOUR_AUTH_TOKENResponses
|
|---|
|
|---|
Returns information about users and workloads for specified team for specified period of time.
Request
GET /rest/api/1/workload?auth_token=YOUR_AUTH_TOKEN
QUERY PARAMETERS
Parameter | Type | Description |
|---|
Parameter | Type | Description |
|---|---|---|
start * | string | Start of the period formatted in "yyyy-MM-dd" format |
end * | string | End of the period formatted in "yyyy-MM-dd" format |
teamId * | long | id of specified team |
projectKey | string | Optional ActivityTimeline v8.1.2 and above |
startOffset | int | Offset for first users, default is 0 |
maxUsers | int | Maximum users count to return, max 50 |
includeProjectDetails | boolean | Optional Activity Timeline v8.2.0 and above Example:"username": "amy.kartel",
"workload": [
{
"day": "2021-07-12",
"day0fWeek" : "mon",
"hours": {
"ABC": 4,
"CDF": 2,
"AMS": 0.5
}
},
{
"day": "2021-07-13",
"day0fWeek": "tue",
"hours": 0
},
..........
{
"day": "2021-07-16",
"dayOfWeek": "fri",
"hours": {
"CDF": 7,
"AMS": 1
}
}
] |
jql | string | v10.4.0+ Optional If specified then the system will filter the issues based on the provided JQL filter query. Also, you may specify |
* indicates required parameters
Example
http://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/workload?start=2016-07-11&end=2016-07-18&teamId=1107507732947945188&startOffset=0&maxUsers=50&auth_token=YOUR_AUTH_TOKEN
Responses
|
|---|
|
|---|
Returns information about user and workloads for specified user for specified period of time.
Request
GET /rest/api/1/workload/$username?auth_token=YOUR_AUTH_TOKEN
QUERY PARAMETERS
Parameter | Type | Description |
|---|
Parameter | Type | Description |
|---|---|---|
start * | string | Start of the period formatted in "yyyy-MM-dd" format |
end * | string | End of the period formatted in "yyyy-MM-dd" format |
username * | string | Username or accountId of specific user |
jql | string | v10.4.0+ Optional If specified then the system will filter the issues based on the provided JQL filter query. Also, you may specify |
* indicates required parameters
Example
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/workload/admin?start=2020-07-01&end=2020-07-30&auth_token=YOUR_AUTH_TOKEN
Responses
|
|---|
|
|---|
Returns information about Team Panel workload (not users) for a specified period of time.
Request
GET /rest/api/1/team/$teamId/workload?auth_token=YOUR_AUTH_TOKEN
QUERY PARAMETERS
Parameter | Type | Description |
|---|
Parameter | Type | Description |
|---|---|---|
start * | string | Start of the period formatted in "yyyy-MM-dd" format |
end * | string | End of the period formatted in "yyyy-MM-dd" format |
teamId * | string | id of a specific team |
* indicates required parameters
Example
https://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/team/1234567890/workload?start=2025-07-01&end=2025-07-07&auth_token=YOUR_AUTH_TOKEN
Responses
|
|---|
|
|---|
Returns information about availability of users of a specific team for a specified period of time.
User’s availability means how many hours of work user still has capacity to do taking into account currently scheduled tasks on that user.
Request
GET /rest/api/1/availability?auth_token=YOUR_AUTH_TOKEN
QUERY PARAMETERS
Parameter | Type | Description |
|---|
Parameter | Type | Description |
|---|---|---|
start * | string | Start of the period formatted in "yyyy-MM-dd" format |
end * | string | End of the period formatted in "yyyy-MM-dd" format |
teamId * | long | id of specified team |
startOffset | int | Offset for first users, default is 0 |
maxUsers | int | Maximum users count to return, max 50 |
jql | string | v10.4.0+ Optional If specified then the system will filter the issues based on the provided JQL filter query. Also, you may specify |
* indicates required parameters
Example
http://<ACTIVITYTIMELINE_INSTANCE>/rest/api/1/availability?start=2023-02-11&end=2023-02-18&teamId=5648895637201243664&startOffset=0&maxUsers=50&auth_token=YOUR_AUTH_TOKEN
Responses
|
|---|
|
|---|