Skip to main content
DELETE
/
api
/
blocked-companies
/
by-id
/
{id}
Remove a blocked company by record ID
curl --request DELETE \
  --url https://app.puffle.ai/api/blocked-companies/by-id/{id} \
  --header 'Authorization: Bearer <token>'
{ "success": true }

​
Overview

Removes a row from blocked_companies matching user_id + id. Use this when the entry has no domain (name-only) and therefore can’t be addressed via /api/blocked-companies/{domain}. Delete is a no-op at the database level when no row matches — the response is still { success: true }. Because the query is scoped to user_id, another user’s id silently matches nothing.

​
AI agent notes

Idempotent. Safe to call repeatedly. Non-existent and cross-user ids both silently return 200 — no way to distinguish “deleted” from “nothing matched”.When to use this over delete-by-domain. Always for name-only entries. Prefer it for domain entries too if you have the row id — avoids URL-encoding edge cases.Listing to find the id. Call listBlockedCompanies to discover id values before deleting.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
id
string<uuid>
required

Blocked company row UUID.

Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$

Response

Delete issued. Returns { success: true } whether or not a row was actually removed.

​
success
enum<boolean>
required
Available options:
true