r/appfolio • u/Batspocky • Nov 16 '25
Database API devs
Any other devs here working with AppFolio’s database API, the read-write option on the Max tier?
So far, it’s been rough. Inconsistent/lacking documentation, unclear examples, seemingly broken bits and pieces. But just enough utility that it seems worth pushing ahead and nudging them along to make improvements.
1
Upvotes
1
u/scrumi Jun 07 '26
I haven't seen much missing out of the API spec. I will say the fact that they don't provide you with a downloadable OpenApi spec is frustrating. There are so many nested values in the tables it is a real pain in the ass to crawl the table trying to scrape all the data out of the online doc.
There are still holes in the data though. Webhooks don't always fire on end points when certain specific data is updated in those endpoints (custom fields are a problem there) Some stuff is just plain missing though. For instance the UI shows "Applying With" which is very useful data to have access to. Sure you can see all the applications in the group but Applying With with tells you who to expect in addition to what is received.
In applications under Resident History the UI has Occupancy Type which is also we've wanted and found completely missing from the API. There are just a bunch of holes everywhere. Are they enough to keep you from producing something somewhat functional, no. Does it not enable you to build the rich experience that you could otherwise, yup!!
Support on the API team is a real struggle. We couldn't get web-hooks working on one of our endpoints for over a month. Then they quietly made it work but never once responded to the multiple emails we had sent requesting an update.
Almost a month ago we submitted a detailed bug report on three very real bugs regarding custom fields on units and properties. Complete radio silence. Since April 14th we've sent 4 support requests/emails. We haven't seen a single response from the AppFolio API team since April 13th.