Enquire CRM API Integration

Matthew Pate

Jun 28, 2021

The Enquire API uses the below-required items to send lead information to the Enquire system.

Benefits
Function/Property	Value
CRM Name- Type	Enquire CRM [API]
Integration Type	API
Send Lead	Yes
Update Lead	No
Create Appointment	Yes*
Update Appointment	No
Comments	Requires validation appointment is created

Enquire CRM API Integration Requirements
Field Name	Description
Portal Id	The Portal ID can have multiple companies included. The Portal ID may not be one company and one Portal ID. A portal ID is a number. Note: Super Administrator: Only the Super Administrator role can access and enter the Portal ID in Company > Settings > Super Admin Settings Support: Users must provide the Portal ID. To support, or direct a user: In the Enquire CRM, users can click "Admin" on the left menu In the URL of the Admin homepage, the Portal/Company ID number is displayed at the end. (https://account.enquiresolutions.com/company/details/*yourCompanyID*).
Conversion Logix Account	In the Enquire CRM, Enquire support must grant access to the Portal ID to the Conversion Logix Account. This allows the Conversion Logix Account to access and send leads generated by The Conversion Cloud® to the Portal ID and matching companies.
Exact Property Name	The exact Property Name is the identification of the company. The ID can be a name, number, or unique ID such as hd. 07 Once the Portal ID is configured within Company Details, the Enquire CRM Configuration will display the Property Name(s) which are available and authorized for the Portal ID.

Notes:

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 - the server does not need to know anything about what state the client is in and vice versa.