Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Propify (YC W23) – Property Management System API Aggregator

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 58 posts

Re: Launch HN: Propify (YC W23) – Property Management System API Aggregator

#31

Post by Cshelton »

kole78 wrote: post #15
pplante wrote: post #14

I wish this was a thing back in 2012 when I was the technical co-founder of Rentlytics! We built our own integrations and it was terrible working with these systems. The docs were non existent and APIs limited in their capabilities to further vendor lock in. What systems do you support? I couldn't find a list anywhere.

Thanks for your feedback! Unfortunately your story is a common one - not much has changed with these APIs since 2012... or since 1999 for that matter. Our current integrations include Yardi, RealPage, Entrata, Propertyware, Buildium, Rent Manager and Rentvine. On the roadmap are Appfolio, MRI and ResMan. Necessary disclaimer: we only support integrations for customers who have officially sanctioned relationships with…

Ah, I went to your "How it Works".. didn't see Yardi, RealPage, or MRI and almost dismissed this product entirely!

Recommend updating that screenshot!

Now I'm interested.. will submit work email. I'm head of product at RealINSIGHT

Re: Launch HN: Propify (YC W23) – Property Management System API Aggregator

#32

Post by rbaudibert »

kole78 wrote: post #30
rbaudibert wrote: post #29

3 questions: 1. Where are the docs for Webhooks?´ 2. Is there any way to get only partial data, which was updated since the last time we hit your API? Is there a way to use a date-based cursor? 3. Is the data being saved (and duplicated) in your server, or are you simply parsing the request, converting to the PMS format, hitting their API, formatting the data, and sending it back, every time? edit: formatting

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.…

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 :)_

Re: Launch HN: Propify (YC W23) – Property Management System API Aggregator

#33

Post by kole78 »

rbaudibert wrote: post #32
kole78 wrote: post #30

Earlier quoted context omitted.

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.…

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…

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.

Re: Launch HN: Propify (YC W23) – Property Management System API Aggregator

#36

Post by rbaudibert »

kole78 wrote: post #33
rbaudibert wrote: post #32

Earlier quoted context omitted.

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…

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.

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 :)

Re: Launch HN: Propify (YC W23) – Property Management System API Aggregator

#39

Post by wasd »

zdms wrote: post #19

I work with multiple PMS platforms and centralizing even a simple unit price table is hellish given different PMS have different paradigms for concepts such as unit pricing. For example, Yardi (depending on the version of course) has 3 different tables for Market Price of a unit flying around in the backend, each with a slightly different definition. Another issue (for users not API creators) is the lack of universal…

zdms, where do you work? would love to connect & chat more. i'm facing this same problem. my email in profile.
Post reply on HN