Hi Alex and Dan, I’m trying to void invoices in WA using the generic api call. I can fetch the invoice so I know I’ve got the connection and authentication right. I’ve attached a screenshot of the module.
I’ve just realised that my api key was set to read only. Now that I’ve changed it to full access the standard query string method works. Only wasted a day or so on banging my head against the wall!
Anyway best wishes, Andrew
You might be interested in a Postman collection of the WA Admin API v2 – this can help you understand much more clearly what WildApricot expects, especially when you end up having to make a Make API Call module configuration. Let me know and I can share it.
Yes, I have had good success with sending out reminders for previous orders from the WA store. This is for insurance purchased for a year. I couldn’t get the startdate and enddate to work in the api command despite lots of efforts, so I retrieve all orders and then filter between two dates in Make. Then send an Gmail reminder to the purchaser. Works fantastically!
Hi Alex, thanks for this. I’ve set up the WA api in Postman and authorised Postman in WA, obtaining a client ID and secret.
I’m struggling with authorisation and would be very grateful for some help. Sorry I’m a bit of a novice at all this.
If I use Type API I should be able just to use my API key??
If I use OAuth 2.0 it requires the Auth URL which is (replacing myorganisation.wildapricot.org with my own domain URL) https://myorganization.wildapricot.org/sys/login/OAuthLogin
Access Token URL ?is this the same as Auth URL?
Client ID and Secret which I have
Then I should be able to set the Variable /accounts/accountId and it should be good to go?
Thanks in advance, Andrew
PS I’ve been able to archive old WA contacts using a WA saved search in Make which is really neat.
Otherwise postman won’t get the token response after successful authentication.
Once you have these encoded the. Click get new token and you will see the oAuth login screen popup. Provide a valid wa username and password and you should get a token.
There are multiple authentication schemes but I like the scheme “Using an authorization code” one best since it doesn’t require you to encode a username and password into postman to authenticate. You can authenticate with any username and password and get an authorization token for subsequent requests.
Here is the full description of each wildapricot authentication scheme:
thanks Alex, really appreciate your help. I was pretty close as I had already set these parameters in the browser version of Postman. Anyway I have now tried the downloadable version with the different callback. Actually I think the 1st problem was that I hadn’t realised I needed to hit the “Get New Access Token” button. 2nd problem was that I hadn’t set the trusted redirect domain in Wild Apricot (its not very obvious!).
I’ve now got a token
Onwards and upwards…
You’ve gotten oAuth to work! Knowing how to authenticate in apis is half the battle usually. Getting comfortable with the configuration is a good skills because other apis have similar modes of authentication.
I can see why your recommended Postman - very helpful. I used it to have another go at the WA store/orders GET with a start and enddate (see previous post 6/13 on May3 - but still it returns all the orders. I suspect that there’s a bug in the api rather than a date formatting entry problem. Doesn’t matter as I have a workaround using filters in Make, but interesting to know if that is the problem.
The online orders used From and To as query params but I think you’re right. It’s not filtering the orders by date. I tried startdate and enddate too as parameters but those seem to be ignored too. Maybe open a ticket with their support team? I think there maybe something wrong there.