List the project-list bulk actions
Returns the bulk actions the project list offers, each with the endpoint and ready-made body to call.
Names are code names, not translated, except stage names, which are the account's own.
Use it to:
- Build the bulk-action menu of a project list; resolve the active stage IDs for PUT /v2/projects/stage
Behaviour:
- Idempotent.
- Safe to retry.
- Changes are visible to the next read immediately.
Next: PUT /v2/projects/status, PUT /v2/projects/stage, PUT /v2/projects/resource-planner
See also: GET /v2/projects
Not yet documented: response → default ordering.
curl -X GET "https://app3.timelog.com/your-account/api/v2/projects/actions" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN"
import requests
import json
url = "https://app3.timelog.com/your-account/api/v2/projects/actions"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://app3.timelog.com/your-account/api/v2/projects/actions", {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("GET", "https://app3.timelog.com/your-account/api/v2/projects/actions", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://app3.timelog.com/your-account/api/v2/projects/actions')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
response = http.request(request)
puts response.body
{
"Entities": [
{
"Properties": {
"Name": "DeleteAction"
}
},
{
"Properties": {
"Name": "ChangeStatusTo",
"Actions": [
{
"Name": "Quote",
"Uri": "status",
"Body": {
"Status": 0
}
},
{
"Name": "Approved",
"Uri": "status",
"Body": {
"Status": 1
}
},
{
"Name": "InProgress",
"Uri": "status",
"Body": {
"Status": 2
}
},
{
"Name": "OnHold",
"Uri": "status",
"Body": {
"Status": 3
}
},
{
"Name": "Completed",
"Uri": "status",
"Body": {
"Status": 4
}
},
{
"Name": "Archived",
"Uri": "status",
"Body": {
"Status": 5
}
},
{
"Name": "Cancelled",
"Uri": "status",
"Body": {
"Status": 6
}
}
]
}
},
{
"Properties": {
"Name": "ChangeStageTo",
"Actions": [
{
"Name": "Initiation",
"Uri": "stage",
"Body": {
"Stage": 1
}
},
{
"Name": "Planning",
"Uri": "stage",
"Body": {
"Stage": 2
}
},
{
"Name": "Execution & Controlling",
"Uri": "stage",
"Body": {
"Stage": 3
}
},
{
"Name": "Closing",
"Uri": "stage",
"Body": {
"Stage": 4
}
}
]
}
},
{
"Properties": {
"Name": "ResourcePlanner",
"Actions": [
{
"Name": "EnableResourcePlanner",
"Uri": "resource-planner",
"Body": {
"IsAddingToResourcePlanner": true
}
},
{
"Name": "DisableResourcePlanner",
"Uri": "resource-planner",
"Body": {
"IsAddingToResourcePlanner": false
}
}
]
}
}
],
"Links": [
{
"Href": "https://app{server-number}.timelog.com/{account}/api/v2/projects/actions",
"Rel": "self"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Internal Server Error",
"message": "An unexpected error occurred on the server",
"code": 500,
"requestId": "req_1234567890"
}
/v2/projects/actions
Target server for requests. Edit to use your own host.
OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.
Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
> Not yet documented: how to obtain a token.
> Not yet documented: token lifetime.Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).
The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.
Not yet documented: how to obtain a token.
Not yet documented: token lifetime.
Responses
Omitted (not []) when the list is empty.