social-media-scraping-apis: a link list wearing a repository's clothes

What is actually in the repository

Four top-level entries tell the whole story: `README.md`, `FOLLOW_CREATOR.md`, a `settings/` directory, and `social-media-apis-3268/`.

There is no `package.json`, no `src/`, no test suite and no build script. The repository declares JavaScript as its primary language, which is consistent with a small amount of tooling that generates a directory rather than a library anyone imports.

The README's central claim is that this is the most comprehensive collection of social media scraping APIs on GitHub, with 3,268 ready-to-use APIs. The word that does the work in that sentence is not GitHub or comprehensive. It is ready-to-use, and the list makes it concrete: every entry is a hyperlink to a third-party listing rather than code you run. The first entries visible in the table are an Apify actor for LinkedIn search posts, an Apify actor for YouTube channel comments, and an Apify actor for Instagram video scraping, each rendered as a table row with a name and a description.

So the honest description of this project is a catalogue of hosted services, formatted as a table. Reading it is useful for one narrow purpose: discovering that a service exists for a platform you were about to build a scraper for. Nothing more.

The repository has no GitHub releases, which is consistent with there being no versioned artifact to release.

The statistics block contradicts the update badge

Two parts of the README make claims that cannot both be true, and the disagreement is the most informative thing in the file.

The collection statistics table states Total APIs 3,268, Category Social Media Scraping, and Last Updated 2025-12-09.

Above it, a set of badges states APIs 3,268, Category Social Media, Status Active, and Updated Daily.

A list that is genuinely updated daily and whose own table says it was last updated on 2025-12-09 is not telling you the same thing twice. One of the two is decorative. The dated value is the one that can be checked, so it is the one to believe, and it means the directory has not been refreshed in roughly ten months relative to the repository's last push on 2026-10-12.

That matters more than it would for a normal list, because the links are the product. Social scraping services are bought, resold and renamed constantly. A link that pointed at a working actor in December may now point at a different vendor, a dead page, or a listing with different pricing, and nothing in the README would tell you.

The repository's own presentation also crowds out its content. A large fraction of the README is a request to star the repository, followed by a promotional section for a paid Skool community with marketing copy about vibe coding and references to other tools by name. The homepage field points at that community rather than at any documentation. That is not disqualifying, but it tells you who the repository is aimed at and what it optimises for.

What the listed services describe, and what they do not

The category breakdown the README gives is worth reading as a description of what this kind of service market looks like, since the list is a cross-section of it.

The stated capabilities cover extracting posts, profiles, comments and engagement data from Instagram, Twitter/X, LinkedIn, TikTok, YouTube, Facebook, Pinterest, Reddit and Snapchat, gathering metrics and tracking competitor activity, downloading videos and images, extracting follower counts and bio information, collecting comments and likes, and automating collection workflows.

The phrasing of individual entries is where the ethics surface. The LinkedIn entry visible in the table sells itself on not using your own account and not using your cookies, which is a pitch built entirely around avoiding detection and account risk. That tells you what the buyer of such a service is optimising for, and it is not the platform's interests.

What none of the entries address, and what the repository does not address either, is the terms of service of the platforms involved. Scraping a platform's data usually runs into that platform's terms regardless of how the request is made, and a directory that aggregates 3,268 such services is not a neutral catalogue of compliance-neutral options. The README asserts that each API is production-ready, which is a statement about uptime expectations and not about authorisation.

There is also a category question worth naming: some services retrieve public pages, some act as a logged-in user, and some buy access to data that a platform has already licensed to a data provider. Those have materially different legal positions, and the table format collapses them into one column of descriptions.

This is not an attack tool and not credential theft, so it belongs in scope for a technical review. But anyone who takes a link from this list inherits that vendor's position, which is the risk to weigh.

What you should do instead, if you need the data

Since the repository offers no installable code, the practical alternative is to choose a source of data deliberately rather than by browsing a table.

For platforms with an official API, that is the API. When an official API is available, review its documented endpoints, authentication and rate limits. The trade-off is that you get the fields the API exposes and nothing else, which is usually the right trade for anything you intend to keep running.

For platforms where an official API is thin or absent, the honest options are a commercial data provider that has done the licensing work, or building and operating your own collector against content you are permitted to collect. The second is more work than a link suggests, and it inherits the same terms-of-service question with none of the vendor's accountability.

There is a third route for a specific and legitimate case: collecting your own data. If the account or pages are yours, you can still review the applicable terms, privacy rules and legal requirements before collecting the data.

What this repository is actually useful for is step one of that process: a platform checklist. The table tells you which platforms have a commercial service presence at all, which saves you the search. Once you have picked one, read that vendor's own documentation and pricing rather than trusting a one-line description in a markdown table that also claims to be updated daily and says it was not.

Maintenance state and the missing license

Two things to establish before you spend any time on this.

The first is maintenance. The repository is not archived and the last push was on 2026-10-12, so something changed. But the stated last update of the collection itself is 2025-12-09, and the layout contains nothing that would need maintaining except the generated directory. Treat the repository as an occasionally regenerated index rather than as a maintained project.

The second is licensing, and the absence is decisive. The repository records no license identifier at all. Without one, the default under copyright applies: no permission to copy, modify or redistribute is granted. For a list of links that is a narrow restriction in practice, although copying only factual data or bare URLs may raise different copyright questions from copying code. But if your use involves bulk copying the directory into your own project, there is no grant to rely on, and the repository ships no `LICENSE` file to tell you otherwise.

The `FOLLOW_CREATOR.md` file at the root and the `settings/` directory suggest the README is templated and generated. That is consistent with a directory rebuilt from a source list on a schedule. It also means individual entry descriptions come from a provider rather than from someone who used the service.

Editorial conclusion

Do not add this repository to a dependency list, because there is nothing to install: the root holds only `README.md`, `FOLLOW_CREATOR.md`, a `settings/` directory and the generated `social-media-apis-3268/` folder, and the repository declares no license. Use it, if at all, as a starting index and then verify each service on its own terms, since every entry is a link out to a third-party listing and the cost, reliability and legal position of each are properties of that service rather than of this list. Verify three things before you rely on it: whether the links still resolve and still point where the description implies, since the stated last update is 2025-12-09 while the badges claim daily updates; whether any platform's terms of service permit what the linked service does, which the list does not address; and who actually operates each service, because the list surfaces none of that. The last push was on 2026-10-12, so something in the repository changes, but the file layout suggests those changes are regeneration of the directory rather than maintenance of any code.

Frequently asked questions

Official sources

1. cporter202/social-media-scraping-apis on GitHub
2. Issues
3. Project website
4. README