Using FormClue’s Consent API to Pre-Screen Leads for Compliance

When you buy leads, speed matters. But compliance matters more.

Many sophisticated buyers don’t immediately accept every lead that arrives. Instead, they perform a quick compliance check before ingesting the lead into their system. One of the most powerful ways to do this with FormClue is by querying the certificate’s detected consent language and verifying that required disclosures are present and agreed to.

This post walks through why this matters, when to use it, and how to implement simple keyword validation using the FormClue Consent API.

Why check consent language before accepting a lead?

In many verticals, it’s not enough that a user simply submitted a form. Buyers often require proof that specific language was shown and agreed to, such as:

• Your company name
• TCPA or SMS disclosure language
• Partner marketing language
• State-specific compliance text

FormClue already detects consent blocks during the certified session. By calling the Consent API in real time, you can programmatically verify whether the required language was present and agreed to before you accept the lead.

Think of it as an automated compliance gate.

Common scenarios where this API is valuable

Different buyers use this endpoint in different ways. Here are some of the most common real-world use cases.

Company name verification

Some buyers require that their exact company name appear in the consent language. This is especially common in co-registration and marketplace environments.

Before accepting the lead, the buyer checks:

• Does the consent text contain our brand name?
• Did the user actually agree to that block?

If not, the lead can be rejected or flagged for review.

SMS and TCPA compliance checks

This is one of the biggest use cases.

If you are sending text messages, you may need to confirm that language like:

“You agree to receive recurring automated marketing text messages…”

was shown and accepted.

With FormClue’s consent endpoint, you can automatically scan the detected consent text for required SMS language and confirm the checkbox was actually checked.

Publisher quality enforcement

Networks and buyers often work with multiple publishers. Not all of them implement forms perfectly.

By validating consent dynamically, you can:

• Catch missing disclosures
• Detect unchecked required boxes
• Identify publishers who are out of compliance

This gives you leverage and protects your downstream campaigns.

Conditional lead acceptance

More advanced buyers use consent checks as part of their lead routing logic.

For example:

• If compliant → accept lead
• If missing required language → reject lead
• If ambiguous → send lead to manual review

This keeps your pipeline clean without slowing down lead flow.

How the Consent API works

FormClue exposes detected consent blocks via:

https://docs.formclue.io/#/?id=get-certificate-consent-language

You simply pass the certificate ID that came with the lead:

GET https://api.formclue.io/v1.0/clientapi/consent/{certificate_id}

The response includes an array of consent blocks, each containing:

• consent_type
• agree
• text

Here is what a typical certificate consent API response looks like:

{
  "msg": "ok",
  "consent": [
    {
      "consent_type": "checkbox",
      "agree": true,
      "text": "I agree to receive marketing communications from ABC Corp...."
    },
    {
      "consent_type": "clickwrap",
      "agree": true,
      "text": "By clicking Submit, you consent to our Terms and Privacy Policy...."
    },
    {
      "consent_type": "checkbox",
      "agree": false,
      "text": "I agree to receive recurring automated text messages from...."
    }
  ]
}

In this example:

• The first checkbox was checked and contains marketing consent language.
• The clickwrap block indicates implied consent by proceeding.
• The final checkbox was not checked, which could make the lead non-compliant for SMS use cases.

This is exactly the data your system can evaluate before deciding whether to accept the lead.

From there, your system can inspect the text and make a compliance decision.

Example workflow

A typical real-time flow looks like this:

1. Lead arrives from publisher
2. Extract the FormClue certificate ID
3. Call the Consent API
4. Search consent text for required keyword
5. Verify agree = true
6. Accept or reject the lead

This entire process usually takes milliseconds.

Simple keyword matching example (Node.js)

Below is a basic example showing how you might verify that the phrase “receive text messages” appears in an agreed consent block.

async function isLeadCompliant(certificate_id, api_key) {
    const response = await fetch(
        `https://api.formclue.io/v1.0/clientapi/consent/${certificate_id}`,
        {
            method: 'GET',
            headers: {
                'api_key': api_key,
                'Content-Type': 'application/json'
            }
        }
    );
    const data = await response.json();
    if (data.msg !== 'ok') {
        throw new Error('Consent API error');
    }
    const required_keyword = 'receive text messages';
    const match_found = data.consent.some(block => {
        return (
            block.agree === true &&
            block.text.toLowerCase().includes(required_keyword)
        );
    });
    return match_found;
}

How it works

The function:

• Pulls consent blocks from FormClue
• Loops through each block
• Checks that the user agreed
• Searches for your required phrase
• Returns true or false

From there, your lead ingestion system can decide whether to accept the lead.