Leverage Propexo's webhooks to get updates that you care about.
Many of our customers use webhooks to get updates on events like lease status changes, new leads, and more. We offer webhook events for new and changed data for all of our data models, job statuses and more.
Why use webhooks?
Webhooks are a way to integrate with Propexo so you know about changes to your data in real-time. Instead of polling the API for changes, you can register a webhook and we'll send you a notification when something changes. You can subscribe to changes on a per-data model basis, so you are only notified when the data you care about changes.
How do webhooks work?
You set up a URL on your system that we will send a POST request to when something changes. We will send you a JSON payload with the data that changed. You can then use that data to update your system.
The above example is intended to be a simple example of how webhooks work. In practice, you will want to use a more robust system to receive and process webhooks. For example, you would probably want to use a queueing system to ensure that you don't lose any webhook events if your system is down.
Then, in Propexo, you can register your webhook URL and subscribe to the events you care about ("Data Update" on the
leases model in this example).
Now each time Propexo identifies a change in the leases model for a particular lease in your integration, you will be notified via a POST request to your webhook URL.
Below is an example of how Propexo might send a webhook request to your system. Note, this is a simplified payload for the example and is not intended to represent a complete webhook payload.
Important Note for the DATA_NEW event
When you subscribe to a
DATA_NEW webhook event, it is automatically disabled until your integration has finished its first full data sync. This is to prevent you from receiving a flood of events when you first set up your integration. After the first full sync, the
DATA_NEW event will be enabled and you will receive a webhook event for every new record that is created in the model to which you are subscribed.
Oftentimes Propexo needs to fully hydrate data over more than one request to a Property Management System. For example, several integrations provide a minimal set of data for residents, applicants, or leads. The minimal dataset might only include an ID and name. We then need to make a subsequent request to retrieve additional information like phone and email. In these cases, you should fully test to ensure that you are receiving all of the data you need with the subscribed webhook event. Some customers only need to subscribe to the
DATA_NEW event, others may want to subscribe to the
DATA_UPDATE event as well.
Optionally, many customers use webhooks as a notification system and then query the associated API endpoint to retrieve a full data record. For example, you may subscribe to the
DATA_UPDATE event for the
leases model. When you receive a webhook event, you can then query the
/leases/:id endpoint to retrieve the full lease record.
Propexo signs every webhook payload. This signature is sent in the
propexo-signature header. You can use this signature to verify that the webhook was sent by Propexo and not a malicious third party.
The secret that is used to sign the payload is available in your integration settings. You can find it by going to the "Webhooks" page in the Propexo dashboard and clicking on the "Settings" button.
Here is an example of how you might verify the signature in Node.js: