diff --git a/versioned_docs/version-8.3/apis-tools/working-with-apis-tools.md b/versioned_docs/version-8.3/apis-tools/working-with-apis-tools.md
index 536721aa2b..03ce9baffe 100644
--- a/versioned_docs/version-8.3/apis-tools/working-with-apis-tools.md
+++ b/versioned_docs/version-8.3/apis-tools/working-with-apis-tools.md
@@ -43,6 +43,10 @@ type:"link", href:"/docs/8.3/apis-tools/java-client/", label: "Java client", doc
 }
 ]}/>
 
+:::note
+Other components in Camunda 8, such as [Tasklist API (GraphQL)](../apis-tools/tasklist-api/generated.md), provide language-agnostic APIs, but no clients to interact with them. GraphQL enables you to query, claim, and complete user tasks.
+:::
+
 ## Learn about Camunda Components and their APIs
 
 Camunda 8 components have APIs to enable polyglot developers to work with in their programming language of choice. Below are links to available component APIs.
@@ -59,6 +63,9 @@ type:"link", href:"/docs/8.3/apis-tools/operate-api/overview/", label: "Operate
 type:"link", href:"/optimize/3.11.0/apis-tools/optimize-api/optimize-api-authorization/", label: "Optimize API (REST)", description: "Get, delete, and export reports and dashboards, enable and disable sharing, and more."
 },
 {
+type:"link", href:"/docs/8.3/apis-tools/tasklist-api/tasklist-api-overview/", label: "Tasklist API (GraphQL)", docId:"apis-tools/tasklist-api/tasklist-api-overview"
+},
+{
 type:"link", href:"/docs/8.3/apis-tools/tasklist-api-rest/tasklist-api-rest-overview/", label: "Tasklist API (REST)", docId:"apis-tools/tasklist-api-rest/tasklist-api-rest-overview"
 },
 {
diff --git a/versioned_docs/version-8.3/components/best-practices/architecture/understanding-human-tasks-management.md b/versioned_docs/version-8.3/components/best-practices/architecture/understanding-human-tasks-management.md
index 9a0777462c..3f36c51903 100644
--- a/versioned_docs/version-8.3/components/best-practices/architecture/understanding-human-tasks-management.md
+++ b/versioned_docs/version-8.3/components/best-practices/architecture/understanding-human-tasks-management.md
@@ -26,9 +26,7 @@ As a general rule, you should assign human tasks in your business process to _gr
   </bpmn:extensionElements>
 ```
 
-Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to `claimTask`.
-
-<!--- To rework --->
+Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to [`claimTask`](../../../apis-tools/tasklist-api/mutations/claim-task.mdx).
 
 ```graphql
 claimTask(
@@ -56,9 +54,7 @@ If you have human tasks in your process, you must make up your mind on how exact
 
 - [Camunda Tasklist](/docs/components/tasklist/introduction-to-tasklist/): The Tasklist application shipped with Camunda. This works out-of-the-box and has a low development effort. However, it is limited in terms of customizability and how much you can influence the user experience.
 
-- Custom task list application: You can develop a custom task list and adapt this to your needs without compromises. Human tasks are shown inside your custom application, following your style guide and usability concept. You will use the Camunda Tasklist API in the background. This is very flexible, but requires additional development work.
-
-<!--- To rework. --->
+- Custom task list application: You can develop a custom task list and adapt this to your needs without compromises. Human tasks are shown inside your custom application, following your style guide and usability concept. You will use the [Camunda Tasklist API](../../../apis-tools/tasklist-api/generated.md) in the background. This is very flexible, but requires additional development work.
 
 - Third party tasklist: If our organization already has a task list application rolled out to the field, you might want to use this for tasks created by Camunda. You will need to develop some synchronization mechanism. The upside of this approach is that your end users might not even notice that you introduce a new workflow engine.
 
diff --git a/versioned_docs/version-8.3/components/best-practices/development/handling-data-in-processes.md b/versioned_docs/version-8.3/components/best-practices/development/handling-data-in-processes.md
index 999cd4c4c0..28b90d2265 100644
--- a/versioned_docs/version-8.3/components/best-practices/development/handling-data-in-processes.md
+++ b/versioned_docs/version-8.3/components/best-practices/development/handling-data-in-processes.md
@@ -48,9 +48,7 @@ In Camunda 8, [values are stored as JSON](/docs/components/concepts/variables/#v
 This best practice describes variable handling within Camunda 8. Process variables are handled slightly differently with Camunda 7. Consult the [Camunda 7 documentation](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/) for details. In essence, variable values are not handled as JSON and thus there are [different values](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/#supported-variable-values) supported.
 :::
 
-You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when completing the "Review tweet" task via the API:
-
-<!--- To rework. --->
+You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when [completing](../../../apis-tools/tasklist-api/mutations/complete-task.mdx) the "Review tweet" task via the API:
 
 ```
 // TODO: Double check!
diff --git a/versioned_docs/version-8.3/components/console/manage-clusters/manage-api-clients.md b/versioned_docs/version-8.3/components/console/manage-clusters/manage-api-clients.md
index ca7ec980ef..e0f50f7cce 100644
--- a/versioned_docs/version-8.3/components/console/manage-clusters/manage-api-clients.md
+++ b/versioned_docs/version-8.3/components/console/manage-clusters/manage-api-clients.md
@@ -29,6 +29,7 @@ The officially offered [client libraries](../../../apis-tools/working-with-apis-
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/grpc.md) API.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/optimize-api-authorization).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_docs/version-8.3/components/tasklist/introduction-to-tasklist.md b/versioned_docs/version-8.3/components/tasklist/introduction-to-tasklist.md
index 112e91648a..50f29d8c23 100644
--- a/versioned_docs/version-8.3/components/tasklist/introduction-to-tasklist.md
+++ b/versioned_docs/version-8.3/components/tasklist/introduction-to-tasklist.md
@@ -10,6 +10,13 @@ With Tasklist, orchestrate human workflows critical to your business and reduce
 
 As you model a business process using BPMN and deploy it to the workflow engine, users are notified in Tasklist when they're assigned a task.
 
-Tasklist also provides a [REST API](/docs/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md).
+Tasklist provides two APIs: a [GraphQL API](/docs/apis-tools/tasklist-api/tasklist-api-overview.md)
+and a [REST API](/docs/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md). Both APIs provide equal capabilities,
+allowing you to build your own applications or use the general [UI](/docs/components/tasklist/userguide/using-tasklist.md) that we have prepared for you.
+
+:::note
+The GraphQL and REST APIs are currently available, but the GraphQL API will be deprecated in future releases, although it will still receive updates for a limited period. If you are building new applications,
+we recommend using the REST API to ensure long-term compatibility.
+:::
 
 Tasklist is also available for production use (with support) in the Camunda 8 offering. To try out Tasklist in Camunda 8, sign up [here](https://signup.camunda.com/accounts?utm_source=docs.camunda.io&utm_medium=referral).
diff --git a/versioned_docs/version-8.3/guides/setup-client-connection-credentials.md b/versioned_docs/version-8.3/guides/setup-client-connection-credentials.md
index 72858f31eb..6de800eded 100644
--- a/versioned_docs/version-8.3/guides/setup-client-connection-credentials.md
+++ b/versioned_docs/version-8.3/guides/setup-client-connection-credentials.md
@@ -14,6 +14,7 @@ Here, we'll set up client connection credentials to create, name, and connect yo
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/grpc.md) API.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/optimize-api-authorization).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_docs/version-8.3/self-managed/tasklist-deployment/tasklist-authentication.md b/versioned_docs/version-8.3/self-managed/tasklist-deployment/tasklist-authentication.md
index 445d059dd2..ab99562be3 100644
--- a/versioned_docs/version-8.3/self-managed/tasklist-deployment/tasklist-authentication.md
+++ b/versioned_docs/version-8.3/self-managed/tasklist-deployment/tasklist-authentication.md
@@ -99,6 +99,14 @@ The user or user group can be assigned the following permission:
 
 For more information, visit the [Identity documentation](/self-managed/concepts/access-control/resource-authorizations.md).
 
+### Use Identity JWT token to access Tasklist API
+
+Tasklist provides a [GraphQL API](/apis-tools/tasklist-api/tasklist-api-overview.md) under the endpoint `/graphql`. Clients can access this API using a JWT access token in an authorization header `Authorization: Bearer <JWT>`.
+
+:::note
+Be aware a JWT token is intended to be used for M2M communication and is therefore issued for the relevant application, not for the user.
+:::
+
 **Example:**
 
 1. [Add an application in Identity](/self-managed/identity/user-guide/additional-features/incorporate-applications.md).
diff --git a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
index acedd4580f..d2f110a047 100644
--- a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
+++ b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
@@ -157,10 +157,12 @@ TaskSearchRequest - query object to search tasks by provided params.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`TaskQuery.processDefinitionId`](../../../tasklist-api/inputs/task-query.mdx#code-style-fontweight-normal-taskquerybprocessdefinitionidbcodestring-) field).
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance
+> (renamed equivalent of [`TaskQuery.processInstanceId`](../../../tasklist-api/inputs/task-query.mdx#code-style-fontweight-normal-taskquerybprocessinstanceidbcodestring-) field).
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>followUpDateDate</b></code>](#)<Bullet />[`DateFilter`](../models/date-filter-input.mdx)
 
diff --git a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
index 0ea856485c..46f1d603b4 100644
--- a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
+++ b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
@@ -90,6 +90,7 @@ FormResponse - represents task embedded form.
 #### [<code style={{ fontWeight: 'normal' }}>FormResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > Reference to process definition
+> (renamed equivalent of [`Form.processDefinitionId`](../../../tasklist-api/objects/form.mdx#code-style-fontweight-normal-formbprocessdefinitionidbcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>FormResponse.<b>schema</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
diff --git a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
index 6f565151b4..e36b7e4b5e 100644
--- a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
+++ b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
@@ -128,10 +128,12 @@ TaskResponse - represents a user task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>creationDate</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > When was the task created
+> (renamed equivalent of [`Task.creationTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcreationtimebcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>completionDate</b></code>](#)<Bullet />`string`
 
 > When was the task completed
+> (renamed equivalent of [`Task.completionTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcompletiontimebcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>assignee</b></code>](#)<Bullet />`string`
 
@@ -160,10 +162,12 @@ TaskResponse - represents a user task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`Task.processDefinitionId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessdefinitionidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance id
+> (renamed equivalent of [`Task.processInstanceId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessinstanceidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>tenantId</b></code>](#)<Bullet />`string`
 
diff --git a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
index 0e6ebac828..57fd6ce2f9 100644
--- a/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
+++ b/versioned_docs/version-8.4/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
@@ -136,10 +136,12 @@ TaskSearchResponse - representing the searched task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>creationDate</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > When was the task created
+> (renamed equivalent of [`Task.creationTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcreationtimebcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>completionDate</b></code>](#)<Bullet />`string`
 
 > When was the task completed
+> (renamed equivalent of [`Task.completionTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcompletiontimebcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>assignee</b></code>](#)<Bullet />`string`
 
@@ -164,10 +166,12 @@ TaskSearchResponse - representing the searched task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`Task.processDefinitionId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessdefinitionidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance id
+> (renamed equivalent of [`Task.processInstanceId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessinstanceidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>tenantId</b></code>](#)<Bullet />`string`
 
diff --git a/versioned_docs/version-8.4/apis-tools/working-with-apis-tools.md b/versioned_docs/version-8.4/apis-tools/working-with-apis-tools.md
index 6fb682a5ca..94a65a3cd0 100644
--- a/versioned_docs/version-8.4/apis-tools/working-with-apis-tools.md
+++ b/versioned_docs/version-8.4/apis-tools/working-with-apis-tools.md
@@ -44,6 +44,10 @@ type:"link", href:"/docs/8.4/apis-tools/java-client/", label: "Java client", doc
 }
 ]}/>
 
+:::note
+Other components in Camunda 8, such as [Tasklist API (GraphQL)](../apis-tools/tasklist-api/generated.md), provide language-agnostic APIs, but no clients to interact with them. GraphQL enables you to query, claim, and complete user tasks.
+:::
+
 ## Learn about Camunda Components and their APIs
 
 Camunda 8 components have APIs to enable polyglot developers to work with in their programming language of choice. Below are links to available component APIs.
@@ -60,6 +64,9 @@ type:"link", href:"/docs/8.4/apis-tools/operate-api/overview/", label: "Operate
 type:"link", href:"/optimize/3.12.0/apis-tools/optimize-api/optimize-api-authentication/", label: "Optimize API (REST)", description: "Get, delete, and export reports and dashboards, enable and disable sharing, and more."
 },
 {
+type:"link", href:"/docs/8.4/apis-tools/tasklist-api/tasklist-api-overview/", label: "Tasklist API (GraphQL)", docId:"apis-tools/tasklist-api/tasklist-api-overview"
+},
+{
 type:"link", href:"/docs/8.4/apis-tools/tasklist-api-rest/tasklist-api-rest-overview/", label: "Tasklist API (REST)", docId:"apis-tools/tasklist-api-rest/tasklist-api-rest-overview"
 },
 {
diff --git a/versioned_docs/version-8.4/components/best-practices/architecture/understanding-human-tasks-management.md b/versioned_docs/version-8.4/components/best-practices/architecture/understanding-human-tasks-management.md
index fc9f78c26f..ddd320592a 100644
--- a/versioned_docs/version-8.4/components/best-practices/architecture/understanding-human-tasks-management.md
+++ b/versioned_docs/version-8.4/components/best-practices/architecture/understanding-human-tasks-management.md
@@ -27,9 +27,7 @@ As a general rule, you should assign human tasks in your business process to _gr
   </bpmn:extensionElements>
 ```
 
-Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to `claimTask`.
-
-<!--- To rework. --->
+Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to [`claimTask`](../../../apis-tools/tasklist-api/mutations/claim-task.mdx).
 
 ```graphql
 claimTask(
diff --git a/versioned_docs/version-8.4/components/best-practices/development/handling-data-in-processes.md b/versioned_docs/version-8.4/components/best-practices/development/handling-data-in-processes.md
index 999cd4c4c0..28b90d2265 100644
--- a/versioned_docs/version-8.4/components/best-practices/development/handling-data-in-processes.md
+++ b/versioned_docs/version-8.4/components/best-practices/development/handling-data-in-processes.md
@@ -48,9 +48,7 @@ In Camunda 8, [values are stored as JSON](/docs/components/concepts/variables/#v
 This best practice describes variable handling within Camunda 8. Process variables are handled slightly differently with Camunda 7. Consult the [Camunda 7 documentation](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/) for details. In essence, variable values are not handled as JSON and thus there are [different values](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/#supported-variable-values) supported.
 :::
 
-You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when completing the "Review tweet" task via the API:
-
-<!--- To rework. --->
+You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when [completing](../../../apis-tools/tasklist-api/mutations/complete-task.mdx) the "Review tweet" task via the API:
 
 ```
 // TODO: Double check!
diff --git a/versioned_docs/version-8.4/components/console/manage-clusters/manage-api-clients.md b/versioned_docs/version-8.4/components/console/manage-clusters/manage-api-clients.md
index 9d0ca92d7c..8b576fa5ce 100644
--- a/versioned_docs/version-8.4/components/console/manage-clusters/manage-api-clients.md
+++ b/versioned_docs/version-8.4/components/console/manage-clusters/manage-api-clients.md
@@ -43,6 +43,7 @@ When the rate limit is triggered, the client will receive an HTTP 429 response.
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) API.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_docs/version-8.4/components/tasklist/introduction-to-tasklist.md b/versioned_docs/version-8.4/components/tasklist/introduction-to-tasklist.md
index 4e40a697e0..a899d3d613 100644
--- a/versioned_docs/version-8.4/components/tasklist/introduction-to-tasklist.md
+++ b/versioned_docs/version-8.4/components/tasklist/introduction-to-tasklist.md
@@ -10,6 +10,13 @@ With Tasklist, orchestrate human workflows critical to your business and reduce
 
 As you model a business process using BPMN and deploy it to the workflow engine, users are notified in Tasklist when they're assigned a task.
 
-Tasklist also provides a [REST API](/docs/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md).
+Tasklist provides two APIs: a [GraphQL API](/docs/apis-tools/tasklist-api/tasklist-api-overview.md)
+and a [REST API](/docs/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md). Both APIs provide equal capabilities,
+allowing you to build your own applications or use the general [UI](/docs/components/tasklist/userguide/using-tasklist.md) that we have prepared for you.
+
+:::note
+The GraphQL and REST APIs are currently available, but the GraphQL API will be deprecated in future releases, although it will still receive updates for a limited period. If you are building new applications,
+we recommend using the REST API to ensure long-term compatibility.
+:::
 
 Tasklist is also available for production use (with support) in the Camunda 8 offering. To try out Tasklist in Camunda 8, sign up [here](https://signup.camunda.com/accounts?utm_source=docs.camunda.io&utm_medium=referral).
diff --git a/versioned_docs/version-8.4/guides/setup-client-connection-credentials.md b/versioned_docs/version-8.4/guides/setup-client-connection-credentials.md
index 0a1cc40cbd..d40e88b833 100644
--- a/versioned_docs/version-8.4/guides/setup-client-connection-credentials.md
+++ b/versioned_docs/version-8.4/guides/setup-client-connection-credentials.md
@@ -15,6 +15,7 @@ Here, we'll set up client connection credentials to create, name, and connect yo
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) API.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_docs/version-8.4/self-managed/tasklist-deployment/tasklist-authentication.md b/versioned_docs/version-8.4/self-managed/tasklist-deployment/tasklist-authentication.md
index 5974026d27..f0bee0ea42 100644
--- a/versioned_docs/version-8.4/self-managed/tasklist-deployment/tasklist-authentication.md
+++ b/versioned_docs/version-8.4/self-managed/tasklist-deployment/tasklist-authentication.md
@@ -115,6 +115,14 @@ The user or user group can be assigned the following permission:
 
 For more information, visit the [Identity documentation](/self-managed/concepts/access-control/resource-authorizations.md).
 
+## Use Identity JWT token to access Tasklist API
+
+Tasklist provides a [GraphQL API](/apis-tools/tasklist-api/tasklist-api-overview.md) under the endpoint `/graphql`. Clients can access this API using a JWT access token in an authorization header `Authorization: Bearer <JWT>`.
+
+:::note
+Be aware a JWT token is intended to be used for M2M communication and is therefore issued for the relevant application, not for the user.
+:::
+
 **Example:**
 
 1. [Add an application in Identity](/self-managed/identity/user-guide/additional-features/incorporate-applications.md).
diff --git a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
index 51ab08b2fd..5a442ce8be 100644
--- a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
+++ b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
@@ -158,10 +158,12 @@ TaskSearchRequest - query object to search tasks by provided params.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`TaskQuery.processDefinitionId`](../../../tasklist-api/inputs/task-query.mdx#code-style-fontweight-normal-taskquerybprocessdefinitionidbcodestring-) field).
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance
+> (renamed equivalent of [`TaskQuery.processInstanceId`](../../../tasklist-api/inputs/task-query.mdx#code-style-fontweight-normal-taskquerybprocessinstanceidbcodestring-) field).
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>followUpDateDate</b></code>](#)<Bullet />[`DateFilter`](../models/date-filter-input.mdx)
 
diff --git a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
index 0ea856485c..46f1d603b4 100644
--- a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
+++ b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
@@ -90,6 +90,7 @@ FormResponse - represents task embedded form.
 #### [<code style={{ fontWeight: 'normal' }}>FormResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > Reference to process definition
+> (renamed equivalent of [`Form.processDefinitionId`](../../../tasklist-api/objects/form.mdx#code-style-fontweight-normal-formbprocessdefinitionidbcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>FormResponse.<b>schema</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
diff --git a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
index 6f565151b4..e36b7e4b5e 100644
--- a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
+++ b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
@@ -128,10 +128,12 @@ TaskResponse - represents a user task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>creationDate</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > When was the task created
+> (renamed equivalent of [`Task.creationTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcreationtimebcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>completionDate</b></code>](#)<Bullet />`string`
 
 > When was the task completed
+> (renamed equivalent of [`Task.completionTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcompletiontimebcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>assignee</b></code>](#)<Bullet />`string`
 
@@ -160,10 +162,12 @@ TaskResponse - represents a user task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`Task.processDefinitionId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessdefinitionidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance id
+> (renamed equivalent of [`Task.processInstanceId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessinstanceidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>tenantId</b></code>](#)<Bullet />`string`
 
diff --git a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
index 0e6ebac828..57fd6ce2f9 100644
--- a/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
+++ b/versioned_docs/version-8.5/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
@@ -136,10 +136,12 @@ TaskSearchResponse - representing the searched task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>creationDate</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > When was the task created
+> (renamed equivalent of [`Task.creationTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcreationtimebcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>completionDate</b></code>](#)<Bullet />`string`
 
 > When was the task completed
+> (renamed equivalent of [`Task.completionTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcompletiontimebcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>assignee</b></code>](#)<Bullet />`string`
 
@@ -164,10 +166,12 @@ TaskSearchResponse - representing the searched task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`Task.processDefinitionId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessdefinitionidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance id
+> (renamed equivalent of [`Task.processInstanceId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessinstanceidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>tenantId</b></code>](#)<Bullet />`string`
 
diff --git a/versioned_docs/version-8.5/apis-tools/working-with-apis-tools.md b/versioned_docs/version-8.5/apis-tools/working-with-apis-tools.md
index c0b3fab311..9ee4f2daec 100644
--- a/versioned_docs/version-8.5/apis-tools/working-with-apis-tools.md
+++ b/versioned_docs/version-8.5/apis-tools/working-with-apis-tools.md
@@ -44,6 +44,10 @@ type:"link", href:"/docs/8.5/apis-tools/java-client/", label: "Java client", doc
 }
 ]}/>
 
+:::note
+Other components in Camunda 8, such as [Tasklist API (GraphQL)](../apis-tools/tasklist-api/generated.md), provide language-agnostic APIs, but no clients to interact with them. GraphQL enables you to query, claim, and complete user tasks.
+:::
+
 ## Learn about Camunda Components and their APIs
 
 Camunda 8 components have APIs to enable polyglot developers to work with in their programming language of choice. Below are links to available component APIs.
diff --git a/versioned_docs/version-8.5/components/best-practices/architecture/understanding-human-tasks-management.md b/versioned_docs/version-8.5/components/best-practices/architecture/understanding-human-tasks-management.md
index 8525de88bd..eae24bd423 100644
--- a/versioned_docs/version-8.5/components/best-practices/architecture/understanding-human-tasks-management.md
+++ b/versioned_docs/version-8.5/components/best-practices/architecture/understanding-human-tasks-management.md
@@ -27,9 +27,7 @@ As a general rule, you should assign human tasks in your business process to _gr
   </bpmn:extensionElements>
 ```
 
-Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to `claimTask`.
-
-<!--- To rework. --->
+Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to [`claimTask`](../../../apis-tools/tasklist-api/mutations/claim-task.mdx).
 
 ```graphql
 claimTask(
diff --git a/versioned_docs/version-8.5/components/best-practices/development/handling-data-in-processes.md b/versioned_docs/version-8.5/components/best-practices/development/handling-data-in-processes.md
index f939931204..9aa8fc51da 100644
--- a/versioned_docs/version-8.5/components/best-practices/development/handling-data-in-processes.md
+++ b/versioned_docs/version-8.5/components/best-practices/development/handling-data-in-processes.md
@@ -48,9 +48,7 @@ In Camunda 8, [values are stored as JSON](/components/concepts/variables.md#vari
 This best practice describes variable handling within Camunda 8. Process variables are handled slightly differently with Camunda 7. Consult the [Camunda 7 documentation](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/) for details. In essence, variable values are not handled as JSON and thus there are [different values](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/#supported-variable-values) supported.
 :::
 
-You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when completing the "Review tweet" task via the API:
-
-<!--- To rework. --->
+You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when [completing](../../../apis-tools/tasklist-api/mutations/complete-task.mdx) the "Review tweet" task via the API:
 
 ```
 // TODO: Double check!
diff --git a/versioned_docs/version-8.5/components/console/manage-clusters/manage-api-clients.md b/versioned_docs/version-8.5/components/console/manage-clusters/manage-api-clients.md
index 5a2811e31c..54b582977a 100644
--- a/versioned_docs/version-8.5/components/console/manage-clusters/manage-api-clients.md
+++ b/versioned_docs/version-8.5/components/console/manage-clusters/manage-api-clients.md
@@ -43,6 +43,7 @@ When the rate limit is triggered, the client will receive an HTTP 429 response.
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) and [REST](/apis-tools/zeebe-api-rest/zeebe-api-rest-overview.md) APIs.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_docs/version-8.5/guides/setup-client-connection-credentials.md b/versioned_docs/version-8.5/guides/setup-client-connection-credentials.md
index c554a8e435..00200bdc22 100644
--- a/versioned_docs/version-8.5/guides/setup-client-connection-credentials.md
+++ b/versioned_docs/version-8.5/guides/setup-client-connection-credentials.md
@@ -14,6 +14,7 @@ Here, we'll set up client connection credentials to create, name, and connect yo
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) and [REST](/apis-tools/zeebe-api-rest/zeebe-api-rest-overview.md) APIs.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_docs/version-8.5/self-managed/tasklist-deployment/tasklist-authentication.md b/versioned_docs/version-8.5/self-managed/tasklist-deployment/tasklist-authentication.md
index 74f43192b3..81be5e1415 100644
--- a/versioned_docs/version-8.5/self-managed/tasklist-deployment/tasklist-authentication.md
+++ b/versioned_docs/version-8.5/self-managed/tasklist-deployment/tasklist-authentication.md
@@ -115,6 +115,14 @@ The user or user group can be assigned the following permission:
 
 For more information, visit the [Identity documentation](/self-managed/concepts/access-control/resource-authorizations.md).
 
+## Use Identity JWT token to access Tasklist API
+
+Tasklist provides a [GraphQL API](/apis-tools/tasklist-api/tasklist-api-overview.md) under the endpoint `/graphql`. Clients can access this API using a JWT access token in an authorization header `Authorization: Bearer <JWT>`.
+
+:::note
+Be aware a JWT token is intended to be used for M2M communication and is therefore issued for the relevant application, not for the user.
+:::
+
 **Example:**
 
 1. [Add an application in Identity](/self-managed/identity/user-guide/additional-features/incorporate-applications.md).
diff --git a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
index aa1c71de9a..28a31a7dd8 100644
--- a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
+++ b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/requests/task-search-request.mdx
@@ -161,10 +161,12 @@ TaskSearchRequest - query object to search tasks by provided params.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`TaskQuery.processDefinitionId`](../../../tasklist-api/inputs/task-query.mdx#code-style-fontweight-normal-taskquerybprocessdefinitionidbcodestring-) field).
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance
+> (renamed equivalent of [`TaskQuery.processInstanceId`](../../../tasklist-api/inputs/task-query.mdx#code-style-fontweight-normal-taskquerybprocessinstanceidbcodestring-) field).
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchRequest.<b>followUpDateDate</b></code>](#)<Bullet />[`DateFilter`](../models/date-filter-input.mdx)
 
diff --git a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
index 0ea856485c..46f1d603b4 100644
--- a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
+++ b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/form-response.mdx
@@ -90,6 +90,7 @@ FormResponse - represents task embedded form.
 #### [<code style={{ fontWeight: 'normal' }}>FormResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > Reference to process definition
+> (renamed equivalent of [`Form.processDefinitionId`](../../../tasklist-api/objects/form.mdx#code-style-fontweight-normal-formbprocessdefinitionidbcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>FormResponse.<b>schema</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
diff --git a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
index 3ff8b5298f..7a2c8ac4a8 100644
--- a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
+++ b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-response.mdx
@@ -128,10 +128,12 @@ TaskResponse - represents a user task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>creationDate</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > When was the task created
+> (renamed equivalent of [`Task.creationTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcreationtimebcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>completionDate</b></code>](#)<Bullet />`string`
 
 > When was the task completed
+> (renamed equivalent of [`Task.completionTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcompletiontimebcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>assignee</b></code>](#)<Bullet />`string`
 
@@ -160,10 +162,12 @@ TaskResponse - represents a user task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`Task.processDefinitionId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessdefinitionidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance id
+> (renamed equivalent of [`Task.processInstanceId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessinstanceidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskResponse.<b>tenantId</b></code>](#)<Bullet />`string`
 
diff --git a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
index 4938cb8957..b466ec5783 100644
--- a/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
+++ b/versioned_docs/version-8.6/apis-tools/tasklist-api-rest/schemas/responses/task-search-response.mdx
@@ -138,10 +138,12 @@ TaskSearchResponse - representing the searched task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>creationDate</b></code>](#)<Bullet />`string` <Badge class="secondary" text="non-null"/>
 
 > When was the task created
+> (renamed equivalent of [`Task.creationTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcreationtimebcodestring--) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>completionDate</b></code>](#)<Bullet />`string`
 
 > When was the task completed
+> (renamed equivalent of [`Task.completionTime`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbcompletiontimebcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>assignee</b></code>](#)<Bullet />`string`
 
@@ -166,10 +168,12 @@ TaskSearchResponse - representing the searched task.
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>processDefinitionKey</b></code>](#)<Bullet />`string`
 
 > Reference to process definition
+> (renamed equivalent of [`Task.processDefinitionId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessdefinitionidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>processInstanceKey</b></code>](#)<Bullet />`string`
 
 > Reference to process instance id
+> (renamed equivalent of [`Task.processInstanceId`](../../../tasklist-api/objects/task.mdx#code-style-fontweight-normal-taskbprocessinstanceidbcodestring-) field)
 
 #### [<code style={{ fontWeight: 'normal' }}>TaskSearchResponse.<b>tenantId</b></code>](#)<Bullet />`string`
 
diff --git a/versioned_docs/version-8.6/apis-tools/working-with-apis-tools.md b/versioned_docs/version-8.6/apis-tools/working-with-apis-tools.md
index d2d07d404b..766d9a434e 100644
--- a/versioned_docs/version-8.6/apis-tools/working-with-apis-tools.md
+++ b/versioned_docs/version-8.6/apis-tools/working-with-apis-tools.md
@@ -38,6 +38,10 @@ Official clients have been developed and tested by Camunda. They also add conven
 <DocCardList items={[{type:"link", href:"/docs/apis-tools/java-client/", label: "Java client", docId:"apis-tools/java-client/index"}
 ]}/>
 
+:::note
+Other components in Camunda 8, such as [Tasklist API (GraphQL)](../apis-tools/tasklist-api/generated.md), provide language-agnostic APIs, but no clients to interact with them. GraphQL enables you to query, claim, and complete user tasks.
+:::
+
 ## Learn about Camunda Components and their APIs
 
 Camunda 8 components have APIs to enable polyglot developers to work with in their programming language of choice. Below are links to available component APIs.
diff --git a/versioned_docs/version-8.6/components/best-practices/architecture/understanding-human-tasks-management.md b/versioned_docs/version-8.6/components/best-practices/architecture/understanding-human-tasks-management.md
index 2e012d0c8b..a2edbfae66 100644
--- a/versioned_docs/version-8.6/components/best-practices/architecture/understanding-human-tasks-management.md
+++ b/versioned_docs/version-8.6/components/best-practices/architecture/understanding-human-tasks-management.md
@@ -27,9 +27,7 @@ As a general rule, you should assign human tasks, like [user tasks](/components/
   </bpmn:extensionElements>
 ```
 
-Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to `claimTask`.
-
-<!--- To rework. --->
+Then, require individual members of that group to explicitly _claim tasks_ before working on them. This way, you avoid different people working on the same task at the same time. Refer to [`claimTask`](../../../apis-tools/tasklist-api/mutations/claim-task.mdx).
 
 ```graphql
 claimTask(
diff --git a/versioned_docs/version-8.6/components/best-practices/development/handling-data-in-processes.md b/versioned_docs/version-8.6/components/best-practices/development/handling-data-in-processes.md
index f939931204..9aa8fc51da 100644
--- a/versioned_docs/version-8.6/components/best-practices/development/handling-data-in-processes.md
+++ b/versioned_docs/version-8.6/components/best-practices/development/handling-data-in-processes.md
@@ -48,9 +48,7 @@ In Camunda 8, [values are stored as JSON](/components/concepts/variables.md#vari
 This best practice describes variable handling within Camunda 8. Process variables are handled slightly differently with Camunda 7. Consult the [Camunda 7 documentation](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/) for details. In essence, variable values are not handled as JSON and thus there are [different values](https://docs.camunda.org/manual/latest/user-guide/process-engine/variables/#supported-variable-values) supported.
 :::
 
-You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when completing the "Review tweet" task via the API:
-
-<!--- To rework. --->
+You can dynamically create such variables by assigning an object of choice to a (string typed) variable name; for example, by passing a `Map<String, Object>` when [completing](../../../apis-tools/tasklist-api/mutations/complete-task.mdx) the "Review tweet" task via the API:
 
 ```
 // TODO: Double check!
diff --git a/versioned_docs/version-8.6/components/console/manage-clusters/manage-api-clients.md b/versioned_docs/version-8.6/components/console/manage-clusters/manage-api-clients.md
index 818d3930ff..bd1c4de41e 100644
--- a/versioned_docs/version-8.6/components/console/manage-clusters/manage-api-clients.md
+++ b/versioned_docs/version-8.6/components/console/manage-clusters/manage-api-clients.md
@@ -43,6 +43,7 @@ When the rate limit is triggered, the client will receive an HTTP 429 response.
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) and [REST](/apis-tools/zeebe-api-rest/zeebe-api-rest-overview.md) APIs.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_docs/version-8.6/guides/setup-client-connection-credentials.md b/versioned_docs/version-8.6/guides/setup-client-connection-credentials.md
index c554a8e435..00200bdc22 100644
--- a/versioned_docs/version-8.6/guides/setup-client-connection-credentials.md
+++ b/versioned_docs/version-8.6/guides/setup-client-connection-credentials.md
@@ -14,6 +14,7 @@ Here, we'll set up client connection credentials to create, name, and connect yo
 Currently, Camunda 8 SaaS supports the following scopes:
 
 - Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) and [REST](/apis-tools/zeebe-api-rest/zeebe-api-rest-overview.md) APIs.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
 - Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
 - Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
 - Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
diff --git a/versioned_sidebars/version-8.3-sidebars.json b/versioned_sidebars/version-8.3-sidebars.json
index 6b1a88ca77..e7e04ad51b 100644
--- a/versioned_sidebars/version-8.3-sidebars.json
+++ b/versioned_sidebars/version-8.3-sidebars.json
@@ -859,6 +859,14 @@
             }
           ]
         },
+        {
+          "Tasklist API (GraphQL)": [
+            {
+              "type": "autogenerated",
+              "dirName": "apis-tools/tasklist-api"
+            }
+          ]
+        },
         {
           "Tasklist API (REST)": [
             {
diff --git a/versioned_sidebars/version-8.4-sidebars.json b/versioned_sidebars/version-8.4-sidebars.json
index 8cbd5fc1a1..777319f96e 100644
--- a/versioned_sidebars/version-8.4-sidebars.json
+++ b/versioned_sidebars/version-8.4-sidebars.json
@@ -1066,6 +1066,14 @@
             }
           ]
         },
+        {
+          "Tasklist API (GraphQL)": [
+            {
+              "type": "autogenerated",
+              "dirName": "apis-tools/tasklist-api"
+            }
+          ]
+        },
         {
           "Tasklist API (REST)": [
             "apis-tools/tasklist-api-rest/tasklist-api-rest-overview",
diff --git a/versioned_sidebars/version-8.5-sidebars.json b/versioned_sidebars/version-8.5-sidebars.json
index 423ecfb92a..380d8c1729 100644
--- a/versioned_sidebars/version-8.5-sidebars.json
+++ b/versioned_sidebars/version-8.5-sidebars.json
@@ -1238,6 +1238,18 @@
               ]
             }
           ]
+        },
+        {
+          "Deprecated": [
+            {
+              "Tasklist API (GraphQL)": [
+                {
+                  "type": "autogenerated",
+                  "dirName": "apis-tools/tasklist-api"
+                }
+              ]
+            }
+          ]
         }
       ]
     },
diff --git a/versioned_sidebars/version-8.6-sidebars.json b/versioned_sidebars/version-8.6-sidebars.json
index e25ed05c26..66f10535b8 100644
--- a/versioned_sidebars/version-8.6-sidebars.json
+++ b/versioned_sidebars/version-8.6-sidebars.json
@@ -1613,6 +1613,14 @@
         },
         {
           "Deprecated": [
+            {
+              "Tasklist API (GraphQL)": [
+                {
+                  "type": "autogenerated",
+                  "dirName": "apis-tools/tasklist-api"
+                }
+              ]
+            },
             {
               "Zeebe API (REST)": [
                 "apis-tools/zeebe-api-rest/zeebe-api-rest-overview",