> ## 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. # Pod Activity > Fetches paginated activities for a specific pod along with global statistics. ## OpenAPI ````yaml get /eigenlayer/pod-activity 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: /eigenlayer/pod-activity: get: summary: Pod Activity description: >- Fetches paginated activities for a specific pod along with global statistics. operationId: getActivities parameters: - name: page in: query required: false schema: type: integer default: 1 description: The page number for pagination. Defaults to 1. - name: limit in: query required: false schema: type: integer default: 12 description: The number of items per page for pagination. Defaults to 12. - name: pod in: query required: true schema: type: string description: The unique identifier of the pod. responses: '200': description: Successful response containing activity data and metadata. content: application/json: schema: type: object properties: data: type: array items: type: object properties: action: type: string description: The action performed in the activity. operator: type: string description: The operator involved in the activity. staker: type: string description: The staker associated with the activity. strategy: type: string description: The strategy involved in the activity. token: type: string description: The token involved in the activity. avs: type: string description: >- Additional value or state associated with the activity. pod: type: string description: The pod related to the activity. data: type: object description: Additional data related to the activity. metadata: type: object description: Metadata of the activity. activity_timestamp: type: string format: date-time description: The timestamp of the activity. meta: type: object properties: total: type: integer description: Total number of activities. page: type: integer description: Current page number. limit: type: integer description: Number of items per page. totalPages: type: integer description: Total number of pages. hasMore: type: boolean description: Indicates if more pages are available. statistics: type: object properties: totalActivities: type: integer description: Total number of activities globally. uniqueActions: type: integer description: Total number of unique actions globally. uniqueStakers: type: integer description: Total number of unique stakers globally. uniquePods: type: integer description: Total number of unique pods globally. '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 ````