Posts tagged with facebook-graph-api

Using cURL, I am trying to get list of AdSets/Ad Campaigns that are having errors like "creative fatigue" with the help of Facebook Graph API.

I checked Graph API documentation, but couldn't find it. I also tried checking out API Explorer tool, but couldn't find a way to get this information.

Even ChatGPT and other AIs couldn't be of help as the references they give do not work now, current version is 20, but AIs give v13, v16 and so on.

Following are a couple of API endpoints from the many I have tried:

  1. https://graph.facebook.com/v12.0/<adset_id>?fields=id,name,creative{status}&access_token=<access_token>

  2. https://graph.facebook.com/v13.0/act_{ad_account_id}/adsets?fields=name,creative_status

I am expecting an endpoint that will help me fetch all the adsets or adcampaigns which are having the error of "creative fatigue" and other similar errors.

When I try to hit

https://graph.facebook.com/me?access_token={{token}} 

using the access token generated from flutter facebook auth on IOS it returns error

{     "error": {         "message": "Invalid OAuth access token - Cannot parse access token",         "type": "OAuthException",         "code": 190,         "fbtrace_id": "A7VLOSLTiXhbqehRbUpNz7z"     } } 

however when I try to generate token from android device and use it in the same endpoint it works fine.

I downgraded flutter facebook auth and same issue still occurs

I have been using ngrok for local testing for quite some time now with no problem at all. But recently, when I set my webhook in my app's callback url, it says:

The callback URL or verify token couldn't be validated. Please verify the provided information or try again later.

The url and token is correct, the endpoint does not get hit when I am doing it from Meta. When I use postman to make a GET request to that same url, I can see the request on ngrok terminal and the vscode terminal too. But not when I am verifying it on Meta. Is Meta now allowing requests to ngrok? What can I do to avoid this?

At midnight UTC on the 7th of June my facebook integration started returning:

((#100) This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature.

When getting information about a page.

I can't see anything on the changelogs about something on this date, but I had a notice of deprecation of v13 for the 28th of May and the switch to v14.

Maybe this change was rolled out over time and my account got the change on the 7th of June? I can't see anything relevant in the v14 changelog.

I am lost on what the issue is.

The Page token I am testing has 'pages_read_engagement' in its scope and my app also has 'Page Public Content Access'.

My own facebook page works though but users pages that appear to have the right permissions don't.