Other Event Logs

Purpose

This endpoint allows you to retrieve logs for other event types that don't fall into the "Incoming Message" or "Message Status" categories. These may include system events, configuration changes, or other WhatsApp Business API events that are logged by your account.

Use this endpoint when you need to monitor events that are not standard message or status updates.

Endpoint Information

Method: GET
Path: /v1/logs
Event Type: eventTypes=Other (URL encoded)

Request Configuration

Required Parameters

Parameter	Type	Description
`eventTypes`	string	Must be `Other` (URL encoded)

Optional Parameters

Parameter	Type	Description
`fromDate`	integer	Start date in Ticks format (100-nanosecond intervals since January 1, 0001 UTC). If omitted, retrieves logs from the beginning of available data.
`toDate`	integer	End date in Ticks format. If omitted, retrieves logs up to the current time.
`phoneNumberId`	string	Filter by a specific WhatsApp Business phone number ID
`url`	string	Filter by a specific webhook URL (must be URL encoded)
`pageSize`	integer	Number of log entries to return per page. Default: 20, Maximum: 20
`nextPageToken`	string	Token for pagination to retrieve the next page of results. Use the `next_page_token` value from the previous response.

Understanding Ticks Format

The date parameters use Ticks format: 100-nanosecond intervals since January 1, 0001 at 00:00:00 UTC.

Format Example: 638000000000000000

API Request Examples

Standard Request

Retrieve all "Other" event logs without date filters:

Or with date range:

With Phone Number Filter

Filter by a specific phone number ID:

With Webhook URL Filter

Filter by a specific webhook endpoint:

With Page Size

Response Format

Successful Response

{
    "message": "Notification logs retrieved successfully",
    "data": {
        "logs": [
            {
                "project_id": "12345",
                "phone_number_id": "123456789012345",
                "event_type": "Other",
                "payload": "{\"object\":\"whatsapp_business_account\",\"entry\":[...]}",
                "created_at": 638500000000000000,
                "direction": 1,
                "flyout_delivery_status": "-",
                "flyout_delivery_response": "-",
                "flyout_delivery_response_code": 0,
                "flyout_url": "-"
            }
        ],
        "next_page_token": "eyJQcm9qZWN0SWQiOnsiTiI6IjEyMzQ1In0sIkNyZWF0ZWRBdCI6eyJOOiI2Mzg1MDAwMDAwMDAwMDAwMCJ9fQ=="
    }
}

Response Schema

Main Response Object

message (string): Descriptive message about the operation result

data (object): Contains the actual log data

Data Object Properties

data.logs (array): Collection of log entries

data.next_page_token (string, optional): Token for pagination

Individual Log Entry Schema

Each log entry in the array contains:

Property	Data Type	Description
`project_id`	string	Identifier for your project
`phone_number_id`	string	WhatsApp Business phone number ID associated with the event
`event_type`	string	Event classification (will be "Other" for this endpoint)
`payload`	string	Complete webhook payload as a JSON string
`created_at`	integer	Event creation timestamp in Ticks format
`direction`	integer	Direction indicator (1 = incoming)
`flyout_delivery_status`	string	Status of flyout notification delivery
`flyout_delivery_response`	string	Response from flyout delivery attempt
`flyout_delivery_response_code`	integer	HTTP status code from flyout delivery
`flyout_url`	string	URL used for flyout notifications

Payload Structure

The payload field contains a JSON string that, when parsed, follows the WhatsApp Business API webhook structure. The exact structure may vary depending on the specific "Other" event type, but typically includes:

{
    "object": "whatsapp_business_account",
    "entry": [
        {
            "id": "...",
            "changes": [
                {
                    "field": "...",
                    "value": {
                        // Event-specific data structure
                    }
                }
            ]
        }
    ]
}

Note: The payload structure for "Other" events may differ from message or status events. Always parse and inspect the payload to understand the specific event structure.

Pagination Guide

When the response includes a next_page_token, you can retrieve the next page of results by including the nextPageToken parameter:

Pagination Steps:

Make your initial request

Check for next_page_token in the response

If present, include it as nextPageToken in your next request with all original parameters

Repeat until no next_page_token is returned

Error Response Codes

400 Bad Request

Returned when request parameters are invalid or malformed.

{
    "message": "Invalid request parameters",
    "data": null
}

401 Unauthorized

Returned when authentication is missing or invalid.

{
    "message": "Unauthorized"
}

403 Forbidden

Returned when the request is authenticated but lacks sufficient permissions.

{
    "message": "Forbidden"
}

500 Internal Server Error

Returned when an unexpected server error occurs.

{
    "message": "Internal server error",
    "data": null
}

Key Points to Remember

Retention Period: Logs are retained for 7 days only

JSON Parsing: The payload field requires JSON parsing before use

Event Variability: "Other" events may have different payload structures

URL Encoding: Remember to URL encode the eventTypes parameter value

Timestamp Format: All timestamps use Ticks format

Practical Applications

System Monitoring: Track system-level events and changes

Event Auditing: Maintain comprehensive audit logs

Troubleshooting: Investigate non-standard events or issues

Integration Testing: Verify webhook handling for various event types

Compliance: Meet logging requirements for regulatory purposes

Implementation Example

Retrieve All Event Logs - Get all event types without filtering

Retrieve Incoming Message Logs - Get incoming message events

Retrieve Message Status Logs - Get message status updates

Retrieve Multiple Event Types - Get specific multiple event types

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Purpose#

Endpoint Information#

Request Configuration#

Required Parameters#

Optional Parameters#

Understanding Ticks Format#

API Request Examples#

Standard Request#

With Phone Number Filter#

With Webhook URL Filter#

With Page Size#

Response Format#

Successful Response#

Response Schema#

Main Response Object#

Data Object Properties#

Individual Log Entry Schema#

Payload Structure#

Pagination Guide#

Error Response Codes#

400 Bad Request#

401 Unauthorized#

403 Forbidden#

500 Internal Server Error#

Key Points to Remember#

Practical Applications#

Implementation Example#

Related Documentation#

Request

Responses