Location API obsolete in v3 API - use Address, Email, Phone and Website API

Hi all,

as announced earlier the Location API is no longer with us in the API v3 version. It was a beast of an API, too smart for its own good and certainly to smart for the API team!

So we created a bunch of new API's instead: Address, Email, Phone and Website. The Contact API will still get you the primary address, email and phone for a contact, and the first website. If you need more (like all the phone numbers for a contact) you can use one of the new API's. Each one has the following functions:

Date set for the next CiviCRM BeNeLux meetup: Friday 15 April 2011 in the afternoon

We have set a date for the next CiviCRM BeNeLux meetup: Friday 15 April 2011 in the afternoon. More details will follow, but we do expect a demo of the CiviCRM Mobile app (Android and iPhone) from qbSet. 


We will also present the new feature on the upcoming 3.4 and 4.0 versions. If there is enough interest, we will focus on the new API v3.


First user test data synchronization between CiviCRM and Oracle transaction system at De Goede Woning

For our project at De Goede Woning we have been developing a data synchronization process between CiviCRM and their main transaction system in Oracle (comparable with an ERP). Some data for a contact (first name, middle name, last name, gender and birth date), phones, emails and addresses will be common between the two, so a change, create or delete in CiviCRM will have to be synchronized with the main transaction system and vice versa.


Presenting.... the API team!

Today is the last day of the Bristol code sprint, which was a great experience! Lots done, climbed the Cheddar Gorge and tasted Kurundś famous lamb.... I will also always remember it for finding out I was part of the API team :-)

On a serious level, it is a good idea to have a team of people that take care of the API's. And taking care I think involves: