> ## Documentation Index > Fetch the complete documentation index at: https://docs.eorion.com/llms.txt > Use this file to discover all available pages before exploring further. # 获取计数 > Retrieves the number of tasks that fulfill a provided filter. Corresponds to the size of the result set when using the [Get Tasks](https://docs.camunda.org/manual/7.22/reference/rest/task/) method. **Security Consideration:** There are several query parameters (such as assigneeExpression) for specifying an EL expression. These are disabled by default to prevent remote code execution. See the section on [security considerations](https://docs.camunda.org/manual/7.22/user-guide/process-engine/securing-custom-code/) for custom code in the user guide for details. ## OpenAPI ````yaml GET /task/count openapi: 3.0.2 info: title: ORION Platform REST API description: OpenApi Spec for ORION Camunda Platform REST API. version: 7.22.6-ee license: name: Apache License 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: http://{host}:{port}/{contextPath} description: The API server for the default process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest - url: http://{host}:{port}/{contextPath}/engine/{engineName} description: The API server for a named process engine variables: host: default: localhost port: default: '8080' contextPath: default: engine-rest engineName: default: default - url: '{url}' description: The API server with a custom url variables: url: default: '' security: - basicAuth: [] tags: - name: Authorization - name: Batch - name: Condition - name: Decision Definition - name: Decision Requirements Definition - name: Deployment - name: Engine - name: Event Subscription - name: Execution - name: External Task - name: Filter - name: Group - name: Historic Activity Instance - name: Historic Batch - name: Historic Decision Definition - name: Historic Decision Instance - name: Historic Decision Requirements Definition - name: Historic Detail - name: Historic External Task Log - name: Historic Identity Link Log - name: Historic Incident - name: Historic Job Log - name: Historic Process Definition - name: Historic Process Instance - name: Historic Task Instance - name: Historic User Operation Log - name: Historic Variable Instance - name: History Cleanup - name: Identity - name: Incident - name: Job - name: Job Definition - name: Message - name: Metrics - name: Migration - name: Modification - name: Process Definition - name: Process Instance - name: Signal - name: Schema Log - name: Task - name: Task Attachment - name: Task Comment - name: Task Identity Link - name: Task Local Variable - name: Task Variable - name: Telemetry - name: Tenant - name: User - name: Variable Instance - name: Version externalDocs: description: Find out more about ORION Rest API url: https://docs.eorion.com paths: /task/count: get: tags: - Task summary: Get List Count description: >- Retrieves the number of tasks that fulfill a provided filter. Corresponds to the size of the result set when using the [Get Tasks](https://docs.camunda.org/manual/7.22/reference/rest/task/) method. **Security Consideration:** There are several query parameters (such as assigneeExpression) for specifying an EL expression. These are disabled by default to prevent remote code execution. See the section on [security considerations](https://docs.camunda.org/manual/7.22/user-guide/process-engine/securing-custom-code/) for custom code in the user guide for details. operationId: getTasksCount parameters: - name: taskId in: query schema: type: string description: Restrict to task with the given id. - name: taskIdIn in: query schema: type: string description: Restrict to tasks with any of the given ids. - name: processInstanceId in: query schema: type: string description: >- Restrict to tasks that belong to process instances with the given id. - name: processInstanceIdIn in: query schema: type: string description: >- Restrict to tasks that belong to process instances with the given ids. - name: processInstanceBusinessKey in: query schema: type: string description: >- Restrict to tasks that belong to process instances with the given business key. - name: processInstanceBusinessKeyExpression in: query schema: type: string description: >- Restrict to tasks that belong to process instances with the given business key which is described by an expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: processInstanceBusinessKeyIn in: query schema: type: string description: >- Restrict to tasks that belong to process instances with one of the give business keys. The keys need to be in a comma-separated list. - name: processInstanceBusinessKeyLike in: query schema: type: string description: >- Restrict to tasks that have a process instance business key that has the parameter value as a substring. - name: processInstanceBusinessKeyLikeExpression in: query schema: type: string description: >- Restrict to tasks that have a process instance business key that has the parameter value as a substring and is described by an expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: processDefinitionId in: query schema: type: string description: >- Restrict to tasks that belong to a process definition with the given id. - name: processDefinitionKey in: query schema: type: string description: >- Restrict to tasks that belong to a process definition with the given key. - name: processDefinitionKeyIn in: query schema: type: string description: >- Restrict to tasks that belong to a process definition with one of the given keys. The keys need to be in a comma-separated list. - name: processDefinitionName in: query schema: type: string description: >- Restrict to tasks that belong to a process definition with the given name. - name: processDefinitionNameLike in: query schema: type: string description: >- Restrict to tasks that have a process definition name that has the parameter value as a substring. - name: executionId in: query schema: type: string description: Restrict to tasks that belong to an execution with the given id. - name: caseInstanceId in: query schema: type: string description: Restrict to tasks that belong to case instances with the given id. - name: caseInstanceBusinessKey in: query schema: type: string description: >- Restrict to tasks that belong to case instances with the given business key. - name: caseInstanceBusinessKeyLike in: query schema: type: string description: >- Restrict to tasks that have a case instance business key that has the parameter value as a substring. - name: caseDefinitionId in: query schema: type: string description: >- Restrict to tasks that belong to a case definition with the given id. - name: caseDefinitionKey in: query schema: type: string description: >- Restrict to tasks that belong to a case definition with the given key. - name: caseDefinitionName in: query schema: type: string description: >- Restrict to tasks that belong to a case definition with the given name. - name: caseDefinitionNameLike in: query schema: type: string description: >- Restrict to tasks that have a case definition name that has the parameter value as a substring. - name: caseExecutionId in: query schema: type: string description: Restrict to tasks that belong to a case execution with the given id. - name: activityInstanceIdIn in: query schema: type: string description: >- Only include tasks which belong to one of the passed and comma-separated activity instance ids. - name: tenantIdIn in: query schema: type: string description: >- Only include tasks which belong to one of the passed and comma-separated tenant ids. - name: withoutTenantId in: query schema: default: false type: boolean description: >- Only include tasks which belong to no tenant. Value may only be `true`, as `false` is the default behavior. - name: assignee in: query schema: type: string description: Restrict to tasks that the given user is assigned to. - name: assigneeExpression in: query schema: type: string description: >- Restrict to tasks that the user described by the given expression is assigned to. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: assigneeLike in: query schema: type: string description: |- Restrict to tasks that have an assignee that has the parameter value as a substring. - name: assigneeLikeExpression in: query schema: type: string description: >- Restrict to tasks that have an assignee that has the parameter value described by the given expression as a substring. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: assigneeIn in: query schema: type: string description: |- Only include tasks which are assigned to one of the passed and comma-separated user ids. - name: assigneeNotIn in: query schema: type: string description: |- Only include tasks which are not assigned to one of the passed and comma-separated user ids. - name: owner in: query schema: type: string description: Restrict to tasks that the given user owns. - name: ownerExpression in: query schema: type: string description: >- Restrict to tasks that the user described by the given expression owns. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: candidateGroup in: query schema: type: string description: Only include tasks that are offered to the given group. - name: candidateGroupLike in: query schema: type: string description: >- Only include tasks that are offered to groups that have the parameter value as a substring. - name: candidateGroupExpression in: query schema: type: string description: >- Only include tasks that are offered to the group described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: candidateUser in: query schema: type: string description: >- Only include tasks that are offered to the given user or to one of his groups. - name: candidateUserExpression in: query schema: type: string description: >- Only include tasks that are offered to the user described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: includeAssignedTasks in: query schema: default: false type: boolean description: >- Also include tasks that are assigned to users in candidate queries. Default is to only include tasks that are not assigned to any user if you query by candidate user or group(s). - name: involvedUser in: query schema: type: string description: >- Only include tasks that the given user is involved in. A user is involved in a task if an identity link exists between task and user (e.g., the user is the assignee). - name: involvedUserExpression in: query schema: type: string description: >- Only include tasks that the user described by the given expression is involved in. A user is involved in a task if an identity link exists between task and user (e.g., the user is the assignee). See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. - name: assigned in: query schema: default: false type: boolean description: >- If set to `true`, restricts the query to all tasks that are assigned. - name: unassigned in: query schema: default: false type: boolean description: >- If set to `true`, restricts the query to all tasks that are unassigned. - name: taskDefinitionKey in: query schema: type: string description: Restrict to tasks that have the given key. - name: taskDefinitionKeyIn in: query schema: type: string description: >- Restrict to tasks that have one of the given keys. The keys need to be in a comma-separated list. - name: taskDefinitionKeyLike in: query schema: type: string description: >- Restrict to tasks that have a key that has the parameter value as a substring. - name: name in: query schema: type: string description: Restrict to tasks that have the given name. - name: nameNotEqual in: query schema: type: string description: Restrict to tasks that do not have the given name. - name: nameLike in: query schema: type: string description: >- Restrict to tasks that have a name with the given parameter value as substring. - name: nameNotLike in: query schema: type: string description: |- Restrict to tasks that do not have a name with the given parameter value as substring. - name: description in: query schema: type: string description: Restrict to tasks that have the given description. - name: descriptionLike in: query schema: type: string description: |- Restrict to tasks that have a description that has the parameter value as a substring. - name: priority in: query schema: type: integer description: Restrict to tasks that have the given priority. - name: maxPriority in: query schema: type: integer description: Restrict to tasks that have a lower or equal priority. - name: minPriority in: query schema: type: integer description: Restrict to tasks that have a higher or equal priority. - name: dueDate in: query schema: type: string description: >- Restrict to tasks that are due on the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.546+0200`. - name: dueDateExpression in: query schema: type: string description: >- Restrict to tasks that are due on the date described by the given expression. See the [User Guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: dueAfter in: query schema: type: string description: >- Restrict to tasks that are due after the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.435+0200`. - name: dueAfterExpression in: query schema: type: string description: >- Restrict to tasks that are due after the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: dueBefore in: query schema: type: string description: >- Restrict to tasks that are due before the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.243+0200`. - name: dueBeforeExpression in: query schema: type: string description: >- Restrict to tasks that are due before the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: withoutDueDate in: query schema: default: false type: boolean description: >- Only include tasks which have no due date. Value may only be `true`, as `false` is the default behavior. - name: followUpDate in: query schema: type: string description: >- Restrict to tasks that have a followUp date on the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.342+0200`. - name: followUpDateExpression in: query schema: type: string description: >- Restrict to tasks that have a followUp date on the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: followUpAfter in: query schema: type: string description: >- Restrict to tasks that have a followUp date after the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.542+0200`. - name: followUpAfterExpression in: query schema: type: string description: >- Restrict to tasks that have a followUp date after the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: followUpBefore in: query schema: type: string description: >- Restrict to tasks that have a followUp date before the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.234+0200`. - name: followUpBeforeExpression in: query schema: type: string description: >- Restrict to tasks that have a followUp date before the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: followUpBeforeOrNotExistent in: query schema: type: string description: >- Restrict to tasks that have no followUp date or a followUp date before the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.432+0200`. The typical use case is to query all `active` tasks for a user for a given date. - name: followUpBeforeOrNotExistentExpression in: query schema: type: string description: >- Restrict to tasks that have no followUp date or a followUp date before the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: createdOn in: query schema: type: string description: >- Restrict to tasks that were created on the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.324+0200`. - name: createdOnExpression in: query schema: type: string description: >- Restrict to tasks that were created on the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: createdAfter in: query schema: type: string description: >- Restrict to tasks that were created after the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.342+0200`. - name: createdAfterExpression in: query schema: type: string description: >- Restrict to tasks that were created after the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: createdBefore in: query schema: type: string description: >- Restrict to tasks that were created before the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.332+0200`. - name: createdBeforeExpression in: query schema: type: string description: >- Restrict to tasks that were created before the date described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: updatedAfter in: query schema: type: string description: >- Restrict to tasks that were updated after the given date. Every action that fires a [task update event](https://docs.camunda.org/manual/7.22/user-guide/process-engine/delegation-code/#task-listener-event-lifecycle) is considered as updating the task. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.332+0200`. - name: updatedAfterExpression in: query schema: type: string description: >- Restrict to tasks that were updated after the date described by the given expression. Every action that fires a [task update event](https://docs.camunda.org/manual/7.22/user-guide/process-engine/delegation-code/#task-listener-event-lifecycle) is considered as updating the task. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to a `java.util.Date` or `org.joda.time.DateTime` object. - name: delegationState in: query schema: enum: - PENDING - RESOLVED type: string description: >- Restrict to tasks that are in the given delegation state. Valid values are `PENDING` and `RESOLVED`. - name: candidateGroups in: query schema: type: string description: >- Restrict to tasks that are offered to any of the given candidate groups. Takes a comma-separated list of group names, so for example `developers,support,sales`. - name: candidateGroupsExpression in: query schema: type: string description: >- Restrict to tasks that are offered to any of the candidate groups described by the given expression. See the [user guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/expression-language/#internal-context-functions) for more information on available functions. The expression must evaluate to `java.util.List` of Strings. - name: withCandidateGroups in: query schema: default: false type: boolean description: >- Only include tasks which have a candidate group. Value may only be `true`, as `false` is the default behavior. - name: withoutCandidateGroups in: query schema: default: false type: boolean description: >- Only include tasks which have no candidate group. Value may only be `true`, as `false` is the default behavior. - name: withCandidateUsers in: query schema: default: false type: boolean description: >- Only include tasks which have a candidate user. Value may only be `true`, as `false` is the default behavior. - name: withoutCandidateUsers in: query schema: default: false type: boolean description: >- Only include tasks which have no candidate users. Value may only be `true`, as `false` is the default behavior. - name: active in: query schema: default: false type: boolean description: |- Only include active tasks. Value may only be `true`, as `false` is the default behavior. - name: suspended in: query schema: default: false type: boolean description: |- Only include suspended tasks. Value may only be `true`, as `false` is the default behavior. - name: taskVariables in: query schema: type: string description: >- Only include tasks that have variables with certain values. Variable filtering expressions are comma-separated and are structured as follows: A valid parameter value has the form `key_operator_value`. `key` is the variable name, `operator` is the comparison operator to be used and `value` the variable value. **Note**: Values are always treated as String objects on server side. Valid `operator` values are: `eq` - equal to; `neq` - not equal to; `gt` - greater than; `gteq` - greater than or equal to; `lt` - lower than; `lteq` - lower than or equal to; `like`. `key` and `value` may not contain underscore or comma characters. - name: processVariables in: query schema: type: string description: >- Only include tasks that belong to process instances that have variables with certain values. Variable filtering expressions are comma-separated and are structured as follows: A valid parameter value has the form `key_operator_value`. `key` is the variable name, `operator` is the comparison operator to be used and `value` the variable value. **Note**: Values are always treated as String objects on server side. Valid `operator` values are: `eq` - equal to; `neq` - not equal to; `gt` - greater than; `gteq` - greater than or equal to; `lt` - lower than; `lteq` - lower than or equal to; `like`; `notLike`. `key` and `value` may not contain underscore or comma characters. - name: caseInstanceVariables in: query schema: type: string description: >- Only include tasks that belong to case instances that have variables with certain values. Variable filtering expressions are comma-separated and are structured as follows: A valid parameter value has the form `key_operator_value`. `key` is the variable name, `operator` is the comparison operator to be used and `value` the variable value. **Note**: Values are always treated as String objects on server side. Valid `operator` values are: `eq` - equal to; `neq` - not equal to; `gt` - greater than; `gteq` - greater than or equal to; `lt` - lower than; `lteq` - lower than or equal to; `like`. `key` and `value` may not contain underscore or comma characters. - name: variableNamesIgnoreCase in: query schema: default: false type: boolean description: |- Match all variable names in this query case-insensitively. If set `variableName` and `variablename` are treated as equal. - name: variableValuesIgnoreCase in: query schema: default: false type: boolean description: |- Match all variable values in this query case-insensitively. If set `variableValue` and `variablevalue` are treated as equal. - name: parentTaskId in: query schema: type: string description: >- Restrict query to all tasks that are sub tasks of the given task. Takes a task id. - name: withCommentAttachmentInfo in: query schema: default: false type: boolean description: >- Check if task has attachments and/or comments. Value may only be `true`, as `false` is the default behavior. Adding the filter will do additional attachment and comments queries to the database, it might slow down the query in case of tables having high volume of data. This param is not considered for count queries responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: Status 200 response value: count: 1 description: Request successful. '400': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: >- Returned if some of the query parameters are invalid. See the [Introduction](https://docs.camunda.org/manual/7.22/reference/rest/overview/#error-handling) for the error response format. components: schemas: CountResultDto: type: object properties: count: type: integer format: int64 description: The number of matching instances. ExceptionDto: title: ExceptionDto type: object properties: type: type: string nullable: true description: An exception class indicating the occurred error. message: type: string nullable: true description: A detailed message of the error. code: type: number description: >- The code allows your client application to identify the error in an automated fashion. You can look up the meaning of all built-in codes and learn how to add custom codes in the [User Guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/error-handling/#exception-codes). securitySchemes: basicAuth: type: http scheme: basic ````