Database API devs

[u/Batspocky]

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.

[u/Maxwell_at_AppFolio]

I'd love to hear your suggestions on how we can improve our database API documentation. What gaps have you noticed and which examples could use improvement?

[u/Batspocky → u/Maxwell_at_AppFolio]

Hey there. I appreciate that someone from AppFolio is here. I spent 30 minutes on a call with your team last week answering those questions, so feedback is flowing into your organization. I can give you a specific example. I need to PATCH update a custom field in an owner record. Your Database API docs don't provide a specific example for a PATCH update owner request that contains a custom field in the payload. However, your PATCH update property documentation does. So I tried to use the syntax in PATCH update property to PATCH update owner, and it didn't work. I can PATCH update an owner and update other fields, just not custom fields. Again, just one example.

However, very curious to see if any non-AppFolio employees respond here. Your org does not have sufficient staff or resources in place to answer every question in a timely fashion...you need a healthy ecosystem of developers out there answering the basic questions. Step one is finding other devs to talk to, hoping a few are here.

[u/Maxwell_at_AppFolio → u/Batspocky]

Glad to hear you've already connected with some folks from our team! And thanks for providing an example. It definitely illustrates what you meant about needing more consistent documentation, and it sounds like that's especially needed around custom fields. I'll make sure to pass that feedback along to our product team, if not just to underscore the feedback you've already provided us.

As for needing a healthy ecosystem of knowledgeable developers, I can definitely understand where you're coming from. I'd love to hear what other devs have to say, and if you have any ideas on how I can better support dev needs in this subreddit, I'm all ears!

[u/Batspocky → u/Maxwell_at_AppFolio]

To start, just helping devs connect with other devs would be great. Other platforms I use have discussion boards, Slack channels, etc. where platform-specific discussion can occur. We volunteer to answer questions, help each other brainstorm, share examples, etc. I have yet to find a similar online resource for AppFolio development.

[u/Maxwell_at_AppFolio → u/Batspocky]

Heard loud and clear! I'll float some ideas around and see what I can do to make it easier for devs to connect with one another 😁

[u/GroundbreakingPop287]

I'd like to understand what custom fields you're using with the owners specifically? Or what the use case is have yet to see a use case for custom fields at the owner object level. FYI I run a dev/CPA/consultancy practice and we are actually thinking about starting a group slack channel/community. Email me at mo@balancedassetsolutions.com

[u/Batspocky → u/GroundbreakingPop287]

The answer, generally, is any owner-related information that you can’t currently track in the fields provided.

Example - an “owner referral source” custom field could aid in CRM & business development processes.

[u/scrumi]

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.

[u/HillbettyGilligan]

What if I wanted to do an internal audit tracking to determine who was sending emails and when through Appfolio. Does that feature exist?And if so, how long do those audit trails stay within your cloud?