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

Legentic Prevent API

Automated claim risk detection for faster investigations

The Legentic Prevent API enables organizations to automatically evaluate incoming insurance claims against predefined business rules configured within the Legentic platform.

Designed for seamless integration into claims workflows, the Prevent API helps insurers, investigators, fraud analysts, and claims handlers identify potentially suspicious or high-risk claims at the earliest possible stage.

When a claim is submitted to the API, Legentic automatically evaluates the claim using configured business rules and returns:

  • Which rules were triggered

  • Severity level of the findings

  • Number of matching records associated with each rule

  • Direct links to investigate the findings inside the Legentic Platform

The Prevent API is commonly used as an automated screening and prioritization tool to help organizations reduce manual investigation work and ensure consistent claim assessment across teams.

Typical Use Cases

  • Claims intake screening

  • Fraud detection workflows

  • Automatic claim prioritization

  • Investigation escalation

  • Risk assessment automation

  • Operational workflow standardization

  • Cross-team investigation support

Example Workflow

  • A new insurance claim is registered

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

  • Legentic evaluates the claim against configured business rules

  • The API returns matching flags, severity levels, and investigation links

  • High-risk claims are automatically escalated for further review

This allows investigators and claims handlers to focus on the claims most likely to require additional attention.

Before You Start

The Prevent API must first be enabled by the Legentic team.

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

Configuration

-> Quick Start tab

The Quick Start section is primarily intended for developers and integration teams, and includes information regarding the:

  • Endpoint documentation

  • Request and response examples

  • Authentication details

  • Integration guidance

  • API testing tools
-> Settings tab

The Settings section allows organizations to view and manage the business rules used during claim evaluation in order to align the API's behavior with their own operational and fraud investigation processes.

Company Admins can:

  • Review configured rules

  • Adjust rule parameters

  • Customize evaluation behavior

  • Filter and organize rules based on internal workflows

-> 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 always be stored securely
-> Usage tab

Usage statistics are available from the Usage tab inside the platform.

Please note:

  • Usage data may have a slight reporting delay

  • Large multi-country searches may increase response times

  • Very broad searches may return larger result sets

Best Practices for Claim Searches

To improve result quality and investigation efficiency:

  • Use exact Identifiers whenever possible -> VINs and license plates usually provide faster searches, more accurate matches and a better investigative precision

  • Include relevant claim information -> adding contextual claim information such as claim dates, claim amounts and claim types allows for more business rules to be evaluated and can improve the quality of the results.

  • Avoid overly broad country searches -> using specific country filters generally provides faster responses, more relevant findings and better operational performance; searching across all available countries may increase response times and result volume.

  • Retry searches if necessary -> when both VIN and license plate are included, the Prevent API currently requires both identifiers to appear in the same underlying document; if no results are returned, try searching again using only one identifier.

Understanding the Results

The Prevent API organizes findings into severity categories to help prioritize claim reviews.

-> Flag - Higher-severity findings that may require immediate investigation or escalation.

-> Inform - Lower-severity or contextual findings that may still provide useful investigative insight.

Each result also includes:

  • A description explaining why the rule triggered

  • Number of matching findings

  • A direct link to investigate the associated results inside the Legentic Platform

Frequently Asked Questions

-> Does the Prevent API automatically investigate claims?

No. The Prevent API evaluates claims against predefined business rules and returns indicators and investigative links to support decision-making.

-> Do I need both VIN and license plate?

No. Only one identifier is required. Providing both identifiers may narrow the search because both must match within the same underlying record.

-> 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 countries your organization has access to.

-> What happens if no rules are triggered?

The API will still return a successful response, but no findings or rule matches will be included.

-> Who can manage API credentials?

Only Company Admins can create or manage API keys.

Support

If you need assistance with:

  • API access

  • Integration setup

  • Business rule configuration

  • Search optimization

  • Troubleshooting

  • Workflow recommendations

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

When contacting support, it may be helpful to include:

  • Request timestamps

  • Claim or case IDs

  • Error messages

  • Example requests or responses