# WhatsappEventReports Get all your WhatsApp activity (unaggregated events) This endpoint will show the unaggregated statistics for WhatsApp activity (30 days by default if `startDate` and `endDate` or `days` is not passed. The date range can not exceed 90 days) - Catalog: `Brevo` - Schema: `TransactionalWhatsApp` This is a read-only table function. The Sendinblue API may not support changing the data or the Invantive UniversalSQL driver for Sendinblue does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Sendinblue API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `WhatsappEventReports`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `contactNumber` | `` | ☐ | | Filter results for specific contact (WhatsApp Number with country code. Example, 85264318721) | | `days` | `` | ☐ | | Number of days in the past including today (positive integer). _Not compatible with 'startDate' and 'endDate'_ | | `endDate` | `` | ☐ | | **Mandatory if startDate is used.** Ending date of the report (YYYY-MM-DD). Must be greater than equal to startDate | | `event` | `` | ☐ | | Filter the report for a specific event type (Values: sent, delivered, read, error, unsubscribe, reply, soft-bounce) | | `startDate` | `` | ☐ | | **Mandatory if endDate is used.** Starting date of the report (YYYY-MM-DD). Must be lower than equal to endDate | ## Columns of Table Function The columns of the table function `WhatsappEventReports` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `body` | `varchar2` | Body | ☐ | Text of the reply (will be there only in case of `reply` event with text) | | `contactNumber` | `varchar2` | | ☐ | WhatsApp Number with country code. Example, 85264318721 | | `date` | `varchar2` | Date | ☐ | UTC date-time on which the event has been generated | | `event` | `varchar2` | Event | ☐ | Event which occurred | | `mediaUrl` | `varchar2` | | ☐ | Url of the media reply (will be there only in case of `reply` event with media) | | `messageId` | `varchar2` | Message ID | ☐ | Message ID which generated the event | | `reason` | `varchar2` | Reason | ☐ | Reason for the event (will be there in case of `error` and `soft-bounce` events) | | `senderNumber` | `varchar2` | | ☐ | WhatsApp Number with country code. Example, 85264318721 |