Create program
<Info><Badge color="gray">Documentation in progress</Badge>
This documentation is in progress. The parameters, fields, request and response bodies, and other data may be subject to change. If you need more information or you want to share feedback, contact Voucherify support or your Technical Account Manager.
</Info>Creates a new loyalty program. The program can be created with status DRAFT (default) or ACTIVE. When created as ACTIVE, the program must be connected to at least one active card definition and at least one active earning rule (provided via card_definitions and earning_rules arrays), otherwise the request is rejected with 423 Locked (keys missing_active_card_definition / missing_active_earning_rule). Optionally assigns card definitions, earning rules, rewards and tier structures in the same request.
Request body
Example request
{
"validity_hours": {
"daily": [
{
"start_time": "09:00",
"end_time": "17:00"
}
]
}
}Response
Program created. Response includes the ids of resources assigned during creation.
Changes
Changed in 2 of the 62 revisions of this API.15518
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
- ▲
added the new required request property
////new-required-request-property
- ▲
added
subschema #1subschema #2to the///request propertyallOflistrequest-property-all-of-added
- ▲
removed from the
request propertyoneOflistrequest-property-one-of-removed
- ▲
the
///request property type changed fromintegertoobjectrequest-property-type-changed
- ▲
the response's body type changed from
objectto no type for statusresponse-body-type-changed
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
response property
allOf[subschema #2]/card_definitionslist-of-types was widened by adding typesnullto media typeapplication/jsonof response200response-property-list-of-types-widened
- ▲
response property
allOf[subschema #2]/earning_ruleslist-of-types was widened by adding typesnullto media typeapplication/jsonof response200response-property-list-of-types-widened
- ▲
response property
allOf[subschema #2]/rewardslist-of-types was widened by adding typesnullto media typeapplication/jsonof response200response-property-list-of-types-widened
- ▲
response property
allOf[subschema #2]/tier_structureslist-of-types was widened by adding typesnullto media typeapplication/jsonof response200response-property-list-of-types-widened
- ●
removed the request property
///request-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ○
added the new optional request property
////new-optional-request-property
- ○
added the new optional request property
new-optional-request-property
- ○
added
subschema #1to therequest propertyoneOflistrequest-property-one-of-added
- ○
added to the response body
allOflist for the response statusresponse-body-all-of-added
- ○
removed from the response body
allOflist for the response statusresponse-body-all-of-removed
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the non-success response with the status
response-non-success-status-added
This revision also has 292 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲