• Facebook -> your website -> Facebook API -> your website -> Facebook
• They scan for “bad” stuff before displaying it.
• Good though because its all secure for you.

Setup

1. name your application (read the terms – good bathroom reading)
2. make note of your API key and secret (needed for all API calls)
3. setup a facebook URL (unique) and the callback URL (your server and should be directory only as they will append different files)
4. settings page to set sandbox, app type, sms integration and iphone

1st Roadblock

• validation is carried out on form fields that have specified names (pre cf9)
• fb_sig is in the wrong format and will never validate. set to another field and clear that field.

A Look at FBML

• tag system that handles output of data
• tags display data just as the website does
• tags are mostly used for UI/layout
• conditional logic tags do exist (if/else)

Digging into the API

• RESTful-ish API
• dot delimited methods
• methods are grouped in actions
• returns XML/JSON/PHP
• access to FQL (SQL-like)
• API Key, Call Id, MD5 Hash of secret and Version needed on EVERY request

CF is your glue

• Use API to get data
• parse and loop over data with CF
• output using FBML
• store data associated with uid w/ CF + SQL
• do not use cfLocation but rather fb:redirect and you can only redirect to FB

? Can you limit who can add your applciation by FB network?

After they allow it, you would have access to all that information. If they are not in the network that you wanted then you could just show a denied message or there may be API functionality to kick them oput of the application.

simonfree.com/presentations

twitter.com/simonfree