You can look into http://help.wildapricot.com/display/DOC/Contacts+API+call

Though you cannot directly use API calls - this not secure, API key cannot be used in publicly available Javascript code. So, you will have to have your own web server somewhere.

In this case we're speaking about the following setup:
* - your web server can accept calls with the parameter of Member ID or Names.
- the server runs server-side code to call Wild Apricot API with your own API key. The key is not available to anyone
- the call result will be what you need (member status)
* - on your regular WA website you place JS code, which collects the form data (member ID, etc.) and redirects them to your web server. The result of the requests you dislpay on the same page using JS code.
*

* This is complicated solution and expensive (requires your web server where you can run server-side code).
*

* Anything else will require from our team development of the special gadget to check member status.

Sorry, this is not as small as it might look like - to launch even the smallest API like this we need to think through and develop proper underlying infrastructure: access control, scalability etc. So it will have to wait until we are ready to move on API - which is quite high up on our priority list.

Yes, I understand it's "not on your roadmap" but my point is that it's a very quick fix/easy win situation that you could implement. Hell, use me as a beta tester if you like, I'm happy to plug in to a simple API that you guys could write very quickly. Just telling people "it's not in our plans at present" isn't really helping.

API is just not our current focus for now unfortunately.

I would like to have comments about API in it's own thread - http://forums.wildapricot.com/forums/308920-archive/suggestions/8831320-api-to-read-contact-member-records-2469 - otherwise we're going to loose them later when we're ready for API development..

I'd like to add that the lack of API is the biggest stumbling block in your entire system. I understand the security concerns and I understand that you are making other changes, but as a .net programmer myself I know how hugely simple it would be to simply expose a member record - or even PARTS of a member record - via a very simple API.

It only has to be read only, no writing required for 95% of people, I'm sure. Writing will be useful in future, but for now... All it needs is a simple api location, standard username/password interface and a couple of methods for retrieval - either directly via member ID of by first/last name or via email address.

Conservatively I could implement that in about 3 hours work with testing so I'm not entirely sure why you guys who are at least 10 times better than me cannot get this sorted. This would open your system up to so many more people and you'd get a huge user uptake on this feature alone. It's highly frustrating to see such a simple trick being missed for such a long time...

I think that the only way to make this is using WA own API - see http://forums.wildapricot.com/forums/308920-archive/suggestions/8831320-api-to-read-contact-member-records-2469

Using API one can create a page that does this thing. But still this is something we are not going to have soon.

Yes, we would find that VERY useful.

There is no such functionality now - but I can see how it can be useful. Let's see what other users say.