LeadFlags
leadflags.com
- Web
- API
What LeadFlags is
LeadFlags is a deterministic lead-scoring API and web service that filters questionable inbound leads before they reach a CRM or call queue. It applies predefined rules and returns a score, quality level, risk flags, positive signals, and a recommended action. The same input produces the same output, with no AI, enrichment, or profiling. JSON requests use a flexible schema, recognize field aliases, and allow mapping overrides for unusual keys. The service can flag missing or invalid contact details, disposable email, suspicious messages, and inconsistent fields. LeadFlags describes itself as CRM-agnostic, with HubSpot and Salesforce among its examples. Requests require an X-API-Key header; Bearer authorization is not supported. Starter costs €39 a month for up to 1,000 leads, Growth €99 for 10,000, and Scale €249 for 50,000. Enterprise uses custom billing and terms; annual billing offers a 20% discount.
Who it suits
LeadFlags suits marketing agencies, call centers, and lead sellers or buyers needing consistent rule-based scoring. It can sit before a CRM or other workflow.
Good to know, and what to watch
- Deterministic rule-based scoring
- Flexible JSON input and field aliases
- Returns routing recommendations and risk flags
- CRM-agnostic API
- Enterprise IP allowlist available
- No AI or predictive scoring
- Bearer authorization is not supported
- Starter limit is 1,000 leads monthly
- Enterprise pricing uses custom terms
Plans
Every plan and priceEnterprise
Starter
Growth
Scale
The verdict
LeadFlags offers predictable screening outputs for inbound-lead routing without profiling or AI. Confirm its rate limits, authentication method, and monthly lead volume before choosing a plan.
What the maker publishes
- API access
- API requests use JSON and require an X-API-Key header; the docs say Bearer authorization is not yet supported. source
- Authentication
- API requests require an X-API-Key header obtained from the dashboard. source
- Bearer limitation
- Bearer authorization is documented as coming soon; X-API-Key is currently the supported method. source
- CRM positioning
- LeadFlags describes itself as CRM-agnostic and intended to sit before any CRM, call center or workflow. source
- Cross-field checks
- The API can flag mismatches such as name versus email, email domain versus website and source versus email type. source
- Custom thresholds
- Enterprise requests can pass mid and low query parameters to customize score cutoffs. source
- Deterministic scoring
- The documentation says identical input produces identical output using predefined, transparent rules. source
- Enterprise controls
- Enterprise plans list an IP allowlist, dedicated SLA and support, and custom score thresholds. source
- Features
- LeadFlags identifies signals such as missing or invalid contact details, disposable email, suspicious messages, and inconsistencies between fields. source
- Flexible input
- The API accepts JSON without a fixed schema, recognizes field aliases, and allows optional mapping overrides for nonstandard keys. source
- Flexible schema
- The API accepts arbitrary JSON without a fixed schema and detects fields through aliases. source
- Independent design
- The About page says the service operates independently from CRMs and marketing tools. source
- Integrations
- LeadFlags describes itself as CRM-agnostic and says it can be used before any CRM or workflow; the site mentions HubSpot and Salesforce as examples. source
- Intended users
- The site names marketing agencies, call centers, and lead sellers and buyers as audiences for consistent lead scoring. source
- IP allowlist
- Enterprise can restrict accepted API traffic to authorized IP addresses. source
- JSON API
- The service exposes POST /api/score-lead and requires JSON request bodies. source
- Limit: API authentication
- Integrators cannot currently use Bearer authorization because the documentation says it is not yet supported. source
- Limit: no published licence
- The opened official documentation and About pages do not state an open-source licence or self-hosting option. source
- Limit: support guarantee
- The docs state ordinary email support has no guaranteed response time. source
- LinkedIn audience signal
- The public LinkedIn LeadFlags page showed one follower when the post was indexed. source
- LinkedIn launch
- LeadFlags’ LinkedIn post announces that the product is live as a deterministic lead-quality scoring API. source
- LinkedIn lock-in claim
- The launch post describes the service as having no CRM lock-in. source
- LinkedIn output
- The launch post says results include a normalized score, quality level, explanatory flags and a recommended action. source
- LinkedIn schema claim
- The LinkedIn post says the API has no fixed schema for inbound lead data. source
Checked against the maker's pages on 15 Oct 2026.