Choose the right API endpoint
Voucherify hosts API clusters in multiple regions. Pick the one closest to your users for lower latency. Shared cluster endpoints:- Europe (default):
https://api.voucherify.io - United States:
https://us1.api.voucherify.io - Asia (Singapore):
https://as1.api.voucherify.io
SDKs let you override the default API endpoint. Read Readme of a specific SDK to learn more.
Understand request processing
Each API request runs in two phases:- Synchronous phase — main response (for example, redemption result).
- Asynchronous phase — background tasks such as:
- Updating segments
- Sending webhooks
- Applying loyalty points
- Triggering distributions
- Bulk imports or exports (customers, products, vouchers)
- Campaign creation or updates
- Metadata updates
Async actions
Async actions
| Types by Context | Endpoint |
|---|---|
| CAMPAIGN | |
CAMPAIGN.VOUCHERS_IMPORT | POST /campaigns/{campaignId}/import |
CAMPAIGN.VOUCHERS_IMPORT_CSV | POST /campaigns/{campaignId}/importCSV |
CAMPAIGN.VOUCHERS_UPDATE | PUT /campaigns/{campaignId} |
CAMPAIGN.VOUCHERS_DELETE | DELETE /campaigns/{campaignId} |
CAMPAIGN.VOUCHERS_GENERATE | - POST /campaigns: asynchronous for campaigns with more than 1 voucher, synchronous for campaign with 1 voucher - POST /campaigns/{campaignId}/vouchers> |
| CUSTOMERS | |
CUSTOMERS.IMPORT_CSV | POST /customers/importCSV |
CUSTOMERS.BULK_UPDATE | POST /customers/bulk/async |
CUSTOMERS.METADATA_UPDATE | POST /customers/metadata/async |
| PRODUCTS | |
PRODUCTS.BULK_UPDATE | POST /products/bulk/async |
PRODUCTS.METADATA_UPDATE | POST /products/metadata/async |
PRODUCTS.IMPORT_CSV | POST /products/importCSV |
SKUS.IMPORT_CSV | POST /skus/importCSV |
| VOUCHERS | |
VOUCHERS.IMPORT | POST /vouchers/import |
VOUCHERS.IMPORT_CSV | POST /vouchers/importCSV |
VOUCHERS.BULK_UPDATE | POST /vouchers/bulk/async |
VOUCHERS.METADATA_UPDATE | POST /vouchers/metadata/async |
| ORDERS | |
ORDERS.IMPORT | POST /orders/import |
| METADATA KEY PURGE | |
CAMPAIGNS.METADATA_KEY_PURGE, CUSTOMERS.METADATA_KEY_PURGE, PRODUCTS.METADATA_KEY_PURGE, VOUCHERS.METADATA_KEY_PURGE, ORDERS.METADATA_KEY_PURGE | No API endpoint equivalent. You can perform this action through the Dashboard. See Dashboard documentation: Dashboard > Project Settings |
Improve performance and efficiency
Voucherify optimizes most requests for speed. Average response time on shared clusters:| API call | Response time – median | Response time – p95 |
|---|---|---|
| Stackable Validation | 100 ms | 220 ms |
| Stackable Redemption | 170 ms | 350 ms |
| Qualifications API | 200 ms | 450 ms |
| Create Campaign (100 000 vouchers) | 60 sec | – |
Use efficient API flows
Follow the recommended flows for validation, redemption, and campaign management. Avoid unnecessary round-trips.To learn more about optimized flows, read the Integration processes guide.
Synchronize data when really needed
You can send customer, order, or product data directly in validation or redemption calls. In some cases it’s not needed to create them earlier through the API or imports.Replace polling with webhooks
Use webhooks instead of repeated API requests to check your data. Webhooks don’t count toward API call limits and deliver updates in real time.Client-side API (browser and mobile)
Use the client-side API only when you must expose live validation in a web or mobile app. For example, you want users check a promo code on checkout.SDK and widgets
The Voucherify JS SDK includes methods and components for:- Validation
- Redemption
- Voucher publication
- Subscription forms
Rate limiting
Client-side calls share a global limit per IP address. If the limit is exceeded, the API returns:Client-side settings
Go to Dashboard > Project Settings > Client-side Settings to configure:- Allowed website URLs — list allowed origins. Use
*only in development. - Danger zone options — enable with caution to allow the following directly from a client-side API or SDK:
- Redeeming vouchers (risk: users may change request data)
- Publishing vouchers
- Listing vouchers
- Creating customers (risk: it can expose customer metadata creation to the browser)
- Updating voucher expiration (recommended only for controlled test cases)
- Creating loyalty or referral events
Enable these only if you fully understand the security impact.
Manage API versions
Voucherify releases dated API versions that control the API or webhook behavior, like properties sent in requests and responses. When the API introduces breaking changes, a new dated version is released. However, your project won’t auto-upgrade, so you control when to move. Check your current version in Project Setting > API Version.Backward-compatible changes
Voucherify may:- Add new endpoints or properties
- Add optional parameters
- Change property order
- Change the length or format of object IDs or other opaque strings
- Introduce new webhook event types
Upgrading
- Review the API changelog
- Test the new version in a Sandbox project.
- Click Upgrade to the latest API version when ready.
API changelog
Read the API changelog:- v2017-04-05 (deprecated):
- Responses from the voucher and campaign listing methods were moved to the new object structure. Methods now render specific properties for a total count and an array of objects.
- Introduced validation for listing parameters:
limitandpage. A limit can range between 1 and 100 items. GET voucher/campaignmethods render validation rules related to the voucher object (can be inherited from a campaign).- Created an API method for getting a campaign identified by name.
- v2017-04-20 (deprecated):
- Response from the voucher publish method was moved to the new object structure. Returned voucher details are wrapped by a transaction object describing the publication event:
- v2018-08-01: Introduces a new model for building Validation Rules. The extended mechanism provides advanced configuration for promo conditions. Changes affect these API methods:
List Promotion Tiers: replaced an object describing conditions by a list of records describing an association between rule and tier (validation_rule_assignments).List Promotion Tiers for campaign: same as above.Promotion Tier Object: updated to support new structure.Validation Rule Object: reorganized to handle advanced rules.Validation Rule Assignment Object: added to describe relation between rules and linked promotions.Validation Rules: modified data model.
- Webhooks v2024-01-01: In v20231205, a new version of webhooks was introduced. These webhooks are available for distribution and the events listed in Project settings.

