> ## 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 details that fulfill the given parameters. Takes the same parameters as the [Get Historic Details](https://docs.camunda.org/manual/7.22/reference/rest/history/detail/get-detail-query/) method. ## OpenAPI ````yaml GET /history/detail/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/detail/count: get: tags: - Historic Detail summary: Get Historic Detail Count description: >- Queries for the number of historic details that fulfill the given parameters. Takes the same parameters as the [Get Historic Details](https://docs.camunda.org/manual/7.22/reference/rest/history/detail/get-detail-query/) method. operationId: getHistoricDetailsCount parameters: - name: processInstanceId in: query schema: type: string description: Filter by process instance id. - name: processInstanceIdIn in: query schema: type: string description: >- Only include historic details which belong to one of the passed comma-separated process instance ids. - name: executionId in: query schema: type: string description: Filter by execution id. - name: taskId in: query schema: type: string description: Filter by task id. - name: activityInstanceId in: query schema: type: string description: Filter by activity instance id. - name: caseInstanceId in: query schema: type: string description: Filter by case instance id. - name: caseExecutionId in: query schema: type: string description: Filter by case execution id. - name: variableInstanceId in: query schema: type: string description: Filter by variable instance id. - name: variableTypeIn in: query schema: type: string description: >- Only include historic details where the variable updates belong to one of the passed comma-separated list of variable types. A list of all supported variable types can be found [here](https://docs.camunda.org/manual/7.22/user-guide/process-engine/variables/#supported-variable-values). **Note:** All non-primitive variables are associated with the type `serializable`. - name: variableNameLike in: query schema: type: string description: >- Filter by variable name like. Example usage: `variableNameLike(%camunda%)`. The query will match the names of variables in a case-insensitive way. - name: tenantIdIn in: query schema: type: string description: Filter by a comma-separated list of tenant ids. - name: withoutTenantId in: query schema: type: boolean description: >- Only include historic details that belong to no tenant. Value may only be `true`, as `false` is the default behavior. - name: userOperationId in: query schema: type: string description: Filter by a user operation id. - name: formFields in: query schema: type: boolean description: >- Only include `HistoricFormFields`. Value may only be `true`, as `false` is the default behavior. - name: variableUpdates in: query schema: type: boolean description: >- Only include `HistoricVariableUpdates`. Value may only be `true`, as `false` is the default behavior. - name: excludeTaskDetails in: query schema: type: boolean description: >- Excludes all task-related `HistoricDetails`, so only items which have no task id set will be selected. When this parameter is used together with `taskId`, this call is ignored and task details are not excluded. Value may only be `true`, as `false` is the default behavior. - name: initial in: query schema: type: boolean description: >- Restrict to historic variable updates that contain only initial variable values. Value may only be `true`, as `false` is the default behavior. - name: occurredBefore in: query schema: type: string format: date-time description: >- Restrict to historic details that occured before the given date (including the date). Default [format](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/) `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., 2013-01-23T14:42:45.000+0200. - name: occurredAfter in: query schema: type: string format: date-time description: >- Restrict to historic details that occured after the given date (including the date). Default [format](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/) `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., 2013-01-23T14:42:45.000+0200. responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: GET `/history/detail/count?variableName=my_variable` description: GET `/history/detail/count?variableName=my_variable` value: count: 3 description: Request successful. '400': content: application/json: schema: $ref: '#/components/schemas/ExceptionDto' description: Returned if some of the query parameters are invalid. 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 ````