Publish several of one merchant's submitted vouchers; one audited decision per voucher
Each listed voucher must be submitted, belong to the given merchant and match its expected version. Each is published exactly as in a single review (own savepoint, own audit rows); one that cannot be published is reported with its error and leaves the others untouched. Unless notifyOwner is false, one email per owner lists everything that went live.
Authorization
bearer In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/platform/rewards/publish-submitted" \ -H "Content-Type: application/json" \ -d '{ "tenantId": "f97df110-f4de-492e-8849-4a6af68026b0", "items": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "expectedVersion": 1 } ] }'{ "published": 0, "failed": 0, "results": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "outcome": "published", "error": "string", "status": "string", "version": -9007199254740991 } ]}Admin approves and publishes a submitted offer or requests changes POST
One published signup offer per merchant requires a selected welcome claim policy. General member benefits are independent of that policy. Publication is immutable and immediately visible in the app; requesting changes requires a note. Unless notifyOwner is false, one transactional email tells the merchant owner(s) what was decided; it never delays or blocks the decision.
/v1/platform/team GET
Next Page