Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
Unique campaign ID of the loyalty program.
"camp_rRsfatlwN7unSeUIJDCYedal"
Body
Provide details to whom the loyalty card should be assigned.
You can choose to either specify the exact loyalty card code that you want to publish from existin (non-assigned) codes, or choose not to specify a voucher code. If you choose not to specify a code in the request paylaod, then the system will choose the next available voucher code available to be assigned to a customer.
You can also include metadata in the request payload. This metadata will be assigned to the publication object, but will not be returned in the response to this endpoint. To see of publications (assignments of particular codes to customers) and publication metadata, use the <!-- [List Publications](OpenAPI.json/paths/~1publications/get) -->List Publications endpoint.
Request body schema for assigning a loyalty card to a customer using POST /loyalties/{campaignId}/members
.
Create publication
Contains information about the customer to whom the publication was directed.
Code of voucher being published.
The merchant's publication ID if it is different from the Voucherify publication ID. It's an optional tracking identifier of a publication. It is really useful in case of an integration between multiple systems. It can be a publication ID from a CRM system, database or 3rd-party service.
If source_id
is provided only 1 voucher can be published per request.
The metadata object stores all custom attributes assigned to the publication. A set of key/value pairs that you can attach to a publication object. It can be useful for storing additional information about the publication in a structured format.
Specify the distribution channel.
Response
Returns the voucher object that was published to the customer provided in the request payload.
Respone body schema for assigning a loyalty card to a customer using POST /loyalties/{campaignId}/members
.
This is an object representing a loyalty member.
Assigned by the Voucherify API, identifies the voucher.
"v_mkZN9v7vjYUadXnHrMza8W5c34fE5KiV"
A code that identifies a voucher. Pattern can use all letters of the English alphabet, Arabic numerals, and special characters.
"WVPblOYX"
A unique campaign name, identifies the voucher's parent campaign.
"Loyalty campaign"
Assigned by the Voucherify API, identifies the voucher's parent campaign.
"camp_FNYR4jhqZBM9xTptxDGgeNBV"
Tag defining the category that this voucher belongs to.
Unique category ID assigned by Voucherify.
"cat_0bb343dee3cdb5ec0c"
Defines the type of the voucher.
LOYALTY_CARD
Object representing loyalty card parameters. Child attributes are present only if type
is LOYALTY_CARD
. Defaults to null
.
Activation timestamp defines when the code starts to be active in ISO 8601 format. Voucher is inactive before this date.
"2021-12-01T00:00:00.000Z"
Expiration timestamp defines when the code expires in ISO 8601 format. Voucher is inactive after this date.
"2021-12-31T00:00:00.000Z"
Set recurrent time periods when the earning rule is valid. For example, valid for 1 hour every other day.start_date
required when including the validity_timeframe
.
Integer array corresponding to the particular days of the week in which the voucher is valid.
0
Sunday1
Monday2
Tuesday3
Wednesday4
Thursday5
Friday6
Saturday
Determines the hours of validity, e.g. to create a happy hours scenario.
A flag to toggle the voucher on or off. You can disable a voucher even though it's within the active period defined by the start_date
and expiration_date
.
true
indicates an active voucherfalse
indicates an inactive voucher
An optional field to keep any extra textual information about the code such as a code description and details.
The metadata object stores all custom attributes assigned to the code. A set of key/value pairs that you can attach to a voucher object. It can be useful for storing additional information about the voucher in a structured format.
Stores links to images of QR and barcode that correspond to an encrypted voucher code.
This is always false for loyalty members.
Timestamp representing the date and time when the voucher was created. The value is shown in the ISO 8601 format.
"2021-12-22T10:13:06.487Z"
Timestamp representing the date and time when the voucher was last updated in ISO 8601 format.
"2021-12-22T10:14:45.316Z"
Unique identifier of the customer who owns the voucher.
"cust_eWgXlBBiY6THFRJwX45Iakv4"
The type of the object represented by JSON. Default is voucher
.
This object stores a summary of publish events: an events counter and an endpoint which can be called to return details of each event. A publication is required for loyalty cards and referral codes. This object gets updated whenever a voucher has been published. Publication means assigning a code to a particular customer. Typically, a publication is made by distributing your codes to your customers, e.g. through Export to MailChimp or <!-- [publish voucher](OpenAPI.json/paths/~1publications/post) -->publish voucher API method.
<!-- title: My Table Title -->Required | Optional |
---|---|
type :LOYALTY_CARD | type :DISCOUNT_VOUCHER |
is_referral_code :true | type :GIFT_VOUCHER |
Stores a summary of redemptions that have been applied to the voucher.