Is api.facebook.com here to stay or will it be deprecated along with Graph API v1.0? - facebook

I am working on a project that requires getting the number of Likes and Shares of various links.
This can be done either by calling api.facebook.com or Graph API v1.0 in the public with no app and token required at all.
http://api.facebook.com/restserver.php?method=links.getStats&urls=http://www.example.com/
http://graph.facebook.com/http://www.example.com/
However, Facebook has started deprecating apps using Graph API v1.0, and their Platform Upgrade Guide makes no mention of api.facebook.com which predates Graph API v1.0.
Developers should expect apps calling API v1.0 to be migrated at any time after April 30th, 2015. The migration will roll out to all apps over the course of a few weeks.
Should I expect api.facebook.com to be deprecated along with Graph API v1.0, or will it be another sharer.php and be kept indefinitely?

It's announced as deprecated since a long time ago. Probably nobody will be able to tell you WHEN or IF Facebook will shut it down. But assume that this can happen anytime.
So, if you don't want to have your app suddenly break, then you should migrate to Graph API v2.3.
Have a look at
Migrating Facebook API for URL share count from v1.0 to v2.0+

So, apparantly the api.facebook.com server is regarded as v2.0, which is no longer available as of August 7th, 2016. All methods on api.facebook.com now return the REST API is deprecated for versions v2.1 and higher (12) error message.

Related

Instagram API deprecation 2020

I'm building an app that has the user log in through instagram, it then reads their feed and uses that information for the app. Instagram has a page that says their API's will be deprecated in 2020 but some things will still work. It's not straightforward as to what is being deprecated and what isn't, and I have not found any way to contact them directly. Does anyone know if the following URL will continue working, and if not if this type of app will even be viable in the future? Why is IG and Facebook becoming much more closed platforms to 3rd party integrations?
https://api.instagram.com/v1/users/self/media/recent/
Deprecation notice:
https://www.instagram.com/developer/
The legacy Instagram API - https://www.instagram.com/developer/ will be deprecated in favor of Instagram Graph API provided by Facebook - https://developers.facebook.com/docs/instagram-api
In order to use https://api.instagram.com/v1/users/self/media/recent/ this endpoint you need Basic permission. As documentation says, it will be deprecated in early 2020, which means that the legacy API will be most probably shut down, since there will be no more capabilities to request for.
You should most definitely start building your app with Graph API. Please keep in mind that it takes some time before you can go live with your app. It requires couple of things like Business Verification, review of requested permissions in App review and it can take some time to be able to go live.
Please keep in mind that the Graph API works only for Instagram Business type of accounts. You can't use it for regular accounts at the moment. It is not clear yet if it will be available for all accounts, but most probably it will be in the future. It was the same as with deprecating Public Content permission on Instagram legacy API. They added similar functionality in Graph API.
If you plan to support all users, you will also have to apply for Basic capability in legacy API. In other words, you need to support both Instagram API and Instagram Graph API if you plan to target all Instagram users, both regulars and Business profiles.
Another thing to keep in mind is that you can't really report bugs or get any help from legacy Instagram API. If you will find the bug you can't report it as they do not accept it due to deprecation.
So start building with Instagram Graph API, once you will be good to go, try to add Instagram legacy API support. If everything will be fine and Facebook will add support for legacy accounts, your Graph API should easily take over Instagram legacy API functionality.
Most probably the reason why they are tightening the integrations and makes it harder for the developers is user privacy. They do not want to have yet another incident like Cambridge Analytica for instance.
It does not make sense to build something with the old API, that old API URL will definitely stop working (with all the old api.instagram.com endpoints). There is a new API though: https://developers.facebook.com/products/instagram/

Will api.facebook.com end point be going away when 2.0 facebook api rolls out

Ok so, Some confusion here, and perhaps I am just stupid.. perhaps somebody who works for Facebook even can answer I don't know...
It says FQL is going away when they phase version 1.0 out, ok fine and well.
Does that include only the graph.facebook end point?
What about api.Facebook end points, i see no mention of that there.... stuff that previously did not require a access token...
Really the simple question is: https://api.facebook.com/method/fql.query?query=select%20%20like_count,share_count,commentsbox_count,click_count%20from%20link_stat%20where%20url=%22http://www.microsoft.com%22
Would that still work in v2.0 or v2.1 seperately?
Thanks.
Graph API v2.0 was rolled out on April 30th 2014 already. The endpoint api.facebook.com is even older than Graph API v1.0, but apparently still supported, even with the Graph API v2.1. FQL itself will be available until August 6th 2016 with Graph API v2.0.
I just wouldn't rely on that, because it is long known that this endpoint is deprecated.
With Graph API v2.1, there's the new endpoint
/?id={url}
See https://developers.facebook.com/docs/graph-api/reference/v2.1/url/ Unfortunately, it has less details concerning the sharing information.

creating event via facebook graph api

Is there any way to create facebook event via code (as of today), referred to the documentation :
for v2.0
for v1.0
Publishing was possible in v1.0 but not in v2.0. Is there legacy API support which I can use to create facebook events ?
Any help appreciated.
If your app is a Graph API v2.0 app (created after April 30th 2014), you don't have the possibility to create events anymore via the Graph API.
If your app is v1.0, the possbility to create events will vanish on May 1st 2015.

Using FB API V1 with new Apps

i need to search in public Facebook Posts.
So, i check my querys using the Graph-Explore-Tool to see whats happen.
search?q=%23wm2014
Switching the Version to 1.0 in top of the Page returns some postings.
So, i created a new FB App, and send my request (via post) to the server.
I always get:
{
"error": {
"message": "(#11) Post search has been deprecated",
"type": "OAuthException",
"code": 11
}
}
So, i used the Endpoint: https://graph.facebook.com/v1.0/
but i recived still the same error.
Finaly i used an old FB App i created (october 2013) and used this App-ID and App-Secret vor the access_token-Parameter and: suprise suprise! it works.
Are there hidden settings in the FB App Settings, to define, witch API should be used?
Thanks for your help.
S.
Apps created after April 2014 will only be able to use v2.0
So if you need to use v1.0 (which will only be possible until April 2015), you have to use an old App.
Using the v1.0 endpoint does not really make sense, but the v2.0 endpoint is there to force older Apps to use the new version already.
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.
Source: https://developers.facebook.com/docs/apps/upgrading

Replacement for deprecated event handling in Graph API

I have a hyper-critical Facebook app (for our organization) that used Graph API v1.0 to read and post events for our [closed] Facebook group. Now that Graph v1.0 is deprecated and event support is "no longer supported" for Graph v2.0 it has literally killed our ability to use this app - or Facebook itself for our social media needs.
Are there any other or "replacement" APIs that would allow my app to post events - even if it is just into one, single, controlled group?
This isn't a great solution, but the 1.0 API will be available through April 2015. You could downgrade to the old API until then - certainly not a good long term plan, but it could give you time to find another option