> ## Documentation Index > Fetch the complete documentation index at: https://docs.rescan.dev/llms.txt > Use this file to discover all available pages before exploring further. # Operators by Status > Retrieves a list of operators filtered by their status, with pagination and aggregated statistics. ## OpenAPI ````yaml get /eigenda/operators-by-status openapi: 3.0.1 info: title: OpenAPI Rescan Explorer description: Api reference for the Rescan Explorer license: name: MIT version: 1.0.0 servers: - url: https://api.blockflow.network/rest security: [] paths: /eigenda/operators-by-status: get: summary: Operators by Status description: >- Retrieves a list of operators filtered by their status, with pagination and aggregated statistics. parameters: - name: network in: query schema: type: string enum: - ethereum - holesky default: holesky required: true description: Select the network you want to track. - name: status in: query required: true schema: type: boolean enum: - true - false default: true description: The status of the operators to filter by. - name: page in: query required: false schema: type: integer default: 1 minimum: 1 description: The page number for pagination. - name: limit in: query required: false schema: type: integer default: 12 minimum: 1 description: The number of items per page for pagination. responses: '200': description: >- Successful response containing operators data with metadata and statistics. content: application/json: schema: type: object properties: data: type: array items: type: object properties: operatorId: type: string description: The unique ID of the operator. operator: type: string description: The operator's name or identifier. socket: type: string description: The socket associated with the operator. status: type: string description: The status of the operator. ejected: type: boolean description: Indicates if the operator has been ejected. quorumStakes: type: array items: type: object properties: quorumNumber: type: string description: >- The quorum number associated with the operator. stake: type: string description: >- The stake amount of the operator in the quorum. description: A list of quorum-related stakes for the operator. totalStake: type: number description: The total stake of the operator across all quorums. description: The list of operators matching the query parameters. meta: type: object properties: total: type: integer description: The total number of operators matching the status. status: type: string description: The status filter applied to the operators. page: type: integer description: The current page number. limit: type: integer description: The number of items per page. totalPages: type: integer description: The total number of pages available. hasMore: type: boolean description: Indicates if there are more pages available. statistics: type: object properties: totalOperators: type: integer description: The total number of operators. totalStake: type: number description: The total stake across all operators. averageStake: type: number description: The average stake per operator. description: Aggregated statistics for the operators. description: Metadata and statistics about the query result. '400': $ref: '#/components/responses/400' '401': $ref: '#/components/responses/401' '403': $ref: '#/components/responses/403' '404': $ref: '#/components/responses/404' '422': $ref: '#/components/responses/422' '429': $ref: '#/components/responses/429' '500': $ref: '#/components/responses/500' components: responses: '400': description: >- The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing). content: application/json: schema: type: object properties: error: type: object properties: code: type: string enum: - bad_request description: A short code indicating the error code returned. example: bad_request message: type: string description: A human readable explanation of what went wrong. example: The requested resource was not found. doc_url: type: string description: >- A link to our documentation with more details about this error code example: >- https://docs.rescan.dev.com/api-reference/errors#bad_request required: - code - message required: - error '401': description: >- Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response. content: application/json: schema: type: object properties: error: type: object properties: code: type: string enum: - unauthorized description: A short code indicating the error code returned. example: unauthorized message: type: string description: A human readable explanation of what went wrong. example: The requested resource was not found. doc_url: type: string description: >- A link to our documentation with more details about this error code example: >- https://docs.rescan.dev.com/api-reference/errors#unauthorized required: - code - message required: - error '403': description: >- The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server. content: application/json: schema: type: object properties: error: type: object properties: code: type: string enum: - forbidden description: A short code indicating the error code returned. example: forbidden message: type: string description: A human readable explanation of what went wrong. example: The requested resource was not found. doc_url: type: string description: >- A link to our documentation with more details about this error code example: https://docs.rescan.dev.com/api-reference/errors#forbidden required: - code - message required: - error '404': description: The server cannot find the requested resource. content: application/json: schema: type: object properties: error: type: object properties: code: type: string enum: - not_found description: A short code indicating the error code returned. example: not_found message: type: string description: A human readable explanation of what went wrong. example: The requested resource was not found. doc_url: type: string description: >- A link to our documentation with more details about this error code example: https://docs.rescan.dev.com/api-reference/errors#not_found required: - code - message required: - error '422': description: >- The request was well-formed but was unable to be followed due to semantic errors. content: application/json: schema: type: object properties: error: type: object properties: code: type: string enum: - unprocessable_entity description: A short code indicating the error code returned. example: unprocessable_entity message: type: string description: A human readable explanation of what went wrong. example: The requested resource was not found. doc_url: type: string description: >- A link to our documentation with more details about this error code example: >- https://docs.rescan.dev.com/api-reference/errors#unprocessable_entity required: - code - message required: - error '429': description: >- The user has sent too many requests in a given amount of time ("rate limiting") content: application/json: schema: type: object properties: error: type: object properties: code: type: string enum: - rate_limit_exceeded description: A short code indicating the error code returned. example: rate_limit_exceeded message: type: string description: A human readable explanation of what went wrong. example: The requested resource was not found. doc_url: type: string description: >- A link to our documentation with more details about this error code example: >- https://docs.rescan.dev.com/api-reference/errors#rate_limit_exceeded required: - code - message required: - error '500': description: The server has encountered a situation it does not know how to handle. content: application/json: schema: type: object properties: error: type: object properties: code: type: string enum: - internal_server_error description: A short code indicating the error code returned. example: internal_server_error message: type: string description: A human readable explanation of what went wrong. example: The requested resource was not found. doc_url: type: string description: >- A link to our documentation with more details about this error code example: >- https://docs.rescan.dev.com/api-reference/errors#internal_server_error required: - code - message required: - error ````