Limitations of MemberAPI?
Apologies for the long post, but we could really use some help here.
We are delving into our first Wild Apricot API project and we just wanted to confirm some things before we got too deep.
NOTE: We've asked support but they've told us they need to escalate the question and the last time they did that we had to wait 20+ days for a response. We’re hoping someone has some faster answers here.
We are writing a custom Members Portal - yes, we know about widgets and gadgets, but we want more granular control so the API seemed like the place to be.
We started building it out with the "Member API" (https://app.swaggerhub.com/apis-docs/WildApricot/wild-apricot_api_for_non_administrative_access/7.15.0) but immediately ran into some limitations… it doesn't appear that the user has the ability to edit their profile through that API…
So where we landed is authenticating the user through the Member API… using it to gather all the read-only data and then handing that off to the Admin API (https://app.swaggerhub.com/apis-docs/WildApricot/wild-apricot_public_api/7.24.0) to write. We also hit a 500 when hitting api.wildapricot.org/publicview/v1/accounts/{accountId}/payments so planning on grabbing that from the Admin API as well. (Didn't know if anyone had encountered that and maybe had a workaround.)
We wanted to confirm with someone the necessity of doing it this way because reading the Member API documentation it doesn't seem like it should be necessary but looking at the spec I see no way of actually updating data through the Member API. It also looks like things like /rpc/{accountId}/CalculateRenewalCosts and /rpc/{accountId}/ApplyForRenewal are missing from the Admin API. So we don't see a way around having to use them both and just wanted to make sure there weren’t any pitfalls to this approach we aren’t thinking about.
Would love to hear from someone with experience building something like this out to just confirm our suspicions.
Thank you in advance! Have a good day.
Team Umbrella
