Batch assign/unassign rewards
<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>Assigns and/or unassigns rewards to/from a program in a single batch. Unassign operations are processed before assign operations. Each reward to assign must include its stock configuration. In strict mode (default) missing rewards or missing assignments cause the whole batch to fail (404 Not Found).
Path parameters
Unique program identifier.
Request body
Response
Batch processing result.
Changes
Changed in 2 of the 62 revisions of this API.13612
- ○
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
- ○
- ▲
the request property
became not nullablerequest-property-became-not-nullable
- ▲
the request property
became not nullablerequest-property-became-not-nullable
- ▲
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
- ▲
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
assignedlist-of-types was widened by adding typesnullto media typeapplication/jsonof response200response-property-list-of-types-widened
- ▲
response property
unassignedlist-of-types was widened by adding typesnullto media typeapplication/jsonof response200response-property-list-of-types-widened
- ●
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
- ●
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
- ○
api operation id
batchProcessRewardsremoved and replaced withbatchProgramRewardAssignmentsapi-operation-id-removed
- ○
request property
list-of-types was widened by adding typesnullto media typeapplication/jsonrequest-property-list-of-types-widened
- ○
request property
list-of-types was widened by adding typesnullto media typeapplication/jsonrequest-property-list-of-types-widened
- ○
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
- ▲