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

Legentic Locate API

Automated detection of lost or stolen vehicles across continuously updated data sources

The Legentic Locate API enables organizations to automatically monitor lost or stolen vehicle cases against Legentic’s continuously refreshed investigative data.

Designed specifically for post-claim and recovery workflows, the Locate API helps insurers, investigators, recovery teams, and fraud specialists identify whether missing vehicles reappear in online listings or shipping records.

When a case is submitted to the API, Legentic evaluates the vehicle identifiers against predefined Locate business rules and returns:

  • Which rules were triggered

  • Severity level of the findings

  • Number of matching records

  • Relevant document information

  • Direct links to investigate the findings inside the Legentic Platform

Unlike one-time manual searches, the Locate API supports ongoing monitoring and detection workflows, helping organizations react quickly when vehicles reappear in external data sources.

Typical Use Cases

  • Stolen vehicle recovery workflows

  • Post-claim monitoring

  • Fraud investigation support

  • Asset recovery operations

  • Shipping and export monitoring

  • High-risk case escalation

  • Continuous vehicle tracking workflows

Example Workflow

A vehicle theft or loss case is registered ->

-> The organization submits the case to the Locate API

-> Legentic continuously evaluates the vehicle against updated data sources

-> The API detects matching listings or shipping records

-> Investigators receive alerts and direct investigation links

-> Recovery or escalation processes can begin immediately

This allows organizations to react faster when missing vehicles reappear in external marketplaces or transportation records.

Before You Start

The Locate 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 inside the platform includes:

  • Endpoint documentation

  • Request and response examples

  • Authentication details

  • Integration guidance

  • API testing tools

This section is primarily intended for developers and integration teams.

-> Settings tab

The Settings section allows users to review the business rules used for Locate workflows, which can determine how missing vehicles are detected across supported data sources.

-> 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

  • Broad searches may return larger result sets

Best Practices for Locate Searches

To improve result quality and recovery efficiency:

-> Use VIN and license plate together whenever possible - providing both identifiers can significantly improve matching capabilities and increase the likelihood of detecting relevant records.

-> Use relevant country filters - this can help improve the search precision, operational performance and relevance of results; searching across all accessible countries may increase response times and result volume.

-> Re-run searches regularly - regular re-execution of searches is strongly recommended for active recovery cases; as Legentic indexes new data continuously, if no matches are found in an intial search, relevant records may still appear later as new listings or shipping records are indexed.

-> Include case information - contextual information such as case dates, case type, claim or recovery details can help support internal workflows and improves collaboration across teams.

Understanding the Results

The Locate API returns structured findings when matching records are detected. These may include:

  • Vehicle sale listings

  • Shipping records

  • Publication dates

  • Vehicle pricing information

  • Source domains

  • Shipping origin and destination countries

Each result also includes:

  • A rule description explaining why the match was triggered

  • Number of matching records

  • A direct investigation link inside the Legentic Platform

Shipping Data Detection

The Locate API can also detect vehicles appearing in shipping records. This can help organizations identify potential international movement, export activity, or cross-border transportation involving missing vehicles. Shipping-related findings may include:

  • Origin country

  • Destination country

  • Shipment timestamp

Frequently Asked Questions

-> Does the Locate API continuously monitor vehicles?

The API evaluates searches against continuously refreshed Legentic data sources. Organizations are encouraged to re-execute searches regularly for active cases.

-> What kind of data can Locate detect?

  • Online sale listings

  • Marketplace advertisements

  • Shipping and transportation records

depending on the business rules configured for your organization.

-> Do I need both VIN and license plate?

No. Either identifier can be used.

However, providing both identifiers can improve matching capabilities and detection accuracy.

-> Can I search multiple countries at once?

Yes. Multiple country codes can be included in a request.

You can also use ["*"] to search across all countries your organization has access to.

-> What happens if no matches are found?

No findings simply means no matching records were detected at the time of the search.

Because new data is indexed daily, matches may still appear later.

-> Are all findings treated as high priority?

Currently, Locate findings are generally treated as high-severity because they may indicate the reappearance or movement of a missing vehicle.

Support

If you need assistance with:

  • API access

  • Integration setup

  • Locate workflow configuration

  • Recovery monitoring strategies

  • Search optimization

  • Troubleshooting

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

When contacting support, it may be helpful to include:

  • Request timestamps

  • Case IDs

  • Error messages

  • Example requests or responses