Why do you plan to remove Facebook API support?

  • Resolved HerveRenault

    (@herverenault)


    6 years, 1 month ago

    Hi,

    thanks for making this great plugin.

    In latest version, you write:

    Support for Facebook API will be removed in the future. Facebook significantly
    reduced access to their APIs across all apps on Apr, 2018. Now it takes longer and is more difficult to configure Facebook Apps that can post content to pages or groups. As a result, it is unlikely that this integration is going to work for new users. We introduced support for Zapier/IFTTT Webhooks as an alternative and expect customers to migrate to that integration method.

    You can read more about Facebook changes here: https://developers.facebook.com/blog/post/2018/04/04/facebook-api-platform-product-changes/

    If you are currently using the Facebook API integration method and not having any issues, you don’t have to do anything right now.

    But I can’t see no sign that the /page-id/feed API will be removed by Facebook:
    https://developers.facebook.com/docs/graph-api/reference/v3.1/page/feed#publish

    And how long will you keep the Facebook integration code in the plugin?

    Best regards

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi @herverenault,

    Thanks for contacting me here.

    I’d like to clear up any confusion about this, because it is definitely confusing (to us and to everyone).

    Facebook has indeed made MAJOR changes to their API since April 2018, when the Cambridge Analytica scandal came to light. They’ve made enough changes that require you to publish a FULL FB application to make the integration work. That’s a lot of work (believe me, we’ve tested it…it takes a LONG time and if you miss something, well, they kick you back to the start and you have to do it all over again, no jumping to the front of the line).

    As for the page-id/feed API, my developer did find a direct FB source that quoted that. I’m not sure where it is but I’ll look and see if I can find it.

    BUT–that doesn’t mean you can’t use AWPCP and Facebook to publish ads! That’s the confusing part.

    We don’t plan to discontinue the use of the FB API right now, but I can’t guarantee that FB won’t cut it off somehow in light of privacy scandals or other internal factors. That’s why we added 2 additional, much easier to use, integrations.

    Their API is only one of 3 ways to do it. We have two others that seem to work well, but they require additional integrations to make it happen.

    We have ALL three methods documented here:
    https://awpcp.com/documentation/#settings-facebook (the API)
    https://awpcp.com/documentation/#settings-facebook-zapier (using Zapier)
    https://awpcp.com/documentation/#settings-facebook-ifttt (using IFTTT)

    We will continue to keep it as is for now. Of the three, the API is now the hardest way to do it, unfortunately.

    Thread Starter HerveRenault

    (@herverenault)

    OK, so we can keep on using the FB API integration that works for us currently?

    You can use the “new” version documented above (with the FB app). That will work for the moment. At some point, it may not and again, that’s outside of our control.

    We’ll do what we can to keep it going but FB is hell bent on changing things so I can’t make any “forever” promises here.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Why do you plan to remove Facebook API support?’ is closed to new replies.