> ## 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) > Query for the number of variable instances that fulfill given parameters. This method takes the same message body as the [Get Variable Instances POST](https://docs.camunda.org/manual/7.22/reference/rest/variable- instance/post-query/) method and therefore it is slightly more powerful than the [Get Variable Instance Count](https://docs.camunda.org/manual/7.22/reference/rest/variable-instance/get-query-count/) method. ## OpenAPI ````yaml POST /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: /variable-instance/count: post: tags: - Variable Instance summary: Get Variable Instance Count (POST) description: >- Query for the number of variable instances that fulfill given parameters. This method takes the same message body as the [Get Variable Instances POST](https://docs.camunda.org/manual/7.22/reference/rest/variable- instance/post-query/) method and therefore it is slightly more powerful than the [Get Variable Instance Count](https://docs.camunda.org/manual/7.22/reference/rest/variable-instance/get-query-count/) method. operationId: queryVariableInstancesCount requestBody: content: application/json: schema: $ref: '#/components/schemas/VariableInstanceQueryDto' examples: example-1: summary: POST `/variable-instance/count` value: variableValues: - name: amount operator: gteq value: '5' - name: amount operator: lteq value: 200 processInstanceIdIn: - aProcessInstanceId - anotherProcessInstanceId responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: description: POST `/variable-instance/count` 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, for example if an invalid operator for variable comparison is used. See the [Introduction](https://docs.camunda.org/manual/7.22/reference/rest/overview/#error-handling) for the error response format. components: schemas: VariableInstanceQueryDto: type: object description: A variable instance query which defines a list of variable instances properties: variableName: type: string nullable: true description: Filter by variable instance name. variableNameLike: type: string nullable: true description: >- Filter by the variable instance name. The parameter can include the wildcard `%` to express like-strategy such as: starts with (`%`name), ends with (name`%`) or contains (`%`name`%`). processInstanceIdIn: type: array nullable: true items: type: string description: |- Only include variable instances which belong to one of the passed process instance ids. executionIdIn: type: array nullable: true items: type: string description: |- Only include variable instances which belong to one of the passed execution ids. caseInstanceIdIn: type: array nullable: true items: type: string description: >- Only include variable instances which belong to one of the passed case instance ids. caseExecutionIdIn: type: array nullable: true items: type: string description: >- Only include variable instances which belong to one of the passed case execution ids. taskIdIn: type: array nullable: true items: type: string description: >- Only include variable instances which belong to one of the passed task ids. batchIdIn: type: array nullable: true items: type: string description: |- Only include variable instances which belong to one of the passed batch ids. activityInstanceIdIn: type: array nullable: true items: type: string description: |- Only include variable instances which belong to one of the passed activity instance ids. tenantIdIn: type: array nullable: true items: type: string description: |- Only include variable instances which belong to one of the passed tenant ids. variableValues: type: array nullable: true items: $ref: '#/components/schemas/VariableQueryParameterDto' description: >- An array to only include variable instances that have the certain values. The array consists of objects with the three properties `name`, `operator` and `value`. `name (String)` is the variable name, `operator (String)` is the comparison operator to be used and `value` the variable value. `value` may be `String`, `Number` or `Boolean`. 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` variableNamesIgnoreCase: type: boolean nullable: true description: >- Match all variable names provided in `variableValues` case-insensitively. If set to `true` **variableName** and **variablename** are treated as equal. variableValuesIgnoreCase: type: boolean nullable: true description: >- Match all variable values provided in `variableValues` case-insensitively. If set to `true` **variableValue** and **variablevalue** are treated as equal. variableScopeIdIn: type: array nullable: true items: type: string description: >- Only include variable instances which belong to one of passed scope ids. 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: - variableName - variableType - activityInstanceId - 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). VariableQueryParameterDto: allOf: - type: object properties: name: type: string nullable: true description: Variable name - $ref: '#/components/schemas/ConditionQueryParameterDto' ConditionQueryParameterDto: type: object properties: operator: type: string nullable: true enum: - eq - neq - gt - gteq - lt - lteq - like - notLike description: >- Comparison operator to be used. `notLike` is not supported by all endpoints. value: $ref: '#/components/schemas/AnyValue' AnyValue: description: |- Can be any value - string, number, boolean, array or object. **Note**: Not every endpoint supports every type. securitySchemes: basicAuth: type: http scheme: basic ````