> ## 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. # 获取计数(POST) > Queries for historic variable instances that fulfill the given parameters. This method takes the same message body as the [Get Variable Instances (POST)](https://docs.camunda.org/manual/7.22/reference/rest/history/variable-instance/post-variable-instance-query/) method and therefore it is more powerful regarding variable values than the [Get Variable Instance Count](https://docs.camunda.org/manual/7.22/reference/rest/history/variable-instance/get-variable-instance-query-count/) method. ## OpenAPI ````yaml POST /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: post: tags: - Historic Variable Instance summary: Get Variable Instance Count (POST) description: >- Queries for historic variable instances that fulfill the given parameters. This method takes the same message body as the [Get Variable Instances (POST)](https://docs.camunda.org/manual/7.22/reference/rest/history/variable-instance/post-variable-instance-query/) method and therefore it is more powerful regarding variable values than the [Get Variable Instance Count](https://docs.camunda.org/manual/7.22/reference/rest/history/variable-instance/get-variable-instance-query-count/) method. operationId: queryHistoricVariableInstancesCount requestBody: content: application/json: schema: $ref: '#/components/schemas/HistoricVariableInstanceQueryDto' examples: example-1: summary: POST `/history/variable-instance/count` value: variableName: someVariable variableValue: 42 responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: POST `/history/variable-instance/count` description: POST `/history/variable-instance/count` 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: HistoricVariableInstanceQueryDto: type: object description: >- A Historic Variable Instance instance query which defines a list of Historic Variable Instance instances properties: variableName: type: string nullable: true description: Filter by variable name. variableNameLike: type: string nullable: true description: Restrict to variables with a name like the parameter. variableValue: type: object description: Filter by variable value. May be `String`, `Number` or `Boolean`. variableNamesIgnoreCase: type: boolean nullable: true description: >- Match the variable name provided in `variableName` and `variableNameLike` case- insensitively. If set to `true` **variableName** and **variablename** are treated as equal. variableValuesIgnoreCase: type: boolean nullable: true description: >- Match the variable value provided in `variableValue` case-insensitively. If set to `true` **variableValue** and **variablevalue** are treated as equal. variableTypeIn: type: array nullable: true items: 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'. includeDeleted: type: boolean nullable: true description: >- Include variables that has already been deleted during the execution. processInstanceId: type: string nullable: true description: Filter by the process instance the variable belongs to. processInstanceIdIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed process instance ids. processDefinitionId: type: string nullable: true description: Filter by the process definition the variable belongs to. processDefinitionKey: type: string nullable: true description: Filter by a key of the process definition the variable belongs to. executionIdIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed and execution ids. caseInstanceId: type: string nullable: true description: Filter by the case instance the variable belongs to. caseExecutionIdIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed and case execution ids. caseActivityIdIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed and case activity ids. taskIdIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed and task ids. activityInstanceIdIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed and activity instance ids. tenantIdIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed and comma- separated tenant ids. withoutTenantId: type: boolean nullable: true description: >- Only include historic variable instances that belong to no tenant. Value may only be `true`, as `false` is the default behavior. variableNameIn: type: array nullable: true items: type: string description: >- Only include historic variable instances which belong to one of the passed variable names. sorting: type: array nullable: true description: >- An array of criteria to sort the result by. Each element of the array is an object that specifies one ordering. The position in the array identifies the rank of an ordering, i.e., whether it is primary, secondary, etc. Sorting has no effect for `count` endpoints items: type: object properties: sortBy: type: string nullable: true enum: - instanceId - variableName - tenantId description: |- Sort the results lexicographically by a given criterion. Must be used in conjunction with the sortOrder parameter. sortOrder: type: string nullable: true enum: - asc - desc description: >- Sort the results in a given order. Values may be `asc` for ascending order or `desc` for descending order. Must be used in conjunction with the sortBy parameter. 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 ````