> ## 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 batches that fulfill the query criteria.
Takes the same filtering parameters as the [Get Batches](https://docs.camunda.org/manual/7.22/reference/rest/batch/get-query/) method.



## OpenAPI

````yaml GET /batch/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:
  /batch/count:
    get:
      tags:
        - Batch
      summary: Get List Count
      description: >-
        Requests the number of batches that fulfill the query criteria.

        Takes the same filtering parameters as the [Get
        Batches](https://docs.camunda.org/manual/7.22/reference/rest/batch/get-query/)
        method.
      operationId: getBatchesCount
      parameters:
        - name: batchId
          in: query
          schema:
            type: string
          description: Filter by batch id.
        - name: type
          in: query
          schema:
            type: string
          description: >-
            Filter by batch type.

            See the [User
            Guide](https://docs.camunda.org/manual/7.22/user-guide/process-engine/batch/#creating-a-batch)

            for more information about batch types.
        - name: tenantIdIn
          in: query
          schema:
            type: string
          description: >-
            Filter by a comma-separated list of `Strings`. A batch matches if it
            has one of the given tenant ids.
        - name: withoutTenantId
          in: query
          schema:
            type: boolean
          description: >-
            Only include batches which belong to no tenant.

            Value can effectively only be `true`, as `false` is the default
            behavior.
        - name: suspended
          in: query
          schema:
            type: boolean
          description: >-
            A `Boolean` value which indicates whether only active or suspended
            batches should be included.

            When the value is set to `true`, only suspended batches will be
            returned and

            when the value is set to `false`, only active batches will be
            returned.
        - name: createdBy
          in: query
          schema:
            type: string
          description: Only include batches that were started by this user id.
        - name: startedBefore
          in: query
          schema:
            type: string
            format: date-time
          description: >-
            Only include batches that were started 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: startedAfter
          in: query
          schema:
            type: string
            format: date-time
          description: >-
            Only include batches that were started 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: withFailures
          in: query
          schema:
            type: boolean
          description: |-
            Only include batches having jobs with failures.
            Value can only be `true`.
        - name: withoutFailures
          in: query
          schema:
            type: boolean
          description: |-
            Only include batches having jobs without failures.
            Value can only be `true`.
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CountResultDto'
              examples:
                example-1:
                  summary: Status 200 response
                  description: Response for GET `/batch/count?type=aBatchType`
                  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

````