---
title: "Get WhatsApp Message History Events"
method: GET
path: "/{Version}/{Message-History-ID}/events"
tags: ["Message History Events"]
---

# Get WhatsApp Message History Events

`GET /{Version}/{Message-History-ID}/events`

## Request

- Base URL: `https://graph.facebook.com`
- URL: `https://graph.facebook.com/{Version}/{Message-History-ID}/events`
- Auth: HTTP bearer

Retrieve paginated message delivery status events for a specific message history entry,
including delivery status occurrences, timestamps, and application information.


**Use Cases:**
- Track detailed message delivery status events and transitions
- Monitor delivery status occurrence timestamps
- Retrieve application information for delivery events
- Debug message delivery issues and status changes


**Rate Limiting:**
Standard Graph API rate limits apply. Use appropriate retry logic with exponential backoff.


**Caching:**
Message history events can be cached for short periods, but delivery status events
may change frequently. Implement appropriate cache invalidation strategies.


**Pagination:**
This endpoint supports cursor-based pagination. Use the `after` and `before` cursors
from the response to navigate through results.

## Path parameters

- `Version` string, required
- `Message-History-ID` string, required

## Query parameters

- `status_filter` 'SENT' | 'DELIVERED' | 'READ' | 'FAILED' | 'DELETED': Message delivery status
- `fields` string
- `limit` integer
- `after` string
- `before` string

## Headers

- `User-Agent` string
- `Authorization` string, required

## Response `200`

Successfully retrieved WhatsApp message history events

- MessageHistoryEventsResponse: Paginated response containing message history events
  - `data` WhatsAppMessageHistoryEventsEdge[]: Array of message history event edges
    - `cursor` string: Pagination cursor for this edge
    - `node` WhatsAppBusinessMessageDeliveryStatusOccurrence, required: Message delivery status occurrence with detailed event information
      - `id` string, required: Unique identifier for the message delivery status occurrence
      - `delivery_status` 'SENT' | 'DELIVERED' | 'READ' | 'FAILED' | 'DELETED', required: Message delivery status
      - `error_description` string: Error description if the delivery encountered an error
      - `occurrence_timestamp` integer, required: Unix timestamp when the delivery status occurrence happened
      - `status_timestamp` integer: Unix timestamp when the status was recorded
      - `application` ApplicationNode: Meta application that owns the Multi-Partner Solution
        - `id` string: Unique identifier for the Meta application
        - `name` string: Name of the Meta application
  - `paging` PaginationInfo: Pagination information for navigating through results
    - `cursors` object: Pagination cursors for navigation
      - `before` string: Cursor for the previous page of results
      - `after` string: Cursor for the next page of results
    - `previous` string, uri: URL for the previous page of results
    - `next` string, uri: URL for the next page of results

## Other responses

- `400`: Bad Request - Invalid parameters or malformed request
- `401`: Unauthorized - Invalid or missing access token
- `403`: Forbidden - Insufficient permissions or access denied
- `404`: Not Found - Message History ID does not exist or is not accessible
- `422`: Unprocessable Entity - Request parameters are valid but cannot be processed
- `429`: Too Many Requests - Rate limit exceeded
- `500`: Internal Server Error - Unexpected server error

---

[API](https://skmtc.dev/meta/apis/whatsapp-business-messaging.md) - [All operations](https://skmtc.dev/meta/apis/whatsapp-business-messaging/llms.txt) - [OpenAPI document](https://skmtc.dev/meta/apis/whatsapp-business-messaging/revisions/5c1973265369?raw)