I have an interesting issue you can help me with. I am using the Contacts API and calling it from a Javascript call using the WA API wrapper for jQuery. I got this code from the WA developer forum and loaded it into the files section to call locally from the WA install (rather than from the original location).

http://iarpreiki.org/resources/js/waPublicApi.js

I am using the API to create a URL that I will pass to an external SaaS system, so I need to collect various contact/membership field data.

The testing page is at

http://iarpreiki.org/Print-Your-Membership-Certificate -- the top HTML widget is where the HTML/JS code lives. It's quite short.

I am getting the contact JSON object properly returned and can populate the various fields that are coming back into my form, but none of the FieldValues array is coming back. I am expecting all the various extended field values like "Member since" and "Renewal due" as well as all the extra contacts and member fields that have been defined.

Here's the debugger output (link to picture) inspecting the object called "data" - The FieldValues object is totally missing.

https://dl.dropboxusercontent.com/u/55719247/debug%20values%20for%20contacts%20WA%20call.png

What am I doing wrong?

Hi,
we have a job that queries via the API searching with a filter on "Profile last updated". The query can return no results, it doesn't find any contacts changed since the last query run. However if we just iterate through the contacts and read the Profile last updated field it can be more recent shown in the API results than displayed in the WA web interface. It appears when reading via the API the "last login date" is used as the Profile last updated date if the last login is newer than the last profile update.

Summary:
Profile last updated date retrieved via API doesn't match the date shown in the web interface, it seems to match Last Login Date if that is more recent.

Search in the API seems to use the same date as Profile last updated as viewed from the web.

Any ideas?

Hi,

I have written JavaScript/HTML in a WildApricot site page to display events as a compact list in a table.

If I login to an administrator account it all works fine, if I login to a non administrator account I get error 403 returned from a get Events API call.....

"Failed to load resource: the server responded with a status of 403 (Current token does not provide access to scope 'events_view'.)"

Code snippet is:
<script>

generateTable();

function generateTable()
{
var EventsList = getDataFromApi("https://xxxxx.wildapricot.org/sys/api/v2/accounts/xxxxxx/Events?$sort=StartDate asc&$filter=Tags in [training,cruising,racing,racing_crew] AND StartDate ge 2017-01-01");

The API documentation here
https://help.wildapricot.com/display/DOC/Authenticating+API+access+from+a+Wild+Apricot+site+page
Says
"Access to Wild Apricot data will be limited by the access permissions of the currently authenticated user. Consequently, the API cannot be accessed within public pages that do not require user authentication."

The page in question is not a public page and the user is logged in (but not as an administrator), why are these API calls resulting in Error 403?

Thanks

Site Admin will grant access to a specific WA page for each Group Leader.
-- On this page will be a form Nicasio creates using WordPress and a
form plugin.
-- If more groups are added or changed, Nicasio would need to
add/update these forms for the Site Admin (or walk the Site Admin
through how to set these up).

The form will include the standard email fields (subject, and body, as
from and to fields will be auto-populated behind the scenes).
-- The from address will be set to the group leader's email within the
form's settings (a Site Admin or Nicasio would need to edit this if
changes are needed).
-- The to address(es) will be loaded via a custom WA API script
Nicasio creates that pulls all email addresses from members within the
specific group being sent to.

The WordPress site and form will need to be hosted where client chooses.
-- The forms will then be iframed/embedded into the group leader pages
mentioned above.

The WordPress site will not meant to be accessed directly and should
probably be blocked unless visiting from within the iframed page while
on one of the Wild Apricot group leader pages.
-- The WordPress site will be streamlined/stripped down to only show
the forms so any other content would be added to the Wild Apricot
pages.

To complete the items mentioned above we estimate this at roughly 25 hours of work.

1. I created a question (required to Members) "Are you using your albums to display your art?" Yes/No

2. The membership field was made public

3. I then created a saved search on the new membership field that allows me to pull out only members who have a "yes"

4. I created another Membership directory on a separate page. So I have 2 membership directories in use. One that displays all members and another that displays members who are using their photo albums.

5. I created a link on my home page directing the public to view the membership directory only for those who have art work to view.

For more details you can write to wal@woodlandsartleague.org