> ## 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. # 获取计数 > Queries for the number of historic tasks that fulfill the given parameters. Takes the same parameters as the [Get Tasks (Historic)](https://docs.camunda.org/manual/7.22/reference/rest/history/task/get-task-query/) method. ## OpenAPI ````yaml GET /history/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: /history/task/count: get: tags: - Historic Task Instance summary: Get Task Count description: >- Queries for the number of historic tasks that fulfill the given parameters. Takes the same parameters as the [Get Tasks (Historic)](https://docs.camunda.org/manual/7.22/reference/rest/history/task/get-task-query/) method. operationId: getHistoricTaskInstancesCount parameters: - name: taskId in: query schema: type: string description: Filter by task id. - name: taskParentTaskId in: query schema: type: string description: Filter by parent task id. - name: processInstanceId in: query schema: type: string description: Filter by process instance id. - name: rootProcessInstanceId in: query schema: type: string description: Filter by root process instance id. - name: processInstanceBusinessKey in: query schema: type: string description: Filter by process instance business key. - name: processInstanceBusinessKeyIn in: query schema: type: string description: |- Filter by 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: >- Filter by process instance business key that has the parameter value as a substring. - name: executionId in: query schema: type: string description: Filter by the id of the execution that executed the task. - name: processDefinitionId in: query schema: type: string description: Filter by process definition id. - name: processDefinitionKey in: query schema: type: string description: >- Restrict to tasks that belong to a process definition with the given key. - name: processDefinitionName in: query schema: type: string description: >- Restrict to tasks that belong to a process definition with the given name. - name: caseInstanceId in: query schema: type: string description: Filter by case instance id. - name: caseExecutionId in: query schema: type: string description: Filter by the id of the case execution that executed the task. - name: caseDefinitionId in: query schema: type: string description: Filter by case definition 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: activityInstanceIdIn in: query schema: type: string description: >- Only include tasks which belong to one of the passed comma-separated activity instance ids. - name: taskName in: query schema: type: string description: Restrict to tasks that have the given name. - name: taskNameLike in: query schema: type: string description: >- Restrict to tasks that have a name with the given parameter value as substring. - name: taskDescription in: query schema: type: string description: Restrict to tasks that have the given description. - name: taskDescriptionLike in: query schema: type: string description: >- Restrict to tasks that have a description that has the parameter value as a substring. - 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 passed comma-separated task definition keys. - name: taskDeleteReason in: query schema: type: string description: Restrict to tasks that have the given delete reason. - name: taskDeleteReasonLike in: query schema: type: string description: >- Restrict to tasks that have a delete reason that has the parameter value as a substring. - name: taskAssignee in: query schema: type: string description: Restrict to tasks that the given user is assigned to. - name: taskAssigneeLike in: query schema: type: string description: >- Restrict to tasks that are assigned to users with the parameter value as a substring. - name: taskOwner in: query schema: type: string description: Restrict to tasks that the given user owns. - name: taskOwnerLike in: query schema: type: string description: >- Restrict to tasks that are owned by users with the parameter value as a substring. - name: taskPriority in: query schema: type: integer format: int32 description: Restrict to tasks that have the given priority. - name: assigned in: query schema: type: boolean description: >- If set to `true`, restricts the query to all tasks that are assigned. - name: unassigned in: query schema: type: boolean description: >- If set to `true`, restricts the query to all tasks that are unassigned. - name: finished in: query schema: type: boolean description: >- Only include finished tasks. Value may only be `true`, as `false` is the default behavior. - name: unfinished in: query schema: type: boolean description: >- Only include unfinished tasks. Value may only be `true`, as `false` is the default behavior. - name: processFinished in: query schema: type: boolean description: >- Only include tasks of finished processes. Value may only be `true`, as `false` is the default behavior. - name: processUnfinished in: query schema: type: boolean description: >- Only include tasks of unfinished processes. Value may only be `true`, as `false` is the default behavior. - name: taskDueDate in: query schema: type: string format: date-time 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.000+0200`. - name: taskDueDateBefore in: query schema: type: string format: date-time 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.000+0200`. - name: taskDueDateAfter in: query schema: type: string format: date-time 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.000+0200`. - name: withoutTaskDueDate in: query schema: type: boolean description: >- Only include tasks which have no due date. Value may only be `true`, as `false` is the default behavior. - name: taskFollowUpDate in: query schema: type: string format: date-time 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.000+0200`. - name: taskFollowUpDateBefore in: query schema: type: string format: date-time 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.000+0200`. - name: taskFollowUpDateAfter in: query schema: type: string format: date-time 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.000+0200`. - name: startedBefore in: query schema: type: string format: date-time description: >- Restrict to tasks that were started 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.000+0200`. - name: startedAfter in: query schema: type: string format: date-time description: >- Restrict to tasks that were started 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.000+0200`. - name: finishedBefore in: query schema: type: string format: date-time description: >- Restrict to tasks that were finished 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.000+0200`. - name: finishedAfter in: query schema: type: string format: date-time description: >- Restrict to tasks that were finished 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.000+0200`. - name: tenantIdIn in: query schema: type: string description: >- Filter by a comma-separated list of tenant ids. A task instance must have one of the given tenant ids. - name: withoutTenantId in: query schema: type: boolean description: >- Only include historic task instances that belong to no tenant. 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: variableNamesIgnoreCase in: query schema: type: boolean description: >- Match the variable name provided in `taskVariables` and `processVariables` case- insensitively. If set to `true` **variableName** and **variablename** are treated as equal. - name: variableValuesIgnoreCase in: query schema: type: boolean description: >- Match the variable value provided in `taskVariables` and `processVariables` case- insensitively. If set to `true` **variableValue** and **variablevalue** are treated as equal. - name: taskInvolvedUser in: query schema: type: string description: Restrict to tasks with a historic identity link to the given user. - name: taskInvolvedGroup in: query schema: type: string description: Restrict to tasks with a historic identity link to the given group. - name: taskHadCandidateUser in: query schema: type: string description: >- Restrict to tasks with a historic identity link to the given candidate user. - name: taskHadCandidateGroup in: query schema: type: string description: >- Restrict to tasks with a historic identity link to the given candidate group. - name: withCandidateGroups in: query schema: 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: type: boolean description: >- Only include tasks which have no candidate group. Value may only be `true`, as `false` is the default behavior. responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: >- GET `/history/task/count?taskAssginee=anAssignee&taskPriority=50` description: >- GET `/history/task/count?taskAssginee=anAssignee&taskPriority=50` 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 ````