I'll be using BlackBerry Token For This Action.
What's The API code for following users is it /follow or /subscribers
And can anyone give its html codes.
Since Graph API v2.0, it's no longer possible to do this via the API.
See
https://developers.facebook.com/docs/apps/changelog#v2_0_graph_api
/me/subscribers and /me/subscribedto have been removed.
Related
My question is Laravel Socialite using for getting tokens only?
For example, I want make Facebook post thought API.
I cant find any methods in Socialite docs. Does it means, that Socialite using only for getting tokens?
As I see in https://socialiteproviders.com/, thats only auth additions.
As auth, it response basic user information, but if you need make full API list, you need find another solution.
I find solution, but I want explain my task:
I need use Instagram API through Facebook.
Facebook has PHP SDK for using Facebook API, with examples, which arent show any instagram cases with API using. I didnt manage Instagram API with Facebook SDK.
And I cant find any working solutions using Facebook SDK.
So, in my case, I am using Laravel Socialite for generate redirect URL and access token.
And then I am using manual HTTP client for Instagram API with token from Socialite.
I'm using WSO2's API Manager version 2.5.0 (https://github.com/wso2/product-apim/tree/v2.5.0).
Problem:
I create a REST API then create a SOAP API. When I edit the REST API looking at the first page (Design), it shows a SOAP endpoint instead of the REST endpoints. If I then create a websocket API and view the design page of the REST and SOAP APIs, the endpoints aren't shown indicating they are now websocket APIs. If I then create another REST API, viewing the design page of the other APIs shows they are now back to normal.
Question:
What is causing this to happen? Is there a fix for it? Does anyone have information about this? I've done extensive research looking through their docs, their github, stackoverflow, and google searches with no luck.
This is a known issue in 2.5.0 and fixed in 2.6.0.
Edit: My bad. It seems it's fixed after 2.6.0 release.
You can use the development branch[1].
[1] https://github.com/wso2/product-apim/tree/2.x
i facing an issue regarding the FaceBook Graph API.
actually a friend of me, have an FB App whitch can be used for the Graph API.
But in that case I activate a FB dev APP for myself, i'm not able to generate a valid security Token with the App-ID and App-Security.
At first the App is live and activated. For that I don't understand the error message at the end.
Second I don't want to have a User-Token with a validation for an hour.
These are the step's i following:
getting App Token
https://graph.facebook.com/oauth/access_token? client_id=20179479xxxxxx&client_secret=3048xxxxxxxxxxxxxxx&grant_type=client_credentials
The result i'm receving:
"access_token": "20179479xxxxxxx|Pqxxxxxxxxxxxxxxxxx",
Now if im trying to use the Graph API Explorer and trying these token as authentication, I'm facing an #200 OAuthexception
my request:
Get -> /v2.12/coca-cola
"(#200) Access to this data is temporarily disabled for non-active apps or apps that have not recently accessed this data due to changes we are making to the Facebook Platform. https://developers.facebook.com/status/issues/205942813488872/",
Have somebody any ideas how to solve or what i'm missing here?
With the Security Token from my friend he can use the example with coca-cola from the developer like in the documentation and example from FaceBook as well.
Thanks in advance
Facebook is changing the API due to a security issue. This means new apps have more restrictions and less access (for the minute) than apps that were already registered and using the API, probably why your friends key works. Seen as your app is either new or hasn't recently accessed the data you are requesting, you currently cannot fetch it.
Its not known what features will be removed from the API following this incident - as a result I wouldn't come to rely to heavily on any feature the API offers.
Im hearing that the ability to retrieve events could either be removed or the data you can access from an event is going to be severely limited, however thats not from any official facebook source. All apps will be subjected to a review according to this official facebook post, before they are granted access to the Events API, Groups API, and Pages API.
We are working on an idea of a FB app which let's us retrieve youtube watch histories of app users.
I know there's the possibility to retrieve watch histories through youtube's api, but in combination with a FB app I couldn't find examples.
Any input on this is much appreciated, thanks!
These two are orthogonal. Since you didn't specify a language, I'll assume you're using Python.
Write an FB app using Canvas to display output to users ... I assume you are using Canvas.
Use the YouTube API and Python client to make API calls. You'll need to use a database or some other storage engine to link a user's Facebook API auth token with their Google auth token. Both are using OAuth 2.0 (though they are different flavors), so once you learn one, the other should be easy.
Before I answer anymore questions, it's probably a good idea for you to work through the getting started guides for both Facebook's API and YouTube API first. After you have some understanding of both, pick a stack and you should more or less be ready to go.
The Graph API documentation says that the (invite only) message API endpoint is read-only.
The MyPad iPad app allows users to both read and compose messages.
Facebook has two APIs at present. The Graph API, which is what all developers should be using, and the REST API which they are in the process of depreciating. While they advise people to use the Graph API, it still lacks features found in the REST API. One of these would appear to be the ability to send messages. Details on the REST API can be found at their documentation page
Neither graph nor rest API can be used to send inbox messages to any user.
Mypad uses the other way around, which use m.facebook to compose and send(POST) messages directly.
of cos, it requires massive understanding of m. site of facebook. And problem is expected when facebook modify any structure on their m.site one day.