Elgg does not have a elaborate roles and permissions system built into core. Although in theory this could be built using a plugin, I think that computing the access control features you describe could be very time consuming and really slow down your site. I recommend sticking with the access features that Elgg provides.

Thanks for your response Kevin. 

So, basically, there is not an easy way to add another access option to the default elgg access features. But it makes sense to have some way to add additional read access options to profile metadata without forking core code. I do not know how to do it.

Thanks anyway. 

send_api_post_call() is more there for testing than anything else. If you have never done web services before I would:

• expose a single function as a web services method and get it working without any authentication from a web browser
• start calling the method from a client application on your computer (PHP cli, Python, Java, etc). You can take a look at the client libraries put together for Flickr or Twitter for an idea of how to build a simple client
• add authentication - first API and then user
• move to the iPhone
• build out your web services API and the client application

Hi Cash,

Thanks for your response.

Actually, I have been able to pull data from the elgg with the API authentication. I could successfully retrieve user profile pic to my iphone app using api authentication.

My problem now is how to use user authentication as well in order to retrieve data. I couldnt find any sample code for elgg so far which can show me a general view how to do it.

Cheers,

The API Admin plugin is in the 1.7 plugins repo at http://code.elgg.org/plugins/tags/1.7/apiadmin/

Thanks Brett for your answer because I sent my questions twice!