Facebook Methods description: profile.setFBML

anna_150.jpg

Sets the FBML for a user’s profile, including the content for both the profile box and the profile actions. See the FBML documentation for a description of the markup and its role in various contexts.

Parameters

 

string api_key The application key associated with the calling application.
string session_key The session key of the logged in user.
float call_id The request’s sequence number. Each successive call for any session must use a sequence number greater than the last. We suggest using the current time in milliseconds, such as PHP’s microtime(true) function.
string sig An MD5 hash of the current request and your secret key, as described in the authentication guide.
string v This must be set to 1.0 to use this version of the API.
string format Optional - desired response format. Either “XML” (default) or “JSON”.
string callback Optional - wrap the response inside a function call. This is primarily to enable cross-domain javascript requests using the <script> tag, sometimes known as “JSONP“. This works with both XML and JSON.
string markup The FBML intended for the user’s profile
int uid Optional - The user whose profile is to be updated. Not allowed for desktop applications (since the application secret is essentially public).

Example Return XML

 

 

<?xml version="1.0" encoding="UTF-8"?>
<profile_setFBML_response xmlns="http://api.facebook.com/1.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://api.facebook.com/1.0/ http://api.facebook.com/1.0/facebook.xsd">1</profile_setFBML_response>

Error codes

1 An unknown error occurred. Please resubmit the request.
2 The service is not available at this time.
4 The application has reached the maximum number of requests allowed. More requests are allowed once the time window has completed.
5 The request came from a remote address not allowed by this application.
100 One of the parameters specified was missing or invalid.
101 The api key submitted is not associated with any known application.
102 The session key was improperly submitted or has reached its timeout. Direct the user to log in again to obtain another key.
103 The submitted call_id was not greater than the previous call_id for this session.
104 Incorrect signature.
240 The uid cannot be specified from a desktop application.
330 The markup was invalid.

Source page

Tags: , ,

Related Post

No Comments

No comments yet.

Comments RSS TrackBack Identifier URI

Leave a comment

SRTH SRTH