External Event: Create Reward
Issues reward cards driven by external-events campaigns — used when an outside system (CRM, app, e-mail) decides when and how much to reward, and Guper just creates the cards under the campaign's identity (validity, tags, sequence, messaging).
The campaign supplies the structure; the request body supplies the value.
Internally the call overrides the campaign's aliquot with the value
you send, so each entry in campaigns[] produces exactly one reward card
of the requested amount. Optional startsAt / expiresAt per entry
override the default availability window of the resulting card.
Accepts a single campaign object { id, value } or an array of objects
— a single object is auto-wrapped.
Try-it values populated from environment ACME (Demo)
Authentication
Token
Send your user token in the x-guper-authorization header. Endpoints that
support a Public mode (e.g. acúmulo and resgate previews) accept the same
request without the header — Private mode adds customer data and a
confirmation token to the response.
Headers
Request body
Content-Type:
application/json