I am looking for an API developer to integrate Campaign Monitor and Seat Advisor (
http://www.seatadvisor.com.au/index.asp). I have had a client request this and API Development is not my field.
When a ticket is bought in this system, emails are collected. My client wants these sent to their Campaign Monitor list.
Also when a person is unsubscribed in Campaign Monitor, there should be a flag raised in SABO that this person does not want emails sent to them.
Could any interested developers please email me on firstname.lastname@example.org for futher information as I need to obtain a quote for my client?
Hi Frederikke, thank you for posting this job here. I'll give this a shout out on Monday, Sydney time over Twitter - best of luck! :D
I had a look at the seat advisor website, and at this stage they don't have a public API, which will make integration difficult. But I was having a chat to a Seat Advisor rep this morning, and he assured me that they are in the process of having a full API developed at the moment.
My suggestion is that you or your client contact them directly so they understand that there is user demand for this sort of integration.
Thanks Ros and Phil!
I have some information from SABO in regards to their API. They have developed an API but it isn't public on their site. I have a document from them that I am happy to show any interested party.
Here's the first part of the document:
SeatAdvisor has developed a RESTful API to access and update patron information associated with organizations in the SABO system. This is the first of what we expect to be many objects accessible through the API, providing programmers and integrators great flexibility in leveraging the power of core SABO technology. This document provides a simple introduction to the mechanics of accessing the SABO REST API, techniques that should be applicable to further extensions of the interface.
Thanks, Frederikke - I think your best bet at this point is to ask Seat Advisor to recommend a developer who has worked previously with SABO. Given that there are not public API docs available, I suspect the concern for most developers will be how feasible it is to work with their API, not ours. Sorry for the trouble here, But I'm sure Seat Advisor will be happy to be of assistance.