Entrata Lead Deduplication Behavior

Last updated: November 6, 2025

When posting leads to Entrata via their API, Entrata automatically performs deduplication checks to prevent duplicate records. Understanding this behavior is critical for successful lead integration.

How Deduplication Works

Entrata checks incoming leads against existing records using two key identifiers:

  • Email address

  • Phone number

If a lead already exists in the system with a matching email address or phone number, Entrata will perform deduplication.

API Response Behavior

When a duplicate is detected, Entrata exhibits the following behavior:

  • Returns a 200 (success) HTTP response code

  • Does not create a new lead record

  • Does not update the existing lead record

  • Does not return an error message indicating duplication

Important: A 200 response does not guarantee that a new lead was created. It only indicates that the API request was processed successfully.

Resolution Steps

Entrata’s API does not currently offer a built-in method to automatically resolve duplicate conflicts. We understand this can create friction in your workflow, and we share your frustration. Our team continues to look for ways to make this process more efficient and reduce manual effort where possible.

When a lead sync fails due to deduplication, you'll need to work with your customer to resolve the conflict directly in Entrata:

  1. Identify the conflicting record - Locate the existing lead in Entrata that has the matching email or phone number

  2. Coordinate a resolution - Work with your customer to determine the best approach, which typically involves deleting or modifying the existing record in Entrata's interface

  3. Retry the sync - Once the conflict is resolved, retry posting the lead through Propexo

  4. Verify the result - Confirm the new lead was successfully created in Entrata