Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The behavior you're seeing is correct.</p> <p>You're currently exchanging your code for a short-lived access token - which is required. Since Facebook removed the <code>offline_access</code> permission, the only way to get a longer lived access token is to exchange your short-lived access token for a long-lived access token. </p> <p>Please see the article on <a href="https://developers.facebook.com/roadmap/offline-access-removal/" rel="nofollow">removal of offline_access</a> specifically Scenario 4 which relates to OAuth. This is where they introduced the concept of long-lived access tokens and tell you how to get one. </p> <p>The short story to accomplish this is to take your short-lived access token - say AQADEADBEEF and GET this...</p> <pre><code>https://graph.facebook.com/oauth/access_token?grant_type=fb_exchange_token&amp;client_id={client_id}&amp;client_secret={client_secret}&amp;fb_exchange_token=AQADEADBEEF </code></pre> <p>Notice the 4 parameters grant_type, client_id, client_secret, and fb_exchange_token. The URL is the same as when you gained your original access token, but the parameters are a bit different. Insert your <code>client_id</code> and <code>client_secret</code> as appropriate</p> <p>You'll then get an access token with a much longer expiration time - 90 days I believe. Facebook is quite ambiguous about the length of any access token. You'll only know the expiration when you get it. The long-lived access token will still expire and Facebook currently offers NO way to renew it.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload