Hi - looking through recent posts in the forum regarding usage of the WA API V2 I get the impression that the API is basically unsupported by WA. e.g. two API issues I posted some days ago remain unanswered and a recent API V2 question from another user (GeePawHill) also remains without any replies.

So a basic question - do WA staff support the API through this forum? If not can anyone at WA advise what other avenues are available in order to get support for the API? e.g. should we be submitting API issues via the support channel? (email) Or some other forum?

I have two iOS clients projects currently underway but both are stalled waiting for API issue resolution.

Thanks

David

Hi - I've spent hours trying to figure why the POST below (in Swift) fails. Status code is HTTP 500 which according to the doc means "Wild Apricot's server has encountered an error and cannot fulfill the request." API Key and authentication are all good since GET requests to the same API work fine.

The event is very simple defined to have only fields first and last name and email. The event is public. I've triple checked all the Id's - event, contact, reg type id etc.

Any ideas much appreciated..

Thanks
David

Post URL is https://api.wildapricot.org/v2/accounts/{acctid}/EventRegistrations/

Post Body is - {"RegistrationTypeId":2394243,"Event":{"Id":1805601},"RegistrationFields":[{"Value":"John","FieldName":"First name"},{"Value":"Barrett","FieldName":"Last name"},{"Value":"fred@gmail.com","FieldName":"e-Mail"}],"Contact":{"Id":26450615}}

Response is -
Status 500
{"Message":"An internal error has occured. Please contact Wild Apricot support.\r\n Request ID:8bc7b4458b4c47b784f9c45dcf3f34ce."}

Swift Code
println("\nPOST Url ----------->(url!)\n")
let request = NSMutableURLRequest(URL: url!)
request.HTTPMethod = "POST"
let auth = NSString(format: "Bearer %@", accessToken)
request.setValue(auth, forHTTPHeaderField: "Authorization")
request.addValue("application/json", forHTTPHeaderField: "Accept")

let params /: [AnyObject]/ = [

"Event": ["Id": 1805601], //ev 4

"RegistrationTypeId": 2394243, // for ev 4

"Contact": ["Id": 26450615], //mem2

"RegistrationFields": [

["FieldName": "First name", "Value": "John"],

["FieldName": "Last name", "Value": "Barrett"],

["FieldName": "e-Mail", "Value": "fred@gmail.com"],

] /*,

"IscheckedIn": false,

"IsPaid": false,

"ShowToPublicIsPaid": true,

"Memo":"Important member",

"GuestRegistrationsSummary": ["NumberOfGuests": 1] */

] as Dictionary

var err: NSError?

var bodyData = NSJSONSerialization.dataWithJSONObject(params, options: nil, error: &err)

var bodyStr = NSString(data: bodyData!, encoding: NSUTF8StringEncoding)!

println("body ----------->(bodyStr)")

request.HTTPBody = NSJSONSerialization.dataWithJSONObject(params, options: nil, error: &err)

var response: NSURLResponse?

var error: NSErrorPointer = nil

var data = NSURLConnection.sendSynchronousRequest(request, returningResponse: &response, error: error)

var reply = NSString(data: data!, encoding: NSUTF8StringEncoding)

//println("\n\nerror ----------->(error)")

println("\nresponse ----------->(response!)")

println(reply!)

In Version 5.4, which was just released on June 15th, Wild Apricot has made changes to the authentication process https://help.wildapricot.com/display/DOC/API+V2+authentication for its API. We have moved from account-based authentication to the more secure application-based authorization. Instead of generating a single API key that provides complete access to your entire Wild Apricot account, you authorize individual applications, each of which are assigned separate credentials. If you've previously generated an API key for your account – prior to the 5.4 release – it will automatically be converted to an authorized application called Legacy API key.
If you are currently using an API key to authenticate your application, you can continue to do so, and no code changes are required.
If you are using Wild Apricot account credentials to authenticate your application, you must change the authorization header of your authentication token request. Specifically, you must, within the authorization header, set username to the client ID assigned to your application when you authorized it, and set password to the client secret assigned to your application. Currently, username is set to the application name and password is set to openwaapi_client (a constant). You will have until July 6, 2015 to make this change. On this date, the account-based authentication method will stop functioning.
As well, Wild Apricot has changed the possible scope https://help.wildapricot.com/display/DOC/API+V2+authentication#APIV2authentication-Supportedscopes values when restricting access using Wild Apricot's API. This is necessary to support the ability to restrict API key access to read-only functions. One of the new scopes – auto – will automatically detect the maximum allowed scope using the API key access level or the user's Wild Apricot account permissions, depending on which was used when requesting an authentication token. No code changes will be required because of this change as newly obsolete scopes will be automatically substituted by the corresponding new scope.