Boost Facebook Comments via API

Greetings, dear audience! Yellow is in touch, and today we will deal with adding such an important thing to our advertising posts as comments.

It’s a little surprising to me that in the arbitration community, which is actively interested in the capabilities of the Facebook API, there is still no suitable software for cheating, although it would seem that the idea is on the surface. I hope that after the publication of this article, these tools will appear on the market.

So, I responsibly declare that by the end of reading you will have a cheating method in your hands, with the help of which you can immediately get down to business!

What we need:

1. Several autoregs, with a loaded avatar and a name for the desired GEO (in the CIS — with Russians, in Burzh with names in Latin);
2. Access Tokens from each of these autoregisters;
3. COOKIES of each author in CURL format;
4. Post ID of your ad;
5. ID of the fp on which the post is posted;
6. The CURL program, with which we will send requests;
7. Texts comments.

If everything is clear with the first two points, then let’s look at the rest in more detail.

We receive cookies in the required format

Let’s launchanti-detect, open our autoreg, on behalf of which we will publish the comment, go to Ads Manager and open Developer Tools (F12). There we go to the Network tab, switch the request type switch to Doc and refresh the page (F5). We see the request, click on it and in the Request Headers section we see cookies in the format we need. Let’s copy them for ourselves.

We get the id of the announcement post and FP

Inside Facebook, each ad “belongs” to the FP with which you are running it. That is, in essence, this is a post on FP. To get the post ID, go from Ads Manager from editing the ad to viewing the post with comments, then in the menu (three dots on the right) for the post, select Embed post, hover over the date and see below:

storyfb_id is the id of the post, and simply id is the id of the fp

Posting a comment using CURL

We are almost ready to publish our first comment. To send requests to the API, we will use the CURL console program. On Macs it is built in by default, so we just launch the Terminal. And for Windowsdownload CURL from hereand unpack the archive to any folder, then launch the console (Start-Run-cmd-Enter) and go to this folder (cd Full_Path_To_Folder).

Let’s go! Copy the request below somewhere in your notepad and fill it with all the necessary data: fp id, post id, token, comment, cookies. Yes, comment textbe sure to run it through firstUrlEncoder! Otherwise you will get an errorMalformed input.

Then copy the completed template into the console and press Enter.

curl "https://graph.facebook.com/v19.0/fpId_postId/comments?access_token=token&method=post&message=Thanks!" --cookie "c_user=10003943638656; cppo=1; wd=1280x610; usida=eyJ2ZXIiOjEsImlkIjoiQXchF_7bCC"

If you inserted something incorrectly, curl or febe will write you an error. For example, if cookies are inserted incorrectly there will be an Invalid Request:

If successful, you will see a response from Facebook in the console, in whichthe id of your new published comment will be written:

You will also see this comment right below your post:

All that’s left for you to do is fill in one by one and enter the command into the console for each of your autoregs and get the number of comments you need. If you want to useproxytogether with CURL — read the help, the software supports them.

Additional chips

Comment on comment (branch comments)

If you want to leave a comment on another comment, then simply use the id value of the comment you need previously received in the console instead of the fpId_postId part of our request.

Comment on behalf of FP

If you want to leave a comment not on behalf of the social network, but on behalf of the FP who hangs on the social network (this is very good. convenient: just collect a pool of FPS with the necessary names and photos of generated people), then just change the token from Ads Manager in the request to a token from the desired FPS.

Here’s the request:
https://graph.facebook.com/v19.0/me/accounts?fields=id,name,access_token&access_token=TOKEN

Change the word TOKEN in it to the usual one from Ads Manager and run this request directly in the browser in a new tab, for example. He will show you all the FPs and their tokens.

But keep in mind that Facebook has a limit on the number of comments left from one social network (approximately 7-8 comments) If you have a bunch of fepe hanging on one social network, then after hitting this limit, you will be able to publish comments only after 24 hours! To bypass the limit, hang your FP on 3-4 accounts at once.

Developer Token

If you often use certain accounts for commenting, then I recommend taking a token from the developer account instead of a token from Ads Manager —I wrote about it in detail here. It lives better and does not tend to change suddenly, moreover, when using it, cookies are not needed.

Conclusion

I hope this was helpful! If you liked the article, don’t forget to write a comment andsubscribe to my tg channel. And, of course, give your Masha a plus!