> ## 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 user operation log entries that fulfill the given parameters. Takes the same parameters as the [Get User Operation Log (Historic)](https://docs.camunda.org/manual/7.22/reference/rest/history/user-operation-log/get-user-operation-log-query/) method. ## OpenAPI ````yaml GET /history/user-operation/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/user-operation/count: get: tags: - Historic User Operation Log summary: Get User Operation Log Count description: >- Queries for the number of user operation log entries that fulfill the given parameters. Takes the same parameters as the [Get User Operation Log (Historic)](https://docs.camunda.org/manual/7.22/reference/rest/history/user-operation-log/get-user-operation-log-query/) method. operationId: queryUserOperationCount parameters: - name: deploymentId in: query schema: type: string description: Filter by deployment id. - name: processDefinitionId in: query schema: type: string description: Filter by process definition id. - name: processDefinitionKey in: query schema: type: string description: Filter by process definition key. - name: processInstanceId in: query schema: type: string description: Filter by process instance id. - name: executionId in: query schema: type: string description: Filter by execution id. - name: caseDefinitionId in: query schema: type: string description: Filter by case definition 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: taskId in: query schema: type: string description: Only include operations on this task. - name: externalTaskId in: query schema: type: string description: Only include operations on this external task. - name: batchId in: query schema: type: string description: Only include operations on this batch. - name: jobId in: query schema: type: string description: Filter by job id. - name: jobDefinitionId in: query schema: type: string description: Filter by job definition id. - name: userId in: query schema: type: string description: Only include operations of this user. - name: operationId in: query schema: type: string description: >- Filter by the id of the operation. This allows fetching of multiple entries which are part of a composite operation. - name: operationType in: query schema: type: string description: >- Filter by the type of the operation like `Claim` or `Delegate`. See the [Javadoc](https://docs.camunda.org/manual/7.22/reference/javadoc/?org/camunda/bpm/engine/history/UserOperationLogEntry.html) for a list of available operation types. - name: entityType in: query schema: type: string description: >- Filter by the type of the entity that was affected by this operation, possible values are `Task`, `Attachment` or `IdentityLink`. - name: entityTypeIn in: query schema: type: string description: >- Filter by a comma-separated list of types of the entities that was affected by this operation, possible values are `Task`, `Attachment` or `IdentityLink`. - name: category in: query schema: type: string description: >- Filter by the category that this operation is associated with, possible values are `TaskWorker`, `Admin` or `Operator`. - name: categoryIn in: query schema: type: string description: >- Filter by a comma-separated list of categories that this operation is associated with, possible values are `TaskWorker`, `Admin` or `Operator`. - name: property in: query schema: type: string description: >- Only include operations that changed this property, e.g., `owner` or `assignee`. - name: afterTimestamp in: query schema: type: string format: date-time description: >- Restrict to entries that were created after the given timestamp. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the timestamp must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., 2013-01-23T14:42:45.000+0200. - name: beforeTimestamp in: query schema: type: string format: date-time description: >- Restrict to entries that were created before the given timestamp. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the timestamp must have the 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/user-operation?operationType=Claim&userId=demo` description: >- GET `/history/user-operation?operationType=Claim&userId=demo` 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 ````