Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizDigital Marketing Facebook Marketing API 2 years ago
Posted on 16 Aug 2022, this text provides information on Facebook Marketing API related to Digital Marketing. Please note that while accuracy is prioritized, the data presented might not be entirely correct or up-to-date. This information is offered for general knowledge and informational purposes only, and should not be considered as a substitute for professional advice.
No matter what stage you're at in your education or career, TuteeHub will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Digital Marketing 0 Answers
Digital Marketing 0 Answers
Digital Marketing 1 Answers
Digital Marketing 0 Answers
Digital Marketing 1 Answers
Ready to take your education and career to the next level? Register today and join our growing community of learners and professionals.
manpreet
Best Answer
2 years ago
_x000D_ UPDATE: see below I've been thinking hard about this question too. It's not entirely clear to me yet but here's the route I am thinking of going. I am creating a REST API an my users only auth with Facebook connect. On the CLIENT: Use the Facebook API to login and get an OAUTH2 code. Exchange this code for an access token. In every call to my custom API I'll include the Facebook user id and the access token. On the API (for every method that requires user authentication): Make a request to the /me Facebook graph using the access token from above. Verify that the Facebook user id returned matches the user id passed to my API from above. If the access token has expired additional communication is required. I have yet to test this. How does it sound? --- Update: July 27th, 2014 to answer question --- I only use the above exchange once upon login. Once I determine which user is logging in, I create my own access token, and that token is used from that point going forward. So the new flow looks like this... On the CLIENT: Use the Facebook API to login and get an OAUTH2 code. Exchange this code for an access token. Request an access token from my API, including the Facebook token as a parameter On the API Receive access token request. Make a request to the /me Facebook graph using the facebook access token Verify that the Facebook user exists and match to a user in my database Create my own access token, save it and return it to the client to be used from this point forward