Defined API

Use this forum to suggest new features, language support, documentation, etc. for OpenEMM's roadmap

Moderator: moderator

Posts: 24
Joined: Tue Aug 22, 2006 6:50 pm
Location: Atlanta, Georgia U.S.A.

Defined API

Post by flyboy » Tue Aug 29, 2006 1:14 am

One thing that would be cool is for you to have a defined API to interface with EMM from other software.

Useful interactions:
- retrieve info on recipients
- update info on recipients
- insert new recipients

- generate new mailing from template and setting content items

I'm sure folks could come up with a lot more.
Fedora Core 5
OpenEMM 5.0.1
Java 1.5.0_08-b03
MySQL v5.0.22

Sam Eads
Sales & Investments
Crown Realty & Management

Site Admin
Posts: 2512
Joined: Thu Aug 03, 2006 10:20 am
Location: Munich, Germany

API for Plugins

Post by maschoff » Wed Nov 01, 2006 5:31 pm

Right now we are specifying an API for plugins. Any thoughts and suggestions are welcome!
OpenEMM Maintainer

Posts: 7
Joined: Tue Nov 14, 2006 1:18 am

Post by carcus88 » Wed Nov 15, 2006 5:01 pm

I am curious as to what sort of API is being defined. What sort of remote method call platform are you planning on using , XML-RPC, SOAP, REST?

I'm sure any of these standards would be ok but which one is going to be preferred by the devlopers and the community?

Here is a short list of things that I think should be API enabled

---- Recipients ---
Add Recipeient
Update Recipeient profile
Delete Recipeient
Bounce Recipeient
OptOut Recipeient
Search Recipients

--- Profile Fields ---
Add profile field
Update profile field
Delete profile field
List profile fields

-- Users --
Add user
Update user
Delete user
List users

-- Black List --
Add blacklist email
Delete blacklist email
Search blacklist emails

-- Mailing Lists --
Add mailing list
Delete mailing list
List mailing lists
Search mailing lists

I think these general things would API enable most of the functions that a third party program would need. The other functions of OpenEMM should be left to the web interface IMHO.

Posts: 8
Joined: Thu Aug 24, 2006 2:12 pm

Post by torcolato » Sun Jul 01, 2007 5:46 pm

I would prefer XML-RPC....
And IMHO there is one very needed task which is AddRecipients.

Everything else should be secondary.

This way we could connect other applications to use OpenEMM without human interaction, at least for what I guess is the most wanted feature.....

Posts: 2
Joined: Fri Nov 04, 2011 8:44 am

Re: Defined API

Post by rockyrock » Tue Nov 08, 2011 2:09 pm

It doesn't seem that PHP is short on XML-RPC solutions.
I would prefer to use the one that is actually a PHP extension since I am running Ubuntu 10.04 LTS, and I will have the library version matching my PHP without too much to worry about (as opposed to the PEAR one, which could possibly be updated beyond my current PHP version).
But there's a warning on all the PHP XML-RPC pages about it being experimental - yet, it's been around for years (implemented in PHP 4.1) and surely should be stable by now? Is this a case of rotten documentation, or should I really avoid this library?

Post Reply