facebook permissions
DESCRIPTION
A comparison of Facebook API v1 to v2.TRANSCRIPT
FACEBOOK API PLATFORM CHANGE LOGU N V E R S I O N E D , V E R S I O N 1 I S N O W V E R S I O N 2
Agenda1. API Change2. Permissions3. user basic profile4. Email5. User_friends6. Tagging API7. Invite friend8. User_photos9. User_likes10. Auto post (publish_action)
1. API CHANGE
1. V1.02. v1.0 for one year and it
will expire on April 30th, 2015.
3. For apps created before April 30th 2014, making API calls without specifying a version number is equivalent to calling v1.0 of the API.
1. V2.02. It will expire on April 30th,
2016.3. For apps created on or
after April 30th 2014, making API calls without specifying a version number is equivalent to calling v2.0 of the API. These apps won't be able to call v1.0 of the API.
The largest change is the introduction of API versioning. Many services that Facebook offer are now versioned
2. Permissions1. V1.02. All are approved for live3. Extra permissions were
approved after sandbox goes to live
4. No Test App either sand box or live
5. User has no option to opt out extra permissions
1. V2.02. Only public_profile, email,
user_friends (a new permission is added) are approved by default.
3. Only extra approved permissions will be available to live fb app,
4. A new concept test app, only developer under development can still use extra permissions
5. User can opt out all extra permissions and other then public_profile
2. PermissionsExtra permissions required at least 7 business days
for approval
2. PermissionsLive App – Test App Login
• Live App for Vanish • Test App for for Vanish
2. PermissionsLive App – Test App Login Permissions opt out
• No Out out • Test App for for Vanish
2. PermissionsLive App – Test App Login Permissions out out
• No Out out • Live App for for Vanish
User can uncheck all extra permission
2. PermissionsLive App – Test App Login Permissions out out
• No Out out • Test App for for Vanish
3. user basic profile
1. V1.02. No approval required3. Real FB ID4. basic_info5. All Friends id is available
as basic_info6. Has to provide
1. V2.02. Default Approved3. app-scoped user IDs (temp id
for this app will be same for this app all time) , the ID for the same user will be different between apps.
4. public_profile5. User_firends new permission
has been added6. Required has to provide
4. Email
1. V1.02. No approval required3. Has to provide
1. V2.02. Default Approved 3. Has option to not give, can
opt out in permission dialog.
4. User_friends
1. V1.02. No approval required3. Has to provide4. All Friends id is available
as basic_info5. /me/friends returns all
friends
1. V2.02. Default Approved 3. Has option to not give, can
opt out in permission dialog.4. User_firends new permissions
has been added5. /me/friends returns the
user's friends who are also using your app
4. User_friends
6. We can access friends data friends_* permissions
6. All friends_* has been removed, not able to access any friend data
7. There are two key use cases where apps need access to non-app friends: tagging and inviting. In v2.0, we've added the Taggable Friends API and the Invitable Friends API to support these flows.
8. Tag and invite
5. User_friends - Taggable Friends API
No friend FB id is not available to store in DB
6. User_friends - Invitable Friends API
Means no custom invite
7. user_photos
1. V1.02. No approval required3. User Has to provide the
permission
1. V2.02. Approval required3. User can opt out the
permission
9. user_likes
1. V1.02. No approval required3. User Has to provide the
permission4. Checked page like
condition via FQL and redirect to tab page from app canvas
1. V2.02. Approval required3. User can opt out the
permission4. Redirecting in between app
page and app canvas is not as per guideline and this requirement will always disapproved. User likes is use case where user interest analysis is required like Axis bank youth card app.
10. auto_post
1. V1.02. No approval required3. User Has to provide the
permission4. User delete the auto
post leads to blocking and negative feedback
1. V2.02. Approval required3. User can opt out the
permission4. For approval tell Facebook
why we need it and what we will do.