All URIs are relative to https://api.voucherify.io
Method | HTTP request | Description |
---|---|---|
check_eligibility_client_side | POST /client/v1/qualifications | Check Eligibility (client-side) |
list_promotion_tiers_client_side | GET /client/v1/promotions/tiers | List Promotion Tiers (client-side) |
redeem_stacked_discounts_client_side | POST /client/v1/redemptions | Redeem Stackable Discounts (client-side) |
track_custom_event_client_side | POST /client/v1/events | Track Custom Event (client-side) |
validate_stacked_discounts_client_side | POST /client/v1/validations | Validate Stackable Discounts (client-side) |
check_eligibility_client_side(opts)
Check Eligibility (client-side)
Generate a list of redeemables that are applicable in the context of the customer and order. The new qualifications method is an improved version of Campaign Qualifications, Voucher Qualifications, and Promotions Validation API requests. The new qualification method introduces the following improvements: - Qualification results are returned faster - No limit on the number of returned redeemables - Introduces new qualification scenarios, not available in the previous version 👍 Scenario Guide Read our dedicated guide to learn about some use cases this endpoint can cover here. # Paging The Voucherify Qualifications API request will return to you all of the redeemables available for the customer in batches of up to 50 redeemables. To get the next batch of redeemables, you need to use the starting_after cursor. To process of paging the redeemables works in the following manner: - You send the first API request for Qualifications without the starting_after parameter. - The response will contain a parameter named has_more. If the parameters value is set to true, then more redeemables are available. - Get the value of the created_at parameter of the last returned redeemable. The value of this parameter will be used as a cursor to retrieve the next page of redeemables. - Send another API request for Qualification with the starting_after parameter set to the value taken from the created_at parameter from the last returned redeemable. - Voucherify will return the next page of redeemables. - If the has_more parameter is set to true, apply steps 3-5 to get the next page of redeemables.
require 'time'
require 'VoucherifySdk'
# setup authorization
VoucherifySdk.configure do |config|
# Configure API key authorization: X-Client-Application-Id
config.api_key['X-Client-Application-Id'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Application-Id'] = 'Bearer'
# Configure API key authorization: X-Client-Token
config.api_key['X-Client-Token'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Token'] = 'Bearer'
end
api_instance = VoucherifySdk::ClientSideApi.new
opts = {
client_qualifications_check_eligibility_request_body: VoucherifySdk::ClientQualificationsCheckEligibilityRequestBody.new # ClientQualificationsCheckEligibilityRequestBody | Define order and customer context.
}
begin
# Check Eligibility (client-side)
result = api_instance.check_eligibility_client_side(opts)
p result
rescue VoucherifySdk::ApiError => e
puts "Error when calling ClientSideApi->check_eligibility_client_side: #{e}"
end
Name | Type | Description | Notes |
---|---|---|---|
client_qualifications_check_eligibility_request_body | ClientQualificationsCheckEligibilityRequestBody | Define order and customer context. | [optional] |
ClientQualificationsCheckEligibilityResponseBody
X-Client-Application-Id, X-Client-Token
- Content-Type: application/json
- Accept: application/json
list_promotion_tiers_client_side(origin, opts)
List Promotion Tiers (client-side)
This method enables you to list promotion tiers.
require 'time'
require 'VoucherifySdk'
# setup authorization
VoucherifySdk.configure do |config|
# Configure API key authorization: X-Client-Application-Id
config.api_key['X-Client-Application-Id'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Application-Id'] = 'Bearer'
# Configure API key authorization: X-Client-Token
config.api_key['X-Client-Token'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Token'] = 'Bearer'
end
api_instance = VoucherifySdk::ClientSideApi.new
origin = 'origin_example' # String | Indicates the origin (scheme, hostname, and port).
opts = {
is_available: true, # Boolean | This parameter allows filtering promotions that are only available at the moment. When set to true, it selects only non-expired and active promotions.
limit: 56, # Integer | Limits the number of objects to be returned. The limit can range between 1 and 100 items.
page: 56, # Integer | Which page of results to return. The lowest value is 1.
order: VoucherifySdk::ParameterOrderListPromotionTiersClientSide::CREATED_AT # ParameterOrderListPromotionTiersClientSide | Sorts the results using one of the filtering options, where the dash - preceding a sorting option means sorting in a descending order.
}
begin
# List Promotion Tiers (client-side)
result = api_instance.list_promotion_tiers_client_side(origin, opts)
p result
rescue VoucherifySdk::ApiError => e
puts "Error when calling ClientSideApi->list_promotion_tiers_client_side: #{e}"
end
Name | Type | Description | Notes |
---|---|---|---|
origin | String | Indicates the origin (scheme, hostname, and port). | |
is_available | Boolean | This parameter allows filtering promotions that are only available at the moment. When set to true, it selects only non-expired and active promotions. | [optional] |
limit | Integer | Limits the number of objects to be returned. The limit can range between 1 and 100 items. | [optional] |
page | Integer | Which page of results to return. The lowest value is 1. | [optional] |
order | ParameterOrderListPromotionTiersClientSide | Sorts the results using one of the filtering options, where the dash - preceding a sorting option means sorting in a descending order. | [optional] |
ClientPromotionsTiersListResponseBody
X-Client-Application-Id, X-Client-Token
- Content-Type: Not defined
- Accept: application/json
redeem_stacked_discounts_client_side(origin, opts)
Redeem Stackable Discounts (client-side)
This method is accessible through public keys which you can use in client side requests coming from mobile and web browser applications. # How API returns calculated discounts and order amounts in the response In the table below, you can see the logic the API follows to calculate discounts and amounts: 📘 Rollbacks You cant roll back a child redemption. When you call rollback on a stacked redemption, all child redemptions will be rolled back. You need to refer to a parent redemption ID in your rollback request.
require 'time'
require 'VoucherifySdk'
# setup authorization
VoucherifySdk.configure do |config|
# Configure API key authorization: X-Client-Application-Id
config.api_key['X-Client-Application-Id'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Application-Id'] = 'Bearer'
# Configure API key authorization: X-Client-Token
config.api_key['X-Client-Token'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Token'] = 'Bearer'
end
api_instance = VoucherifySdk::ClientSideApi.new
origin = 'origin_example' # String | Indicates the origin (scheme, hostname, and port).
opts = {
client_redemptions_redeem_request_body: VoucherifySdk::ClientRedemptionsRedeemRequestBody.new # ClientRedemptionsRedeemRequestBody |
}
begin
# Redeem Stackable Discounts (client-side)
result = api_instance.redeem_stacked_discounts_client_side(origin, opts)
p result
rescue VoucherifySdk::ApiError => e
puts "Error when calling ClientSideApi->redeem_stacked_discounts_client_side: #{e}"
end
Name | Type | Description | Notes |
---|---|---|---|
origin | String | Indicates the origin (scheme, hostname, and port). | |
client_redemptions_redeem_request_body | ClientRedemptionsRedeemRequestBody | [optional] |
ClientRedemptionsRedeemResponseBody
X-Client-Application-Id, X-Client-Token
- Content-Type: application/json
- Accept: application/json
track_custom_event_client_side(origin, opts)
Track Custom Event (client-side)
To track a custom event, you create an event object. The event object must be linked to the customer who performs the action. If a customer doesnt exist in Voucherify, the customer will be created.
require 'time'
require 'VoucherifySdk'
# setup authorization
VoucherifySdk.configure do |config|
# Configure API key authorization: X-Client-Application-Id
config.api_key['X-Client-Application-Id'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Application-Id'] = 'Bearer'
# Configure API key authorization: X-Client-Token
config.api_key['X-Client-Token'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Token'] = 'Bearer'
end
api_instance = VoucherifySdk::ClientSideApi.new
origin = 'origin_example' # String | Indicates the origin (scheme, hostname, and port).
opts = {
client_events_create_request_body: VoucherifySdk::ClientEventsCreateRequestBody.new({customer: VoucherifySdk::Customer.new}) # ClientEventsCreateRequestBody | Specify the details of the custom event.
}
begin
# Track Custom Event (client-side)
result = api_instance.track_custom_event_client_side(origin, opts)
p result
rescue VoucherifySdk::ApiError => e
puts "Error when calling ClientSideApi->track_custom_event_client_side: #{e}"
end
Name | Type | Description | Notes |
---|---|---|---|
origin | String | Indicates the origin (scheme, hostname, and port). | |
client_events_create_request_body | ClientEventsCreateRequestBody | Specify the details of the custom event. | [optional] |
ClientEventsCreateResponseBody
X-Client-Application-Id, X-Client-Token
- Content-Type: application/json
- Accept: application/json
validate_stacked_discounts_client_side(origin, opts)
Validate Stackable Discounts (client-side)
Verify redeemables provided in the request. This method is accessible through public keys which you can use in client side requests coming from mobile and web browser applications.
require 'time'
require 'VoucherifySdk'
# setup authorization
VoucherifySdk.configure do |config|
# Configure API key authorization: X-Client-Application-Id
config.api_key['X-Client-Application-Id'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Application-Id'] = 'Bearer'
# Configure API key authorization: X-Client-Token
config.api_key['X-Client-Token'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
# config.api_key_prefix['X-Client-Token'] = 'Bearer'
end
api_instance = VoucherifySdk::ClientSideApi.new
origin = 'origin_example' # String | Indicates the origin (scheme, hostname, and port).
opts = {
client_validations_validate_request_body: VoucherifySdk::ClientValidationsValidateRequestBody.new # ClientValidationsValidateRequestBody |
}
begin
# Validate Stackable Discounts (client-side)
result = api_instance.validate_stacked_discounts_client_side(origin, opts)
p result
rescue VoucherifySdk::ApiError => e
puts "Error when calling ClientSideApi->validate_stacked_discounts_client_side: #{e}"
end
Name | Type | Description | Notes |
---|---|---|---|
origin | String | Indicates the origin (scheme, hostname, and port). | |
client_validations_validate_request_body | ClientValidationsValidateRequestBody | [optional] |
ClientValidationsValidateResponseBody
X-Client-Application-Id, X-Client-Token
- Content-Type: application/json
- Accept: application/json