Native delivery connection

Boberdoo suppression, delivered the moment an opt-out is verified.

revoq owns the whole Boberdoo request shape. You supply your account's API address and API key; revoq adds each verified number to your block list and keeps the reply as evidence.

Book a revoq Readiness Review All delivery connections

What happens on a verified opt-out

One suppression call, one evidence record

The suppression call

revoq sends a GET request to your Boberdoo API address using theblockListValueInsert action, with the consumer's number as ten digits and your sealed key as the Key parameter. Nothing else about the consumer is sent.

The evidence record

Every attempt stores the request shape used, the configuration revision and credential version it was signed with, the sanitized reply from Boberdoo, and how revoq interpreted that reply — success or failure.

The number is only sent after revoq has verified the consumer's phone number by one-time code.
Boberdoo answers with HTTP 200 even when the key is wrong, so revoq reads the reply body: a reported error is always recorded as a failure.
Delivery counts as complete only when Boberdoo reports a success status.
Failed attempts are retried automatically with increasing spacing, up to a bounded number of attempts.

Setup

Two values from you, the rest is pre-built

In revoq, add a delivery connection and choose Boberdoo.
Paste your Boberdoo API address. Every account has its own — copy it from your Boberdoo API settings; it usually ends in /new_api/api.php.
Enter your Boberdoo API key. It is encrypted on save and never displayed back in full.
Choose coverage: every website, or a specific set of websites and channels (calls, texts, or both).
Run a destination test from revoq's servers using a test number you choose, then read the sanitized reply and revoq's interpretation of it.
Activate. The connection cannot go live without a passing test, and a later change to the address pauses it until it is tested again.

Details

What the connector does and does not do

Action: blockListValueInsert, sent as a GET request with a JSON reply.
Phone format: Ten digits, national format, with no punctuation.
Authentication: Your API key, sealed in revoq and sent as the Key query parameter.
Channels: Calls and texts. One connection can serve both or a single channel.
Confirmation lookups: Not supported by this connector. Proof of suppression comes from the recorded Boberdoo reply, not from a follow-up query.
LeadPortal accounts: LeadPortal runs on Boberdoo, so LeadPortal accounts use this same connector.

Have your Boberdoo API address and key ready, and the connection can be live and tested in the same session.

Book a revoq Readiness Review How revocation is captured and proven