You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
Entrata CRM API Integration
print icon

The Entrata API uses the following required items to send lead information to the Entrata system.


Function/Property Value
CRM Name- Type Entrata CRM [API]
Integration Type API
Send Lead Yes
Update Lead No*
Create Appointment Yes
Update Appointment No*
Comments  Future Development: Update lead and calendar functionality | Update functionality programmed but not tested or deployed.




Entrata CRM Integration Requirements

Field Name


Conversion Logix Entrata User

  • The Entrata user must create a Conversion Logix user in their Entrata system. This user is required to send Conversion Cloud submissions.

  • Recommended user name: “conversion_logix_api@” After the @ sign is typically the customer's domain name.

Entrata API Access

After the user creates the Conversion Logix user, this user must grant access to the below API calls for the integration to work. The user grants access in Entrata.

  • getProperties

  • getLeadPickLists

  • sendLeads

  • updateLeads


This is created and supplied by Entrata user.

Lead Source Name

  • This is the category or element to categorize a Conversion Cloud lead when injected into the Entrata system.

  • Examples: Specials Banner or Website or even Conversion Cloud Lead


  • This is created specifically for a property or set of properties.

  • This must be supplied by Entrata user.

Property Id

This must be supplied by Entrata user. This is a number. Example: 674579



  • Reuses all fields listed for the HTML Integration: CRM Emails | CC Emails | Reply-to Email

  • Appointment Type: Requested type included in comments if no appointment type field is available.

  • This is a REST API

    • REST stands for REpresentational State Transfer. This is an architectural style for providing standards between computer systems on the web, making it easier for systems to communicate with each other.

    • Systems that follow REST are stateless, meaning that the server does not need to know anything about what state the client is in and vice versa.

0 out of 0 found this helpful

scroll to top icon