This is a placeholder right now. I'm not sure if we will need it yet.
The client needs to make a graph call to create applinks for Facebook invites. The call requires an app access token which lets us make the call as the app instead of as a user. Getting an app access token requires use of our facebook secret and that should stay protected by the service.
GET /oauth/access_token?
client_id={app-id}
&client_secret={app-secret}
&grant_type=client_credentials
The call returns an app access token which should be returned to caller. The access token is basically a combination of app_id and app_secret. If we persist the app access token on the client, it will be in an encrypted form (think keychain, etc.).
This is a placeholder right now. I'm not sure if we will need it yet.
The client needs to make a graph call to create applinks for Facebook invites. The call requires an app access token which lets us make the call as the app instead of as a user. Getting an app access token requires use of our facebook secret and that should stay protected by the service.
GET /oauth/access_token? client_id={app-id} &client_secret={app-secret} &grant_type=client_credentials
The call returns an app access token which should be returned to caller. The access token is basically a combination of app_id and app_secret. If we persist the app access token on the client, it will be in an encrypted form (think keychain, etc.).