Skip to main content
DELETE
/
api
/
v1
/
rewards
/
app
/
{rewardsAppId}
/
api-version-blocklist
/
{blocklistId}
Delete Blocklist Entry
curl --request DELETE \
  --url https://api.zebedee.io/api/v1/rewards/app/{rewardsAppId}/api-version-blocklist/{blocklistId} \
  --header 'Authorization: <authorization>' \
  --header 'z-client: <z-client>'
{
  "success": true,
  "message": "API version blocklist deleted successfully."
}
This operation re-enables client SDK access for the specified API route that was previously blocked.
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

z-client
string
required
Client identifier (use “developer-dashboard” )
Authorization
string
required
Bearer token for authenticationFormat: Bearer {JWT_TOKEN}

Path Parameters

rewardsAppId
string
required
Your Rewards App ID
blocklistId
string
required
The ID of the blocklist entry to delete Get this ID from the “Get Blocklist Entries” endpoint
{
  "success": true,
  "message": "API version blocklist deleted successfully."
}
{
  "success": false,
  "message": "Invalid UUID"
}

Response Fields

FieldTypeDescription
successbooleanWhether the deletion was successful
messagestringConfirmation message

Response Status Codes

CodeDescription
200Blocklist entry deleted successfully
400Bad request - invalid UUID
401Unauthorized - authentication required
403Forbidden - developer does not own this app
404Blocklist entry not found
500Internal server error

Code Examples

const rewardsAppId = 'YOUR_REWARDS_APP_ID';
const blocklistId = 'YOUR_BLOCKLIST_ID';
const jwtToken = 'YOUR_JWT_TOKEN';

async function deleteBlocklistEntry(rewardsAppId, blocklistId) {
  const response = await fetch(
    `https://api.zebedee.io/api/v1/rewards/app/${rewardsAppId}/api-version-blocklist/${blocklistId}`,
    {
      method: 'DELETE',
      headers: {
        'z-client': 'developer-dashboard',
        'Authorization': `Bearer ${jwtToken}`
      }
    }
  );

  const data = await response.json();

  if (data.success) {
    console.log('✅ Blocklist entry deleted successfully!');
    console.log('Client-side rewards are now enabled.');
    return data;
  } else {
    throw new Error(`Failed: ${data.message}`);
  }
}

// Delete entry
await deleteBlocklistEntry(
  'b28e0306-2c06-4092-8d56-a1623d6b97fb',
  'bb6178d1-4fb5-4b35-93d6-31fe052b73dd'
);

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.