i am developping a mobile app which can use the facebook API to create and diffuse publicities. but i don't know which API to use. i saw somewhere th MARKETING API can be the one but i am not sure.
The markeying API is one choice. However, there also exists the Facebook Ads API. The only problem with this one is that you have to be approved and verified by Facebook to use it.
Related
I want to make a app for Non-Bussiness Instagram accounts.
My only problem is that when I access the old Instagram API (https://www.instagram.com/developer/) they tell me to use the new Graph API, but when I go to the Instagram Graph API reference, they says:
If you are building apps for Instagram Non-Business Accounts, please
use the Instagram Platform API instead.
(Note: The old Instagram API will be deprecated soon: https://developers.facebook.com/blog/post/2018/01/30/instagram-graph-api-updates/)
What can I do to resolve this little problem?
Instagram users can now set their accounts as 'creator accounts'. This allows the same capabilities via the Facebook Graph API as for business accounts, but without actually needing to be a business.
Details here: https://help.instagram.com/2358103564437429
Which API we can use for Facebook Ad creation programmatically in C#?Atlas API or ADs API. I have gone through both API documents and I find that both object names are different and Ads API is very similar to Facebook Ad fields. But I couldn't find any code samples for Ads API where as we have the code samples for Atlas API but object names are different compared to Facebook Ad. Please suggest me which API is better to use and what the process to access both Ads API.
To create ads on Facebook, you'll want to use the Facebook Ads API. This API is JSON based and pretty much any Graph API client library should be able to connect to it. One caveat is you'll need to request access to the Ads API, which might take a bit of time to get reviewed and enabled. The documentation for this API is here:
https://developers.facebook.com/docs/ads-api/
The Atlas API is primarily used to serve display ads and measure their performance. It doesn't sound like that's your primary use case here.
There are no C# Ads SDK that I am aware, but you can start with a C# Facebook SDK that will help you with lower level objects such as requests, accesstokens, batch requests etc.
http://facebooksdk.net/
And to build your Business Logic Layer, here is the spec:
https://developers.facebook.com/docs/ads-api/
Note: dont think it as repeat of any other similar questions.
We have options to display the 'Invite Friends' dialog using Legacy FBML and javascript (it also uses FBML) and they are working fine.
As facebook states that these FBML are going to be deprecated, is there any other better to way to Invite/ send requests to friends to join an application ..
I'm in the initial phase of my db app development and dont want to use the to be deprecated stuffs.. Is there any option using GRAPH Api?
Edit: I'm using PHP SDK for this app development and is there any function we could use from that?
The requests dialog is currently the only non-deprecated method of inviting your friends to a Facebook application. I doubt there will be a graph api method to create them as it would seem to be too easy to abuse, but getting, clearing and deleting them are available with the graph api.
I'm trying to access Facebook data using the Graph API from an external commercial application. I've created a login for my company and gather that I need to register a Facebook App in order to use the Graph API.
However, I am confused about the Facebook requirement to associate a Personal Profile (a real person) with the Facebook App. Why must a person become connected to my organization's application?
What if I leave the organization? Will the company I worked for need to pick another employee in order to access the Graph API?
Surely I am missing something.
Your question here seems to be about the Facebook API in general and registering an app for it, rather than the Graph API per se. The answer to the general question is that, as with the Twitter API and certain Google APIs, the personal account is used as part of the process of validating that the app is tied to a real person. Luckily, there's a good solution in place for handling when app developers no longer work for a company: another app developer can remove them from the app. You can list someone else on your team as a developer of the app and they will have the same rights to edit it as you do.
My google skills have failed.
My interest is how much user information I can access when having users connect to my website through. Comments, shared links, uploaded photos, data from other facebook applications used by the user?
Have a look at the Graph API ..or the old REST API for an idea of what you can access via Facebook APIs.
There's a good tutorial here: Facebook Connect Tutorial. I believe this article is using the REST API and the Javascript SDK for single sign on.