[kole78]

Thanks for the questions!

1. Docs for webhooks are located in our app (after login). But a basic outline is that you add your URL, add any custom headers you wish, get the signing key, subscribe to an event and you're off the races. Events that we currently support are Job Success, Job Failure, New Data, Diff Data. Probably the most popular event (as you have alluded to in your next question) is our Diff Data event. The payload for this event will return only the data that has changed for a particular record since the last time we received data from a PMS.

2. Currently, not via the API. We will be adding more features like this to the API in the coming weeks. For now, our customers seem to prefer the Diff Data webhook anyway.

3. We do cache the data. One of the hallmarks of PMS APIs is that they are unreliable. That being the case, all of the data served from our API is from our cache so we can pass along our uptime SLA benefits to our customers.

[rbaudibert]

Thank you for responding so promptly! That seems quite interesting :).

Diff data + new data definitely seem what 90% of your customers will need.

Another quick question: When you say "Job Success/Failure", what's a job?

_Full disclosure: I work at LeadSimple <https://www.leadsimple.com> and we integrate with most of these companies ourselves, and these questions were just me being interested in knowing how you solved (or intend to solve) some of the same problems we had to solve when integrating with them :)_

[kole78]

Of course, since we are not a pass-through API, our tech is set up as an async ETL. So a job represents a unit of work for Propify either fetching data from or pushing data to a PMS. You can track jobs to understand the lifecycle of your requests and overall status of your integrations.

[rbaudibert]

Oh, got it, because you'll save any POST/PATCH request and try updating it in the PMS in case they've been down. That's cool, thank you for clarifying that :)