Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 3.71 KB

CampaignsUpdateRequestBody.md

File metadata and controls

57 lines (41 loc) · 3.71 KB

CampaignsUpdateRequestBody

Properties

Name Type Description Notes
startDate OffsetDateTime Activation timestamp defines when the campaign starts to be active in ISO 8601 format. Campaign is inactive before this date. [optional]
expirationDate OffsetDateTime Expiration timestamp defines when the campaign expires in ISO 8601 format. Campaign is inactive after this date. [optional]
validityTimeframe CampaignsUpdateRequestBodyValidityTimeframe [optional]
validityDayOfWeek List<ValidityDayOfWeekEnum> Integer array corresponding to the particular days of the week in which the campaign is valid. - `0` Sunday - `1` Monday - `2` Tuesday - `3` Wednesday - `4` Thursday - `5` Friday - `6` Saturday [optional]
validityHours ValidityHours [optional]
description String An optional field to keep any extra textual information about the campaign such as a campaign description and details. [optional]
category String The category assigned to the campaign. Either pass this parameter OR the `category_id`. [optional]
metadata Object [optional]
unsetMetadataFields List<String> Determine which metadata should be removed from campaign. [optional]
categoryId String Unique category ID that this campaign belongs to. Either pass this parameter OR the `category`. [optional]
activityDurationAfterPublishing String Defines the amount of time the campaign will be active in ISO 8601 format after publishing. For example, a campaign with a `duration` of `P24D` will be valid for a duration of 24 days. [optional]
joinOnce Boolean If this value is set to `true`, customers will be able to join the campaign only once. [optional]
autoJoin Boolean Indicates whether customers will be able to auto-join a loyalty campaign if any earning rule is fulfilled. [optional]
type TypeEnum Defines whether the campaign can be updated with new vouchers after campaign creation. - `AUTO_UPDATE`: By choosing the auto update option you will create a campaign that can be enhanced by new vouchers after the time of creation (e.g. by publish vouchers method). - `STATIC`: vouchers need to be manually published. [optional]
discount Object [optional]
referralProgram ReferralProgram [optional]
gift Gift [optional]
loyaltyTiersExpiration LoyaltyTiersExpirationAll [optional]
options CampaignsUpdateRequestBodyOptions [optional]
winnersCount String It represents the total number of winners in a lucky draw. [optional]
uniqueWinnersPerDraw String It indicates whether each winner in a draw is unique or not. [optional]
uniqueWinners String Specifies whether each participant can win only once across multiple draws. [optional]

Enum: List<ValidityDayOfWeekEnum>

Name Value
NUMBER_0 0
NUMBER_1 1
NUMBER_2 2
NUMBER_3 3
NUMBER_4 4
NUMBER_5 5
NUMBER_6 6

Enum: TypeEnum

Name Value
AUTO_UPDATE "AUTO_UPDATE"
STATIC "STATIC"