> ## 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 external tasks that fulfill given parameters. Takes the same parameters as the
[Get External Tasks](https://docs.camunda.org/manual/7.22/reference/rest/external-task/get-query/) method.



## OpenAPI

````yaml GET /external-task/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:
  /external-task/count:
    get:
      tags:
        - External Task
      summary: Get List Count
      description: >-
        Queries for the number of external tasks that fulfill given parameters.
        Takes the same parameters as the

        [Get External
        Tasks](https://docs.camunda.org/manual/7.22/reference/rest/external-task/get-query/)
        method.
      operationId: getExternalTasksCount
      parameters:
        - name: externalTaskId
          in: query
          schema:
            type: string
          description: Filter by an external task's id.
        - name: externalTaskIdIn
          in: query
          schema:
            type: string
          description: Filter by the comma-separated list of external task ids.
        - name: topicName
          in: query
          schema:
            type: string
          description: Filter by an external task topic.
        - name: workerId
          in: query
          schema:
            type: string
          description: >-
            Filter by the id of the worker that the task was most recently
            locked by.
        - name: locked
          in: query
          schema:
            type: boolean
          description: >-
            Only include external tasks that are currently locked (i.e., they
            have a lock time and it has not expired).

            Value may only be `true`, as `false` matches any external task.
        - name: notLocked
          in: query
          schema:
            type: boolean
          description: >-
            Only include external tasks that are currently not locked (i.e.,
            they have no lock or it has expired).

            Value may only be `true`, as `false` matches any external task.
        - name: withRetriesLeft
          in: query
          schema:
            type: boolean
          description: >-
            Only include external tasks that have a positive (&gt; 0) number of
            retries (or `null`). Value may only be

            `true`, as `false` matches any external task.
        - name: noRetriesLeft
          in: query
          schema:
            type: boolean
          description: >-
            Only include external tasks that have 0 retries. Value may only be
            `true`, as `false` matches any

            external task.
        - name: lockExpirationAfter
          in: query
          schema:
            type: string
            format: date-time
          description: >-
            Restrict to external tasks that have a lock that expires after a
            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: lockExpirationBefore
          in: query
          schema:
            type: string
            format: date-time
          description: >-
            Restrict to external tasks that have a lock that expires before a
            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: >-
            Filter by the id of the activity that an external task is created
            for.
        - name: activityIdIn
          in: query
          schema:
            type: string
          description: >-
            Filter by the comma-separated list of ids of the activities that an
            external task is created for.
        - name: executionId
          in: query
          schema:
            type: string
          description: Filter by the id of the execution that an external task belongs to.
        - name: processInstanceId
          in: query
          schema:
            type: string
          description: >-
            Filter by the id of the process instance that an external task
            belongs to.
        - name: processInstanceIdIn
          in: query
          schema:
            type: string
          description: >-
            Filter by a comma-separated list of process instance ids that an
            external task may belong to.
        - name: processDefinitionId
          in: query
          schema:
            type: string
          description: >-
            Filter by the id of the process definition that an external task
            belongs to.
        - name: tenantIdIn
          in: query
          schema:
            type: string
          description: |-
            Filter by a comma-separated list of tenant ids.
            An external task must have one of the given tenant ids.
        - name: active
          in: query
          schema:
            type: boolean
          description: >-
            Only include active tasks. Value may only be `true`, as `false`
            matches any external task.
        - name: suspended
          in: query
          schema:
            type: boolean
          description: >-
            Only include suspended tasks. Value may only be `true`, as `false`
            matches any external task.
        - name: priorityHigherThanOrEquals
          in: query
          schema:
            type: integer
            format: int64
          description: >-
            Only include jobs with a priority higher than or equal to the given
            value.

            Value must be a valid `long` value.
        - name: priorityLowerThanOrEquals
          in: query
          schema:
            type: integer
            format: int64
          description: >-
            Only include jobs with a priority lower than or equal to the given
            value.

            Value must be a valid `long` value.
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CountResultDto'
              examples:
                example-1:
                  summary: GET /external-task/count?topicName=aTopic
                  value:
                    count: 42
          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

````