> ## Documentation Index > Fetch the complete documentation index at: https://docs.beaconcha.in/llms.txt > Use this file to discover all available pages before exploring further. # Validator attestations history > Retrieve attestations observed for one or more validators within a bounded epoch window. By default, the service returns data for the last 100 epochs ending at the latest processed epoch. You can narrow the range with `startEpoch` and `endEpoch`, which must lie within `[latest-99, latest]` and satisfy `startEpoch <= endEpoch`. Each item represents a scheduled attestation duty for a validator and includes the slot attested to, the inclusion slot when observed, a status flag, and convenience week boundaries for grouping in UI charts. When `slim=true`, the response omits the `week`, `week_start`, `week_end`, and `committeeindex` properties from each item to reduce payload size. ## OpenAPI ````yaml /api/v1/bundled.yaml get /api/v1/validator/{indexOrPubkey}/attestations openapi: 3.0.4 info: title: beaconcha.in API Documentation license: name: GPL-3.0 url: https://www.gnu.org/licenses/gpl-3.0.en.html description: >- > ⚠️ No new features or endpoints will be added to V1. We recommend the [V2 API](/api/overview) for all new projects. See the [migration guide](/api/v1-to-v2-migration). ## Introduction **Advanced and reliable API for accessing comprehensive Ethereum blockchain data.** - **Free Usage Policy:** The API is free to use under a fair use policy, with rate limits of 10 requests per minute per IP. - **Caching:** All responses are cached for 1 minute. - **Higher Usage Plans:** For higher usage plans, visit: [https://beaconcha.in/pricing](https://beaconcha.in/pricing). An API key is required to use these plans. ### API Key Usage API keys can be obtained at [/user/settings](https://beaconcha.in/user/settings) and must be included in requests either as a query string parameter or in the request header. #### Example: Query String Parameter ```bash curl https://beaconcha.in/api/v1/slot/1?apikey= ``` #### Example: Request Header ```bash curl -H 'apikey: ' https://beaconcha.in/api/v1/slot/1 ``` contact: {} version: '1.1' servers: - url: https://beaconcha.in description: Ethereum mainnet - url: https://hoodi.beaconcha.in description: Hoodi Ethereum testnet security: - ApiKeyAuthQuery: [] - ApiKeyAuthHeader: [] tags: - name: Epoch description: Data related to consensus layer epochs - name: Slots description: Data related to consensus layer slots - name: Validators description: Data related to consensus layer validators - name: Rewards description: Data related to validator rewards - name: Sync Committees description: Data related to sync committees - name: Rocketpool description: Data related to the rocketpool protocol - name: ETH.Store® description: Data related to the ETH.Store® metric - name: Validator deposits description: Data related to execution layer validator deposits - name: Blocks description: Data related to execution layer blocks - name: Gas description: Data related to gas prices - name: Address description: Data related to ethereum addresses - name: Network description: Network data - name: Misc description: Miscellaneous data - name: User description: User data - name: Machine Metrics description: Submit machine, beacon-node, and validator-client monitoring metrics paths: /api/v1/validator/{indexOrPubkey}/attestations: get: tags: - Validators summary: Validator attestations history description: >- Retrieve attestations observed for one or more validators within a bounded epoch window. By default, the service returns data for the last 100 epochs ending at the latest processed epoch. You can narrow the range with `startEpoch` and `endEpoch`, which must lie within `[latest-99, latest]` and satisfy `startEpoch <= endEpoch`. Each item represents a scheduled attestation duty for a validator and includes the slot attested to, the inclusion slot when observed, a status flag, and convenience week boundaries for grouping in UI charts. When `slim=true`, the response omits the `week`, `week_start`, `week_end`, and `committeeindex` properties from each item to reduce payload size. operationId: listValidatorAttestations parameters: - name: indexOrPubkey in: path description: >- Comma-separated validator indices and/or public keys (maximum 100 items by default). required: true style: simple explode: false schema: $ref: '#/components/schemas/primitives.indicesOrPubkeys' - name: startEpoch in: query description: >- Start epoch for the query window. Defaults to `latest - 99`. Must be within `[latest-99, latest]` and less than or equal to `endEpoch` when provided. required: false style: form explode: true schema: type: integer minimum: 0 example: 399260 - name: endEpoch in: query description: >- End epoch for the query window. Defaults to `latest`. Must be within `[startEpoch, latest]` when provided. required: false style: form explode: true schema: type: integer minimum: 0 example: 399359 - name: slim in: query description: >- When true, return a slimmed response that excludes `week`, `week_start`, `week_end`, and `committeeindex` fields from each item. required: false style: form explode: true schema: type: boolean default: false example: true responses: '200': description: >- Matching attestations were retrieved successfully. The `data` array contains one entry per scheduled attestation for the specified validators within the requested epoch window. Items are sorted by epoch (descending) and then by validator index (ascending). content: application/json: schema: allOf: - $ref: '#/components/schemas/types.ApiResponse' - type: object properties: data: type: array items: $ref: >- #/components/schemas/types.ApiValidatorAttestationsResponse '400': description: >- The request is invalid (for example, malformed identifiers, out-of-range epochs, or too many identifiers). content: application/json: schema: $ref: '#/components/schemas/types.ApiErrorResponse' examples: invalidParam: summary: Invalid validator identifier value: status: 'ERROR: invalid validator-parameter' data: null tooMany: summary: Too many identifiers value: status: 'ERROR: only a maximum of 100 query parameters are allowed' data: null invalidStartEpoch: summary: Invalid startEpoch value: status: 'ERROR: invalid start epoch parameter' data: null invalidEndEpoch: summary: Invalid endEpoch value: status: 'ERROR: invalid end epoch parameter' data: null unresolvedPubkeys: summary: Pubkey did not resolve to an index value: status: >- ERROR: invalid validator argument, pubkey(s) did not resolve to a validator index data: null '500': description: An unexpected server error occurred while processing your request. content: application/json: schema: $ref: '#/components/schemas/types.ApiErrorResponse' examples: serverError: summary: Internal error value: status: 'ERROR: internal server error' data: null components: schemas: primitives.indicesOrPubkeys: type: string description: > Comma-separated list (no spaces) of validator identifiers. Each identifier must be either: - A validator index as a base-10 integer (for example, 652648) - A BLS public key as a 96-hex-character string with or without the 0x prefix (case-insensitive) Resolution and limits: - The server resolves public keys to validator indices before querying data. - The total number of identifiers must not exceed the server-enforced limit (default 100). - Identifiers that cannot be parsed or resolved result in HTTP 400. example: 1,2,3 types.ApiResponse: type: object description: Standard success envelope used by all API endpoints. properties: status: type: string description: >- HTTP-independent status of the API operation. For successful responses this is always "OK". enum: - OK data: description: Response payload specific to the endpoint. nullable: true x-omitempty: true types.ApiValidatorAttestationsResponse: type: object description: >- Per-validator attestation record within an epoch window. Each item corresponds to a scheduled attestation duty for a specific validator and includes the slot attested to, the observed inclusion slot (when included), a status flag, and week-based grouping metadata used in UI charts. properties: attesterslot: type: integer description: >- Slot number that the validator attested to (the source of the vote). Always non-negative. minimum: 0 example: 12779525 committeeindex: type: integer description: >- Committee index within the epoch for this attestation (>= 0). May be 0 when not recorded in this dataset. minimum: 0 example: 0 epoch: type: integer description: Epoch containing the attestation duty (>= 0). minimum: 0 example: 399360 inclusionslot: type: integer description: >- Slot number of the beacon block that included the attestation when it was observed on-chain. Set to 0 when the attestation was not observed/included (missed). minimum: 0 example: 12779526 status: type: integer description: >- Attestation status flag. 1 indicates the attestation was observed and included on-chain; 0 indicates it was missed. example: 1 validatorindex: type: integer description: Validator index (>= 0) to whom this attestation duty applies. minimum: 0 example: 20 week: type: integer description: Epoch-based week number computed as `epoch / (EpochsPerDay * 7)`. minimum: 0 example: 253 week_start: type: string format: date-time description: Start timestamp (UTC, RFC 3339) of the week containing `epoch`. example: '2025-10-07T12:00:23Z' week_end: type: string format: date-time description: End timestamp (UTC, RFC 3339) of the week containing `epoch`. example: '2025-10-14T12:00:23Z' types.ApiErrorResponse: type: object description: Standard error envelope returned when a request fails. properties: status: type: string description: >- Human-readable error indicator and message. The value begins with "ERROR:" followed by details. example: 'ERROR: ' data: type: string description: Optional additional context for the error. Null in most cases. nullable: true default: null securitySchemes: ApiKeyAuthQuery: type: apiKey in: query name: apikey description: '' ApiKeyAuthHeader: type: apiKey in: header name: apikey description: '' ````