@bpmnkit/camunda-docspack 0.0.0

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.modify-process-instance.api.md

@@ -0,0 +1,36 @@
+# Modify process instance
+
+`POST /process-instances/{processInstanceKey}/modification`
+
+Modifies a running process instance.
+This request can contain multiple instructions to activate an element of the process or
+to terminate an active instance of an element.
+
+Use this to repair a process instance that is stuck on an element or took an unintended path.
+For example, because an external system is not available or doesn't respond as expected.
+
+- Required permissions: MODIFY_PROCESS_INSTANCE on PROCESS_DEFINITION.
+- Added in Camunda 8.6.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  processInstanceKey (path, string, required)
+
+Request body:
+  application/json: ProcessInstanceModificationInstruction (required)
+    operationReference (OperationReference)
+    activateInstructions (ProcessInstanceModificationActivateInstruction[]) — Instructions describing which elements to activate in which scopes and which variables to create or update.
+    moveInstructions (ProcessInstanceModificationMoveInstruction[]) — Instructions describing which elements to move from one scope to another.
+    terminateInstructions (ProcessInstanceModificationTerminateInstruction[]) — Instructions describing which elements to terminate.
+
+Responses:
+  204 — The process instance is modified.
+  400 ProblemDetail — The provided data is not valid.
+  404 ProblemDetail — The process instance is not found.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/modify-process-instance.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.modify-process-instances-batch-operation.api.md

@@ -0,0 +1,31 @@
+# Modify process instances (batch)
+
+`POST /process-instances/modification`
+
+Modify multiple process instances.
+Since only process instances with ACTIVE state can be modified, any given
+filters for state are ignored and overridden during this batch operation.
+In contrast to single modification operation, it is not possible to add variable instructions or modify by element key.
+It is only possible to use the element id of the source and target.
+This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}).
+
+- Added in Camunda 8.8.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: ProcessInstanceModificationBatchOperationRequest (required)
+    filter (ProcessInstanceFilter, required) — The process instance filter.
+    moveInstructions (ProcessInstanceModificationMoveBatchOperationInstruction[], required) — Instructions for moving tokens between elements.
+    operationReference (OperationReference)
+
+Responses:
+  200 BatchOperationCreatedResult — The batch operation request was created.
+  400 ProblemDetail — The process instance batch operation failed. More details are provided in the response body.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/modify-process-instances-batch-operation.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.pause-exporting.api.md

@@ -0,0 +1,30 @@
+# Pause exporting
+
+`POST /exporting/pause`
+
+Pauses exporting on all partitions of the physical tenant. While paused, exported records
+are not committed, so the log is not compacted for the affected partitions.
+
+With `soft=true`, exporting continues to run but its position is not committed, so the
+state after resuming is identical to a hard pause; use this variant when exporting must
+keep progressing (e.g. to avoid falling behind) while still preventing log compaction,
+such as during a backup.
+
+- Required permissions: PAUSE on EXPORTER.
+- Added in Camunda 8.10.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  soft (query, boolean)
+
+Responses:
+  204 — Exporting was successfully paused.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/pause-exporting.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.pin-clock.api.md

@@ -0,0 +1,31 @@
+# Pin internal clock (alpha)
+
+`PUT /clock`
+
+Set a precise, static time for the Zeebe engine's internal clock.
+When the clock is pinned, it remains at the specified time and does not advance.
+To change the time, the clock must be pinned again with a new timestamp.
+
+:::note
+This endpoint is an [alpha feature](/components/early-access/alpha/alpha-features.md) and may be subject to change
+in future releases.
+:::
+
+- Required permissions: UPDATE on SYSTEM.
+- Added in Camunda 8.6.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: ClockPinRequest (required)
+    timestamp (integer, required) — The exact time in epoch milliseconds to which the clock should be pinned.
+
+Responses:
+  204 — The clock was successfully pinned.
+  400 ProblemDetail — The provided data is not valid.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/pin-clock.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.publish-message.api.md

@@ -0,0 +1,34 @@
+# Publish message
+
+`POST /messages/publication`
+
+Publishes a single message.
+Messages are published to specific partitions computed from their correlation keys.
+Messages can be buffered.
+The endpoint does not wait for a correlation result.
+Use the message correlation endpoint for such use cases.
+
+- Required permissions: CREATE on MESSAGE.
+- Added in Camunda 8.6.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: MessagePublicationRequest (required)
+    name (string, required) — The name of the message.
+    correlationKey (string) — The correlation key of the message.
+    timeToLive (integer) — Timespan (in ms) to buffer the message on the broker.
+    messageId (string) — The unique ID of the message. This is used to ensure only one message with the given ID will be published during the lifetime of the message (if `timeToLive`…
+    variables (object) — The message variables as JSON document.
+    tenantId (TenantId) — The tenant of the message sender.
+    businessId (BusinessId) — An optional business id used to enforce uniqueness of the process instance that a message start event would create. If provided and uniqueness enforcement is…
+
+Responses:
+  200 MessagePublicationResult — The message was published.
+  400 ProblemDetail — The provided data is not valid.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/publish-message.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.reset-clock.api.md

@@ -0,0 +1,26 @@
+# Reset internal clock (alpha)
+
+`POST /clock/reset`
+
+Resets the Zeebe engine's internal clock to the current system time, enabling it to tick in real-time.
+This operation is useful for returning the clock to
+normal behavior after it has been pinned to a specific time.
+
+:::note
+This endpoint is an [alpha feature](/components/early-access/alpha/alpha-features.md) and may be subject to change
+in future releases.
+:::
+
+- Required permissions: UPDATE on SYSTEM.
+- Added in Camunda 8.6.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Responses:
+  204 — The clock was successfully reset to the system time.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/reset-clock.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resolve-incident.api.md

@@ -0,0 +1,30 @@
+# Resolve incident
+
+`POST /incidents/{incidentKey}/resolution`
+
+Marks the incident as resolved; most likely a call to Update job will be necessary
+to reset the job's retries, followed by this call.
+
+- Required permissions: UPDATE_PROCESS_INSTANCE on PROCESS_DEFINITION.
+- Added in Camunda 8.6.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  incidentKey (path, string, required)
+
+Request body:
+  application/json: IncidentResolutionRequest
+    operationReference (OperationReference)
+
+Responses:
+  204 — The incident is marked as resolved.
+  400 ProblemDetail — The provided data is not valid.
+  404 ProblemDetail — The incident with the incidentKey is not found.
+  409 ProblemDetail — The incident cannot be resolved due to an invalid state. For example, the associated job may have no retries left.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resolve-incident.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resolve-incidents-batch-operation.api.md

@@ -0,0 +1,28 @@
+# Resolve related incidents (batch)
+
+`POST /process-instances/incident-resolution`
+
+Resolves multiple instances of process instances.
+Since only process instances with ACTIVE state can have unresolved incidents, any given
+filters for state are ignored and overridden during this batch operation.
+This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}).
+
+- Added in Camunda 8.8.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: ProcessInstanceIncidentResolutionBatchOperationRequest
+    filter (ProcessInstanceFilter, required) — The process instance filter.
+    operationReference (OperationReference)
+
+Responses:
+  200 BatchOperationCreatedResult — The batch operation request was created.
+  400 ProblemDetail — The process instance batch operation failed. More details are provided in the response body.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resolve-incidents-batch-operation.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resolve-process-instance-incidents.api.md

@@ -0,0 +1,25 @@
+# Resolve related incidents
+
+`POST /process-instances/{processInstanceKey}/incident-resolution`
+
+Creates a batch operation to resolve multiple incidents of a process instance.
+
+- Required permissions: UPDATE_PROCESS_INSTANCE on PROCESS_DEFINITION.
+- Added in Camunda 8.9.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  processInstanceKey (path, string, required)
+
+Responses:
+  200 BatchOperationCreatedResult — The batch operation request for incident resolution was created.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  404 ProblemDetail — The process instance is not found.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resolve-process-instance-incidents.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resolve-secrets.api.md

@@ -0,0 +1,39 @@
+# Resolve secrets (alpha)
+
+`POST /secrets/resolve`
+
+Resolve a deduplicated batch of `camunda.secrets.*` references for the caller's
+physical tenant in a single round-trip.
+
+Each reference is authorized and resolved independently. For valid requests, the endpoint
+always responds with HTTP 200: successfully resolved references are returned in `resolved`,
+while references that could not be resolved (for example not found, malformed or over-long,
+or the caller lacks `SECRET:REVEAL` on that reference) are returned in `errors`. A failure of
+one reference never fails the others. Only structurally invalid requests are rejected with
+HTTP 400: a missing or non-array `references` field, more than 20 references, or a null entry.
+
+References are resolved against the secret stores configured for the caller's physical
+tenant, served from the gateway's secret cache when the value is already cached and read
+from the store otherwise.
+
+This endpoint is an [alpha feature](/components/early-access/alpha/alpha-features.md) and may be subject to change in future releases.
+
+- Required permissions: REVEAL on SECRET.
+- Added in Camunda 8.10.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: SecretResolveRequest (required)
+    references (string[], required) — The secret references to resolve, each of the form `camunda.secrets.<name>`. Duplicate references are deduplicated by the server and resolved once. At most 20…
+
+Responses:
+  200 SecretResolveResult — The batch was processed. Per-reference outcomes are split between `resolved` and `errors`; this status is returned even when some or all references failed.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resolve-secrets.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.restore-as-cluster-admin.api.md

@@ -0,0 +1,35 @@
+# Restore one or every physical tenant from a backup
+
+`POST /cluster/v2/restore`
+
+Restores physical tenants from backups. The restore is described either by a list of backup IDs or by a time range (`from`/`to`) that selects the backups to restore. Restores are only accepted while the targeted physical tenants are in recovery mode; requests are rejected otherwise. The request is validated and acknowledged, but the restore itself is performed asynchronously.
+
+If the `physicalTenantId` parameter is provided, only that physical tenant is restored and `overrides` must be omitted.
+
+If it is not provided, every physical tenant of the cluster is restored: those named in `overrides` with their own backup selection, all others with the selection at the top level of the request body.
+
+Requires the cluster-admin security chain. Although this operation lists `bearerAuth` / `basicAuth` like the rest of the Orchestration Cluster API, it does not accept an Orchestration Cluster user's credentials — only the separate cluster-admin credentials are valid here.
+
+- Added in Camunda 8.10.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  physicalTenantId (query, string)
+  dryRun (query, boolean)
+
+Request body:
+  application/json: ClusterRestoreRequest (required)
+    overrides (object) — The backup selection to apply to individual physical tenants, keyed by physical tenant id. Only allowed for a cluster-wide restore, that is when no…
+
+Responses:
+  202 ClusterRestoreResponse — The restore request was accepted; returns the planned cluster change covering every requested physical tenant.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  404 ProblemDetail — The requested `physicalTenantId`, or a physical tenant named in `overrides`, does not exist in this cluster.
+  409 — A targeted physical tenant is not in recovery mode, so the restore cannot be accepted.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/restore-as-cluster-admin.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.restore.api.md

@@ -0,0 +1,31 @@
+# Restore from a backup
+
+`POST /restore`
+
+Restores the cluster from a backup. The restore is described either by a single backup ID or by a time range (`from`/`to`) that selects the backups to restore. This endpoint is only accessible while the cluster is in recovery mode; requests are rejected otherwise. The request is validated and acknowledged, but the restore itself is performed asynchronously.
+
+- Required permissions: RESTORE on BACKUP.
+- Added in Camunda 8.10.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  dryRun (query, boolean)
+
+Request body:
+  application/json: RestoreRequest (required)
+    from (string) — The start of the time range to restore from, as an ISO 8601 timestamp.
+    to (string) — The end of the time range to restore from, as an ISO 8601 timestamp.
+    backupIds (integer[]) — The IDs of the backups to restore from, one per partition.
+
+Responses:
+  202 ClusterRestoreResponse — The restore request was accepted; returns the planned cluster changes.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  409 — The cluster is not in recovery mode, so the restore cannot be accepted.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/restore.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resume-batch-operation.api.md

@@ -0,0 +1,29 @@
+# Resume Batch operation
+
+`POST /batch-operations/{batchOperationKey}/resumption`
+
+Resumes a suspended batch operation.
+This is done asynchronously, the progress can be tracked using the batch operation status endpoint (/batch-operations/{batchOperationKey}).
+
+- Required permissions: UPDATE on BATCH.
+- Added in Camunda 8.8.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  batchOperationKey (path, BatchOperationKey, required)
+
+Request body:
+  application/json: 
+
+Responses:
+  204 — The batch operation resume request was created.
+  400 ProblemDetail — The provided data is not valid.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  404 ProblemDetail — Not found. The batch operation was not found.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resume-batch-operation.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resume-exporting.api.md

@@ -0,0 +1,21 @@
+# Resume exporting
+
+`POST /exporting/resume`
+
+Resumes exporting on all partitions of the physical tenant after a pause or soft pause.
+
+- Required permissions: PAUSE on EXPORTER.
+- Added in Camunda 8.10.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Responses:
+  204 — Exporting was successfully resumed.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resume-exporting.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resume-process-instance.api.md

@@ -0,0 +1,30 @@
+# Resume process instance
+
+`POST /process-instances/{processInstanceKey}/resumption`
+
+Resumes a suspended process instance, returning it to the ACTIVE state and continuing processing.
+Only process instances in the SUSPENDED state can be resumed.
+
+- Required permissions: SUSPEND_PROCESS_INSTANCE on PROCESS_DEFINITION.
+- Added in Camunda 8.10.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  processInstanceKey (path, string, required)
+
+Request body:
+  application/json: ResumeProcessInstanceRequest
+    operationReference (OperationReference)
+
+Responses:
+  204 — The process instance is resumed.
+  400 ProblemDetail — The provided data is not valid.
+  404 ProblemDetail — The process instance is not found.
+  409 ProblemDetail — The process instance is not in the SUSPENDED state and cannot be resumed. More details are provided in the response body.
+  500 ProblemDetail — An internal error occurred while processing the request.
+  503 ProblemDetail — The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains `RESOURCE_EXHAUSTED`. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resume-process-instance.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.resume-process-instances-batch-operation.api.md

@@ -0,0 +1,28 @@
+# Resume process instances (batch)
+
+`POST /process-instances/resumption`
+
+Resumes multiple suspended process instances.
+Since only SUSPENDED root instances can be resumed, any given
+filters for state and parentProcessInstanceKey are ignored and overridden during this batch operation.
+This is done asynchronously, the progress can be tracked using the batchOperationKey from the response and the batch operation status endpoint (/batch-operations/{batchOperationKey}).
+
+- Added in Camunda 8.10.
+- Consistency: strong.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: ProcessInstanceResumptionBatchOperationRequest (required)
+    filter (ProcessInstanceFilter, required) — The process instance filter.
+    operationReference (OperationReference)
+
+Responses:
+  200 BatchOperationCreatedResult — The batch operation request was created.
+  400 ProblemDetail — The process instance batch operation failed. More details are provided in the response body.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/resume-process-instances-batch-operation.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.search-agent-definitions.api.md

@@ -0,0 +1,26 @@
+# Search agent definitions
+
+`POST /agent-definitions/search`
+
+Search for agent definitions based on given criteria.
+
+- Required permissions: READ_PROCESS_DEFINITION on PROCESS_DEFINITION.
+- Added in Camunda 8.10.
+- Consistency: eventual.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: AgentDefinitionSearchQuery
+    sort (AgentDefinitionSearchQuerySortRequest[]) — Sort field criteria.
+    filter (AgentDefinitionFilter) — The agent definition search filters.
+
+Responses:
+  200 AgentDefinitionSearchQueryResult — The agent definition search result.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/search-agent-definitions.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.search-agent-instance-history.api.md

@@ -0,0 +1,31 @@
+# Search agent instance history
+
+`POST /agent-instances/{agentInstanceKey}/history/search`
+
+Searches the conversation history of an agent instance. Committed items
+are returned by default.
+
+- Required permissions: READ_PROCESS_INSTANCE on PROCESS_DEFINITION.
+- Added in Camunda 8.10.
+- Consistency: eventual.
+
+Authentication: bearerAuth or basicAuth
+
+Parameters:
+  agentInstanceKey (path, string, required)
+
+Request body:
+  application/json: AgentInstanceHistorySearchQuery
+    sort (AgentInstanceHistorySearchQuerySortRequest[]) — Sort field criteria.
+    filter (AgentInstanceHistoryFilter) — The history item search filters.
+
+Responses:
+  200 AgentInstanceHistorySearchQueryResult — The agent instance history search result.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  404 ProblemDetail — The agent instance with the given key was not found. More details are provided in the response body.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/search-agent-instance-history.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.search-agent-instances.api.md

@@ -0,0 +1,26 @@
+# Search agent instances
+
+`POST /agent-instances/search`
+
+Search for agent instances based on given criteria.
+
+- Required permissions: READ_PROCESS_INSTANCE on PROCESS_DEFINITION.
+- Added in Camunda 8.10.
+- Consistency: eventual.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: AgentInstanceSearchQuery
+    sort (AgentInstanceSearchQuerySortRequest[]) — Sort field criteria.
+    filter (AgentInstanceFilter) — The agent instance search filters.
+
+Responses:
+  200 AgentInstanceSearchQueryResult — The agent instance search result.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/search-agent-instances.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.search-audit-logs.api.md

@@ -0,0 +1,26 @@
+# Search audit logs
+
+`POST /audit-logs/search`
+
+Search for audit logs based on given criteria.
+
+- Required permissions: READ on AUDIT_LOG.
+- Added in Camunda 8.9.
+- Consistency: eventual.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: AuditLogSearchQueryRequest
+    sort (AuditLogSearchQuerySortRequest[]) — Sort field criteria.
+    filter (AuditLogFilter) — The audit log search filters.
+
+Responses:
+  200 AuditLogSearchQueryResult — The audit logs search result.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/search-audit-logs.api

package/.llms/chunks/apis-tools.orchestration-cluster-api-rest.specifications.search-authorizations.api.md

@@ -0,0 +1,26 @@
+# Search authorizations
+
+`POST /authorizations/search`
+
+Search for authorizations based on given criteria.
+
+- Required permissions: READ on AUTHORIZATION.
+- Added in Camunda 8.8.
+- Consistency: eventual.
+
+Authentication: bearerAuth or basicAuth
+
+Request body:
+  application/json: AuthorizationSearchQuery
+    sort (AuthorizationSearchQuerySortRequest[]) — Sort field criteria.
+    filter (AuthorizationFilter) — The authorization search filters.
+
+Responses:
+  200 AuthorizationSearchResult — The authorization search result.
+  400 ProblemDetail — The provided data is not valid.
+  401 ProblemDetail — The request lacks valid authentication credentials.
+  403 ProblemDetail — Forbidden. The request is not allowed.
+  500 ProblemDetail — An internal error occurred while processing the request.
+
+---
+Source: https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/search-authorizations.api