Campaigns
Issue Rewards
Issue rewards to users for a campaign variant
POST
Scope required:
rewards.issue202 Accepted response containing the issuance
job details. Use the
Get Issuance Job endpoint to poll
for completion status.
Best Practices for Event-Driven Workflows
While there is nothing preventing you from issuing rewards one user at a time, we strongly recommend batching identifiers into a single request whenever possible. Sending individual requests per user is significantly less efficient and may result in rate limiting under the global rate limits. Collect identifiers and submit them in batches of up to 10,000 per request for optimal throughput.Idempotency
This endpoint supports idempotent requests via theX-Idempotency-Key
header. When provided, duplicate requests with the same key return the
cached response from the original request. If the request body differs
from the original, a 422 Unprocessable Entity error is returned.
Parameters
Campaign ID
Merchant ID
Variant ID. Must belong to the specified campaign.
Array of user identifiers to issue rewards to (max 10,000)
Optional idempotency key to prevent duplicate issuance jobs.
Response
Returns202 Accepted with the issuance job object.
Issuance job ID
Campaign ID
Variant ID
Job state:
pending, processing, completed, or failedTotal number of identifiers submitted
Number of identifiers processed so far
Number of rewards successfully issued
Number of failed issuances
Completion percentage (0-100)
Job creation timestamp (ISO8601)
Processing start timestamp (ISO8601), null if not started
Processing completion timestamp (ISO8601), null if not completed