Restrict Client-Side Reward Sending
Send Rewards (Server)
Restrict Client-Side Reward Sending
Disable client-side SendReward calls by adding an API version blocklist entry to enforce server-only rewards.
POST
Restrict Client-Side Reward Sending
Block client-side
SendReward calls by adding an API version blocklist entry to your Rewards App.
This step is optional but highly recommended for apps with high-value rewards or when you need complete control over reward issuance.
Configuration
Header Parameters
string
required
Client identifier (use
“developer-dashboard” )string
required
Bearer token for authenticationFormat:
Bearer {JWT_TOKEN}Path Parameters
string
required
Your Rewards App ID
Body Parameters
number
required
API version to blocklistUse
1 to block client SDK calls (to block Send Reward v1)string
required
The API route to blocklistUse
“/earn/limited-achievement/reward” to block client reward sendingResponse Fields
Response Status Codes
What Happens After Restriction?
After applying this blocklist:Client SDK Blocked
Client SDK calls to send rewards will be rejected
Backend Server Active
Server calls with API key will continue to work
Client SDK Behavior
When a client tries to send rewards via v1 after the blocklist is applied:Server Behavior
Your backend server can continue sending rewards normally using the v2 endpoint with your API key.Code Examples
You only need to create a single block list entry with version 1 to disable client-side rewards. To re-enable client rewards, simply delete that block list entry.
You can remove the blocklist entry at any time to re-enable client-side reward sending by deleting the blocklist entry.
What’s Next?
You’ve now restricted client-side reward sending and enforced backend-only control. Next, manage and secure your Rewards App:- Manage via Dashboard — Create, list, and revoke API keys for your Rewards App.