> ## 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 incidents that fulfill the given parameters. Takes the same parameters as the [Get Incidents](https://docs.camunda.org/manual/7.22/reference/rest/history/incident/get-incident-query/) method. ## OpenAPI ````yaml GET /history/incident/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/incident/count: get: tags: - Historic Incident summary: Get Incident Count description: >- Queries for the number of historic incidents that fulfill the given parameters. Takes the same parameters as the [Get Incidents](https://docs.camunda.org/manual/7.22/reference/rest/history/incident/get-incident-query/) method. operationId: getHistoricIncidentsCount parameters: - name: incidentId in: query schema: type: string description: Restricts to incidents that have the given id. - name: incidentType in: query schema: type: string description: >- Restricts to incidents that belong to the given incident type. See the [User Guide](/manual/develop/user-guide/process-engine/incidents/#incident-types) for a list of incident types. - name: incidentMessage in: query schema: type: string description: Restricts to incidents that have the given incident message. - name: incidentMessageLike in: query schema: type: string description: > Restricts to incidents that incidents message is a substring of the given value. The string can include the wildcard character '%' to express like-strategy: starts with (string%), ends with (%string) or contains (%string%). - name: processDefinitionId in: query schema: type: string description: >- Restricts to incidents that belong to a process definition with the given id. - name: processDefinitionKey in: query schema: type: string description: Restricts to incidents that have the given processDefinitionKey. - name: processDefinitionKeyIn in: query schema: type: string description: >- Restricts to incidents that have one of the given process definition keys. - name: processInstanceId in: query schema: type: string description: >- Restricts to incidents that belong to a process instance with the given id. - name: executionId in: query schema: type: string description: >- Restricts to incidents that belong to an execution with the given id. - name: createTimeBefore in: query schema: type: string format: date-time description: >- Restricts to incidents that have a createTime date before the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.000+0200`. - name: createTimeAfter in: query schema: type: string format: date-time description: >- Restricts to incidents that have a createTime date after the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.000+0200`. - name: endTimeBefore in: query schema: type: string format: date-time description: >- Restricts to incidents that have an endTimeBefore date before the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.000+0200`. - name: endTimeAfter in: query schema: type: string format: date-time description: >- Restricts to incidents that have an endTimeAfter date after the given date. By [default](https://docs.camunda.org/manual/7.22/reference/rest/overview/date-format/), the date must have the format `yyyy-MM-dd'T'HH:mm:ss.SSSZ`, e.g., `2013-01-23T14:42:45.000+0200`. - name: activityId in: query schema: type: string description: Restricts to incidents that belong to an activity with the given id. - name: failedActivityId in: query schema: type: string description: >- Restricts to incidents that were created due to the failure of an activity with the given id. - name: causeIncidentId in: query schema: type: string description: >- Restricts to incidents that have the given incident id as cause incident. - name: rootCauseIncidentId in: query schema: type: string description: >- Restricts to incidents that have the given incident id as root cause incident. - name: configuration in: query schema: type: string description: >- Restricts to incidents that have the given parameter set as configuration. - name: historyConfiguration in: query schema: type: string description: >- Restricts to incidents that have the given parameter set as history configuration. - name: open in: query schema: type: boolean description: Restricts to incidents that are open. - name: resolved in: query schema: type: boolean description: Restricts to incidents that are resolved. - name: deleted in: query schema: type: boolean description: Restricts to incidents that are deleted. - name: tenantIdIn in: query schema: type: string description: >- Restricts to incidents that have one of the given comma-separated tenant ids. - name: withoutTenantId in: query schema: type: boolean description: >- Only include historic incidents that belong to no tenant. Value may only be `true`, as `false` is the default behavior. - name: jobDefinitionIdIn in: query schema: type: string description: >- Restricts to incidents that have one of the given comma-separated job definition ids. responses: '200': content: application/json: schema: $ref: '#/components/schemas/CountResultDto' examples: example-1: summary: GET `/history/incident/count?processInstanceId=aProcInstId` description: GET `/history/incident/count?processInstanceId=aProcInstId` value: count: 2 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 ````