> ## 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. # 获取计数 > Requests the number of decision requirements definitions that fulfill the query criteria. Takes the same filtering parameters as the [Get Decision Requirements Definitions](https://docs.camunda.org/manual/7.22/reference/rest/decision-requirements-definition/get-query/) method. ## OpenAPI ````yaml GET /decision-requirements-definition/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: /decision-requirements-definition/count: get: tags: - Decision Requirements Definition summary: Get Decision Requirements Definition Count description: >- Requests the number of decision requirements definitions that fulfill the query criteria. Takes the same filtering parameters as the [Get Decision Requirements Definitions](https://docs.camunda.org/manual/7.22/reference/rest/decision-requirements-definition/get-query/) method. operationId: getDecisionRequirementsDefinitionsCount parameters: - name: decisionRequirementsDefinitionId in: query schema: type: string description: Filter by decision requirements definition id. - name: decisionRequirementsDefinitionIdIn in: query schema: type: string description: Filter by decision requirements definition ids. - name: name in: query schema: type: string description: Filter by decision requirements definition name. - name: nameLike in: query schema: type: string description: >- Filter by decision requirements definition names that the parameter is a substring of. - name: deploymentId in: query schema: type: string description: >- Filter by the id of the deployment a decision requirement definition belongs to. - name: key in: query schema: type: string description: >- Filter by decision requirements definition key, i.e., the id in the DMN 1.3 XML. Exact match. - name: keyLike in: query schema: type: string description: >- Filter by decision requirements definition keys that the parameter is a substring of. - name: category in: query schema: type: string description: Filter by decision requirements definition category. Exact match. - name: categoryLike in: query schema: type: string description: >- Filter by decision requirements definition categories that the parameter is a substring of. - name: version in: query schema: type: integer format: int32 description: Filter by decision requirements definition version. - name: latestVersion in: query schema: type: boolean description: >- Only include those decision requirements definitions that are latest versions. Value may only be `true`, as `false` is the default behavior. - name: resourceName in: query schema: type: string description: >- Filter by the name of the decision requirements definition resource. Exact match. - name: resourceNameLike in: query schema: type: string description: >- Filter by names of those decision requirements definition resources that the parameter is a substring of. - name: tenantIdIn in: query schema: type: string description: >- Filter by a comma-separated list of tenant ids. A decision requirements definition must have one of the given tenant ids. - name: withoutTenantId in: query schema: type: boolean description: >- Only include decision requirements definitions which belong to no tenant. Value may only be `true`, as `false` is the default behavior. - name: includeDecisionRequirementsDefinitionsWithoutTenantId in: query schema: type: boolean description: >- Include decision requirements definitions which belong to no tenant. Can be used in combination with `tenantIdIn`. 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 `/decision-requirements-definition/count?key=dish` description: GET `/decision-requirements-definition/count?key=dish` 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, for example if a `sortOrder` parameter is supplied, but no `sortBy`. 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 ````