Reward Unit Configuration. The reward unit (e.g., 1 satoshi or $0.10) is defined for your game by your ZBD Customer Success Manager.
Configuration
Header Parameters
API key used for authentication. Obtain this from the Create an API Key step.
Client identifier (use
“developer-dashboard” )Content Type
Body Parameters
The recipient’s ZBD Rewards User ID
Reward amount in configured unitsExample:
10 (units defined by your ZBD Customer Success Manager)Response Status Codes
| Code | Description |
|---|---|
201 | Reward sent successfully |
400 | Bad request – invalid parameters |
401 | Unauthorized – invalid or missing API key |
404 | Rewards user not found |
500 | Internal server error |
Response Fields
| Field | Type | Description |
|---|---|---|
success | boolean | Whether the request was successful |
message | string | Response message |
data | array | Array containing transaction details |
transactionId | string | Unique transaction identifier |
Security Reminder, Never expose your API key in client-side code. Always send rewards from your backend server where your API key is securely stored.
Code Examples
Try It Out
Ready to send your first reward from the server? Use our API playground on the right to test with your API key.What’s Next?
You’ve now successfully sent rewards from your backend using the ZBD Rewards API (v2).Next, continue enhancing your reward flow and security:
- Restrict Client-Side Rewards. Block client SDK reward calls to enforce server-only reward issuance.
- Manage API Keys. View and revoke API keys to maintain secure backend authentication.
- Manage Blocklist Entries. Review or remove blocklist entries to adjust client access when needed.