REA Ignite is a powerful platform built to streamline property campaigns and elevate agency performance. From insights to mobile access, it empowers agents to work smarter and connect faster. This article will cover how to enable the Ignite integration.
How is the integration setup?
If a client wants REA Ignite applications to load into their Reapit Lettings account, they will just need to integrate their REA Ignite account with us. REA have provided the article below to help their clients connect their applications to their chosen CRM (Reapit Lettings / Inspect Real Estate).
Please see - How do I set up my CRM with Rental Applications in Ignite?
How does it work, and what is sent to Reapit Lettings?
Once the client has followed the steps outlined in the article provided by REA, we will begin receiving applications from Ignite via their API.
From the API, we receive the following limited data:
Applicant’s details
Application details
Number of pets
URL to view the application in Ignite
Listing details
How do statuses work with Ignite Applications?
When we receive the application for the first time from the REA application API, we will map the API application status (PUBLISHED/VIEWED/SUCCESSFUL/UNSUCCESSFUL/WITHDRAW) to a status within the client’s Reapit Lettings account. The statuses that are used are based on the ‘External Status’ of the client's status event.
We will map the following REA API statuses to the following IRE ‘External Status’.
REA API Status: PUBLISHED = IRE External Status: “Received” or “Processing”
REA API Status: SUCCESSFUL = IRE External Status: “Approved” or “Accepted”
REA API Status: WITHDRAW = IRE External Status: “Withdrawn”
REA API Status: UNSUCCESSFUL = IRE External Status: “Declined”
Important information below on status updates with REA Ignite Applications
Now as we can receive the status, we can also send updates to REA Ignite when the application status in Reapit Lettings is updated.
One issue with statuses is that REA Ignite has lots of types of status names that clients can update their application to, but the response in the API is extremely limited as the REA application API will only contain the following status names - PUBLISHED/VIEWED/SUCCESSFUL/UNSUCCESSFUL/WITHDRAW and this is all we can use to map these names to a status within Reapit Lettings.
Another issue is that there is a type of status in Ignite for “Waiting Payment”, and if the application in Ignite is updated to this status we receive the status name as “SUCCESSFUL” which will then map to the below external names.
IRE External Status: “Approved”
IRE External Status: “Accepted”
This can be a big issue for clients as the above ‘External Status’ is against the default “Paid” status in Reapit Lettings, which can trigger status rules within the account. Unfortunately, we do not know how many statuses are in Ignite and what API status name they are mapped to as well as there isn’t a specific API status name for their type of waiting payment status that we might be able to differentiate and map to a possible new ‘External Status’.