Deleting a blocklist entry immediately re-enables client-side reward sending for that API route. Make sure you understand the security implications.
Reversible Action. You can always add the blocklist entry back if you need to restrict client-side rewards again.
Configuration
Header Parameters
Client identifier (use
“developer-dashboard” )Bearer token for authenticationFormat:
Bearer {JWT_TOKEN}Path Parameters
Your Rewards App ID
The ID of the blocklist entry to delete
Get this ID from the “Get Blocklist Entries” endpoint
Response Fields
| Field | Type | Description |
|---|---|---|
success | boolean | Whether the deletion was successful |
message | string | Confirmation message |
Response Status Codes
| Code | Description |
|---|---|
200 | Blocklist entry deleted successfully |
400 | Bad request - invalid UUID |
401 | Unauthorized - authentication required |
403 | Forbidden - developer does not own this app |
404 | Blocklist entry not found |
500 | Internal server error |
Code Examples
What Happens After Deletion?
Before Deletion Client SDK Blocked
Client cannot send rewards
After Deletion Client SDK Enabled
Client can send rewards again
Try It Out
Ready to delete a blocklist entry? Use our API playground on the right to test with your JWT token.What’s Next?
Now that you’ve managed your blocklist entries, you can move on to managing your API keys:- Manage API Keys. View, list, or revoke API keys used for backend authentication.