# WhatsAppCampaigns: Sendinblue WhatsApp Campaigns Return all your created WhatsApp campaigns Retrieve a paginated list of all your WhatsApp campaigns with their statistics and metadata. Results can be filtered by creation date range using startDate and endDate, with a default limit of 50 and maximum of 100 per page. The sort order defaults to descending by modification date. - Catalog: `Brevo` - Schema: `WhatsAppCampaigns` - Primary Keys: `id` - Label: WhatsApp Campaigns Can retrieve data and change data using insert, update and delete. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `WhatsAppCampaigns`. 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 | |---|:---:|:---:|:---:|---| | `endDate` | `` | ☐ | | **Mandatory if startDate is used**. Ending (urlencoded) UTC date-time (YYYY-MM-DDTHH:mm:ss.SSSZ) to filter the WhatsApp campaigns created. **Prefer to pass your timezone in date-time format for accurate result** | | `startDate` | `` | ☐ | | **Mandatory if endDate is used**. Starting (urlencoded) UTC date-time (YYYY-MM-DDTHH:mm:ss.SSSZ) to filter the WhatsApp campaigns created. **Prefer to pass your timezone in date-time format for accurate result** | ## Columns of Table Function The columns of the table function `WhatsAppCampaigns` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `campaignName` | `varchar2` | | ☐ | Name of the WhatsApp Campaign | | `campaignStatus` | `varchar2` | | ☐ | Status of the Whatsapp Campaign | | `createdAt` | `varchar2` | Creation Date | ☐ | Creation UTC date-time of the WhatsApp campaign (YYYY-MM-DDTHH:mm:ss.SSSZ) | | `errorReason` | `varchar2` | | ☐ | Error Reason associated with the WhatsApp campaign sending | | `id` | `int64` | ID | ☐ | ID of the WhatsApp Campaign | | `invalidatedContacts` | `int64` | | ☐ | Count of invalidated contacts | | `modifiedAt` | `varchar2` | Modified Date | ☐ | UTC date-time of last modification of the WhatsApp campaign (YYYY-MM-DDTHH:mm:ss.SSSZ) | | `readPercentage` | `double` | | ☐ | Read percentage of the the whatsapp campaign created | | `scheduledAt` | `varchar2` | Schedule Date | ☐ | UTC date-time on which WhatsApp campaign is scheduled. Should be in YYYY-MM-DDTHH:mm:ss.SSSZ format | | `stats_delivered` | `int64` | #Delivered | ☐ | | | `stats_notSent` | `int64` | | ☐ | | | `stats_read` | `int64` | | ☐ | | | `stats_sent` | `int64` | #Sent | ☐ | | | `stats_unsubscribe` | `int64` | | ☐ | | | `templateId` | `varchar2` | Template ID | ☐ | Id of the WhatsApp template |