Check new records before they enter
The Delete Act asks you to keep deleting data you later collect on consumers who used DROP. Every hash DROP has sent you joins your suppression list. Send hashes of new records to the screening API, and it returns the ones on that list.
POST /api/v1/screen
{ "checked": 2,
"matches": [
{ "ref": "lead-8812",
"list": "Email",
"workItemId": "WnDUKL8qatXV" } ] }Hashes in, hashes out
Send rows of list name and Base64 SHA-256 hash, standardized the DROP way. The reply lists the rows that match. No identifier in the clear is ever sent.
Keys you control
Owners and admins create screening keys on the screening page, one per pipeline if you like, and revoke any of them at once. We store only a hash of each key.
Built for batches
Up to 50,000 rows per request, so a nightly import can be screened in a handful of calls.
Or in the app
Without code, choose a file of new records on the screening page. It is hashed in your browser and the rows to leave out are listed.
Plans: Growth and Scale. See pricing
Request and response
curl https://caldropcompliance.com/api/v1/screen \
-H "Authorization: Bearer sk_scr_…" \
-H "Content-Type: application/json" \
-d '{"rows": [["Email", "Rn1dQx…base64…="], ["Phone", "c2Vh…base64…="]]}'
→ {"matched": [["Email", "Rn1dQx…base64…="]]}Errors: 401 for a missing or revoked key, 402 if the workspace is not on Growth or Scale, 400 for a malformed body or more than 50,000 rows. The hashing guide explains how to standardize each list before hashing.
Questions
Something else? Write to us and a person answers within one working day.
Why hash on our side?
Which hashes are on the suppression list?
The rest of the product
Answer your next DROP batch on time
14-day trial on every plan. Run the practice batch first if you like.