Skip to content
English
legentic.com
  • There are no suggestions because the search field is empty.

Legentic Scan API

Fast investigative screening for automated workflows

The Legentic Scan API enables organizations to quickly determine whether relevant investigative data exists in the Legentic platform — without retrieving full records upfront.

Designed for speed and automation, the Scan API helps insurers, investigators, fraud analysts, and compliance teams perform lightweight investigative checks directly from their own systems and workflows.

By sending a search query such as a license plate number, VIN, phone number, email address, or name, the API returns:

  • The number of matching records found

  • Search execution information

  • A direct link to investigate the results in the Legentic Platform

The Scan API is commonly used as an early-stage filtering and triage tool to identify cases that may require deeper investigation and can be very useful in workflows where rapid screening and prioritization are important.

Typical Use Cases

  • Claims intake screening

  • Fraud detection workflows

  • Automated background checks

  • Investigation triage

  • High-volume monitoring processes

  • Internal risk assessment automation

Example Workflow

  • A new insurance claim is submitted

  • The insurer’s system automatically triggers a Scan API request

  • Legentic checks for related investigative data

  • The API returns a match count and investigation link

  • Suspicious or high-risk cases are escalated for review

This allows analysts to focus on the cases most likely to require deeper investigation.

Before You Start

The Scan API must first be enabled by the Legentic team. In order to receive access, please first contact our Support team at support@legentic.com.

Configuration

-> Quick Start tab

The Quick Start section inside the platform includes endpoint documentation, request&response schemas and authentication examples.

-> Credentials tab

All API requests require an API key which can be generated from the Credentials tab.

Important notes:

  • API keys become active immediately after creation

  • Only Company Admins can create or manage credentials

  • API keys should be stored securely and never exposed publicly

-> Usage tab

Usage statistics are available in the Usage tab within the platform.

Please note:

  • Usage data may have a slight reporting delay

  • Large multi-country searches may increase response times

  • Excessively broad searches may return very large result sets

Best Practices for Searches

To improve result quality and investigative efficiency:

-> Use Exact Identifiers Whenever Possible

Exact identifiers (like License plates, VINs, Phone numbers and Email addresses) usually provide:

  • Faster searches

  • More precise results

  • Fewer false positives

-> Combine Multiple Contextual Clues

Combining identifiers with:

  • Locations

  • ZIP codes

  • Cities

  • Vehicle descriptions

can significantly improve result relevance.

-> Avoid Overly Broad Searches

Broad free-text searches may return:

  • Very large result sets

  • Unrelated matches

  • Longer response times

Example:

  • "search_term": "Audi" - this is usually too broad to be operationally useful.

-> Use Date and Price Filters for Claims Investigations

Publication date and price filters can help identify:

  • Relevant timelines

  • Value inconsistencies

  • Suspicious activity patterns

Frequently Asked Questions

-> Does the Scan API return the full records?

No. The Scan API is intentionally lightweight and only returns:

  • Match counts

  • Search metadata

  • A direct investigation link

-> Can I search multiple countries at once?

Yes. Multiple country codes can be included in the request. You can also use: ["*"] to search across all accessible countries.

-> Why am I getting too many results?

This can usually caused by:

  • Broad free-text searches

  • Missing filters

  • Generic identifiers

Try:

  • Adding contextual information

  • Using structured identifiers

  • Applying country/date filters

-> Why am I getting no results?

Possible causes include:

  • Overly restrictive searches

  • Incorrect identifiers

  • Limited country filters

  • No matching investigative data

Try broadening the search slightly or adjusting filters.

Support

If you need assistance with:

  • Search strategy optimization

  • Query design

  • Integration setup

  • Troubleshooting

  • API access

please contact the Legentic Support team, at support@legentic.com

When reaching out to support, it is helpful to include:

  • Request timestamps

  • Case IDs

  • Request payloads

  • Error messages

  • Relevant response examples