The document outlines changes to the Facebook API between versions 1 and 2. Key changes include: - API versioning so calls must specify a version number - Permissions now require approval by default, with a test app for unapproved permissions - User IDs are now app-scoped temporary IDs instead of real Facebook IDs - Access to friend data is more limited, with new APIs for tagging and inviting friends - Permissions for photos, likes, and auto-posting now require approval instead of being automatic

1. FACEBOOK API PLATFORM CHANGE LOG
U 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

2. Agenda
1. API Change
2. Permissions
3. user basic profile
4. Email
5. User_friends
6. Tagging API
7. Invite friend
8. User_photos
9. User_likes
10. Auto post (publish_action)

3. 1. API CHANGE
1. V1.0
2. 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.0
2. 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

4. 2. Permissions
1. V1.0
2. All are approved for live
3. 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.0
2. 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

5. 2. Permissions
Extra permissions required at least 7 business days for
approval

6. 2. Permissions
Live App – Test App Login
• Live App for Vanish • Test App for for Vanish

7. 2. Permissions
Live App – Test App Login Permissions opt out
• No Out out • Test App for for Vanish

8. 2. Permissions
Live App – Test App Login Permissions out out
• No Out out • Live App for for Vanish
User can uncheck all extra permission

9. 2. Permissions
Live App – Test App Login Permissions out out
• No Out out • Test App for for Vanish

10. 3. user basic profile
1. V1.0
2. No approval required
3. Real FB ID
4. basic_info
5. All Friends id is available as
basic_info
6. Has to provide
1. V2.0
2. Default Approved
3. 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_profile
5. User_firends new permission has
been added
6. Required has to provide

11. 4. Email
1. V1.0
2. No approval required
3. Has to provide
1. V2.0
2. Default Approved
3. Has option to not give, can opt
out in permission dialog.

12. 4. User_friends
1. V1.0
2. No approval required
3. Has to provide
4. All Friends id is available as
basic_info
5. /me/friends returns all friends
1. V2.0
2. Default Approved
3. Has option to not give, can opt
out in permission dialog.
4. User_firends new permissions
has been added
5. /me/friends returns the user's
friends who are also using your
app

13. 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

14. 5. User_friends - Taggable Friends API
No friend
FB id is not
available to
store in DB

15. 6. User_friends - Invitable Friends API
Means no custom
invite

16. 7. user_photos
1. V1.0
2. No approval required
3. User Has to provide the
permission
1. V2.0
2. Approval required
3. User can opt out the permission

17. 9. user_likes
1. V1.0
2. No approval required
3. User Has to provide the
permission
4. Checked page like condition
via FQL and redirect to tab
page from app canvas
1. V2.0
2. Approval required
3. User can opt out the permission
4. 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.

18. 10. auto_post
1. V1.0
2. No approval required
3. User Has to provide the
permission
4. User delete the auto post
leads to blocking and
negative feedback
1. V2.0
2. Approval required
3. User can opt out the permission
4. For approval tell Facebook why
we need it and what we will do.