> ## 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 variable instances that fulfill the given parameters. Takes the same parameters as the [Get Variable Instances](https://docs.camunda.org/manual/7.22/reference/rest/history/variable-instance/get-variable-instance-query/) method. ## OpenAPI ````yaml GET /history/variable-instance/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/variable-instance/count: get: tags: - Historic Variable Instance summary: Get Variable Instance Count description: >- Queries for the number of historic variable instances that fulfill the given parameters. Takes the same parameters as the [Get Variable Instances](https://docs.camunda.org/manual/7.22/reference/rest/history/variable-instance/get-variable-instance-query/) method. operationId: getHistoricVariableInstancesCount parameters: - name: variableName in: query schema: type: string description: Filter by variable name. - name: variableNameLike in: query schema: type: string description: Restrict to variables with a name like the parameter. - name: variableValue in: query schema: type: object description: >- Filter by variable value. Is treated as a `String` object on server side. - name: variableNamesIgnoreCase in: query schema: type: boolean description: >- Match the variable name provided in `variableName` and `variableNameLike` 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 `variableValue` case-insensitively. If set to `true` **variableValue** and **variablevalue** are treated as equal. - name: variableTypeIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and comma- separated 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: includeDeleted in: query schema: type: boolean description: >- Include variables that has already been deleted during the execution. - name: processInstanceId in: query schema: type: string description: Filter by the process instance the variable belongs to. - name: processInstanceIdIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and comma-separated process instance ids. - name: processDefinitionId in: query schema: type: string description: Filter by the process definition the variable belongs to. - name: processDefinitionKey in: query schema: type: string description: Filter by a key of the process definition the variable belongs to. - name: executionIdIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and and comma-separated execution ids. - name: caseInstanceId in: query schema: type: string description: Filter by the case instance the variable belongs to. - name: caseExecutionIdIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and and comma-separated case execution ids. - name: caseActivityIdIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and and comma-separated case activity ids. - name: taskIdIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and and comma-separated task ids. - name: activityInstanceIdIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and and comma-separated activity instance ids. - name: tenantIdIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and comma- separated tenant ids. - name: withoutTenantId in: query schema: type: boolean description: >- Only include historic variable instances that belong to no tenant. Value may only be `true`, as `false` is the default behavior. - name: variableNameIn in: query schema: type: string description: >- Only include historic variable instances which belong to one of the passed and comma-separated variable names. responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: >- GET `/history/variable-instance/count?variableName=my_variable` description: >- GET `/history/variable-instance/count?variableName=my_variable` 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 ````