npm scraper API
The InsightSocial npm API has 18 endpoints, from 20 credits a call. A package call costs 20 credits, about $0.02 on Pro, and your first 10 calls up to 100 credits each are free.
The npm API for packages, versions, downloads, dependents, security advisories and provenance, plus users, orgs and registry changes, in the same envelope as every other platform on your key.
18 endpoints · from 20 credits a call · 10 free calls up to 100 credits each · no credit card
curl "https://api.insightsocial.app/v1/npm/package?name=express" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
What npm data can you get?
Public npm data only, in the same JSON envelope as every other platform. Every npm endpoint is beta: inside data it returns npm's own structure under our naming rules (snake_case keys, string ids, ISO times where npm gives a timestamp), not the shared profile and post schema, and fields may change.
Packages and versions
A package's latest version, dist-tags, publisher and dependencies, its full registry document, every version with publish time and sizes, and one version in full.
Downloads
Downloads for one package over a period or a day range, daily if you want, per version for last week, or for up to 128 packages in one call.
Dependents, advisories and provenance
The packages that depend on one, the security advisories that affect a version, and its decoded publish and SLSA provenance attestations.
Search, users, orgs and the registry
Registry search, a user's or org's profile and packages, recent updates and the registry change feed.
What people build with the npm API
Dependency and security reviews
Check a package's advisories, provenance, maintainers and deprecation before you add it, in a CI job or an AI agent.
Adoption tracking
Compare downloads for a set of packages over time, daily or by version, to see which libraries are growing.
Ecosystem research
List a package's dependents and an org's packages, then follow the registry change feed for new releases.
npm API endpoints
All 18 npm endpoints and their price in credits. 1 are metered: they show a range and charge what the call actually read.
| Endpoint | Credits | What it returns |
|---|---|---|
| /org | 20 | Get an npm org or scope profile, including the type npm actually stores. |
| /org/packages | 20 | List the packages an npm org or scope can publish, 25 per page. |
| /package | 20 | Get an npm package's latest version, every dist-tag, publisher, dependencies and last week's downloads. |
| /package/advisories | 20 | List the security advisories affecting an npm package version, or every version. |
| /package/dependents | 20 | List packages that depend on an npm package, 36 per page; a page past the served list is empty. |
| /package/details | 20 | Get npm package registry document with every version, README, stars and timestamps. |
| /package/downloads | 20 | Get npm downloads for a package over a period or a day range, or the whole registry's total. |
| /package/downloads/versions | 20 | Get last week's npm downloads for every version of a package. |
| /package/provenance | 20 | Get the publish and SLSA provenance attestations attached to an npm version, decoded from their sigstore bundles. |
| /package/version | 20 | Get one npm version document, by exact version or dist-tag, with its files, dependencies, scripts and registry metadata. |
| /package/versions | 20 | List an npm package's versions newest first, with publication time, deprecation, provenance, integrity and sizes. |
| /packages/downloads | 20–1,600 | Get npm downloads for up to 128 package names in one call, one result per requested name. |
| /packages/search | 20 | Search the npm registry by words and qualifiers, ranked by npm's search score; a page past the results is empty. |
| /registry/changes | 20 | List npm registry changes from a sequence cursor, with deleted-document markers. |
| /registry/packages | 20 | List npm package names in registry key order, with an opaque cursor. |
| /registry/recent | 20 | List recent npm package updates, newest first, at most 50 items. |
| /user | 20 | Get an npm user's profile: display name, GitHub handle, dates and package count. |
| /user/packages | 20 | List the packages an npm user can publish, 25 per page. |
Parameters, response fields and examples for each endpoint are in the npm API reference.
InsightSocial vs the official npm API
The npm registry and its downloads API are public and free to read without a key.
| InsightSocial API | Official npm API | |
|---|---|---|
| Access | One API key | Open; no key needed to read |
| Shape | One envelope, cursor paging and errors shared with every platform | The registry's own documents |
| Other platforms | The same key covers GitHub and the other platforms too | npm only |
| Cost per call | 20 credits | Free to read |
The official API is the right tool for posting, messaging or managing accounts you own. This one is read-only public data.
How much does the npm API cost?
npm calls start at 20 credits. Every endpoint's price is in the table above and in the free GET /v1/endpoints catalogue, so you know the cost before you call. Pro's 10,000 monthly credits cover about 500 package lookups at 20 credits each.
Failed calls are free
A call that errors or finds nothing costs 0 credits.
Repeats and retries
A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
One balance
API calls and Chrome extension exports share the same credits. The free plan includes 500 a month.
Not writing code?
Connect InsightSocial to Claude or ChatGPT and ask for npm data in plain English. Same account, same credits.
npm API: frequently asked questions
If you only need npm, the registry and its downloads API are free and need no key, and they are a fine choice. This one is for when npm is one of several sources: one key, one response envelope, one credit balance and the same paging and errors as GitHub, Hugging Face and the rest.
Yes. /v1/npm/packages/downloads takes up to 128 names, at most 20 of them scoped, and returns one result per name for a period or a day range. It is metered from 20 to 1,600 credits by how many names it reads. /v1/npm/package/downloads covers one package, daily if you ask.
/v1/npm/package/dependents lists them, 36 a page.
They return the registry's own record shapes under our naming rules (snake_case keys, string ids and ISO times) rather than the shared profile and post entities, so fields may change. Every npm endpoint is 20 credits a call except bulk downloads, which is metered. Calls that fail or find nothing are free.
No. There is no npm app, OAuth flow or review. One API key in the x-api-key header works for npm and the other 60 platforms.
Yes. Your first 10 calls priced at 100 credits or less are free, and the free plan includes 500 credits every month. No credit card is needed to get a key.
60 requests a minute and 10 requests in flight at once, per API key. Going over either returns a 429 with a Retry-After header, and a rejected request costs nothing. There is no daily quota: past those two limits, your credit balance is what bounds volume.
List endpoints return rows in data.items and a pagination object with next_cursor and has_more. Send next_cursor back unchanged as the cursor parameter for the next page, and stop when has_more is false. A handful of endpoints page with their own parameter instead; their reference pages name it.
No. A call that errors or finds nothing costs 0 credits. A live fetch costs the endpoint's price, or for a metered endpoint what it actually read. A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
A call fetches live unless a recent copy is in the shared cache, and every response says which with the cached field; a cached answer costs 2 credits. Add fresh=1 or send Cache-Control: no-cache to skip the cache; that call is charged at the normal price.
Collecting publicly available data is generally treated differently from accessing private data, but the answer depends on your jurisdiction, npm's terms and what you do with personal data afterwards. The API reads public data only. Talk to a lawyer for anything commercial.
npm API guides
The same key works for 60 more platforms
- TikTok scraper API
- LinkedIn scraper API
- Twitter/X scraper API
- YouTube scraper API
- Reddit scraper API
- Pinterest scraper API
- Bluesky scraper API
- Truth Social scraper API
- Snapchat scraper API
- Telegram scraper API
- Twitch scraper API
- Kick scraper API
- Rumble scraper API
- Kwai scraper API
- Douyin scraper API
- Xiaohongshu (RedNote) scraper API
- Quora scraper API
- TikTok Shop scraper API
- Weibo scraper API
- Zhihu scraper API
- Substack scraper API
- Nextdoor scraper API
- Amazon scraper API
- App Store scraper API
- Apple Music scraper API
- Behance scraper API
- Dailymotion scraper API
- Deezer scraper API
- DEV Community scraper API
- Discord scraper API
- Dribbble scraper API
- Fandom scraper API
- Flickr scraper API
- GitHub scraper API
- Google Ads Transparency scraper API
- Google News scraper API
- Google Trends scraper API
- Gumroad scraper API
- Hacker News scraper API
- Hugging Face scraper API
- Ko-fi scraper API
- Lemmy scraper API
- Letterboxd scraper API
- Linktree scraper API
- Lnk.Bio scraper API
- Mastodon scraper API
- Medium scraper API
- MyAnimeList scraper API
- Polymarket scraper API
- Product Hunt scraper API
- Shopify scraper API
- SoundCloud scraper API
- Spotify scraper API
- Stack Overflow scraper API
- Stan Store scraper API
- Steam scraper API
- Vimeo scraper API
- Wikipedia scraper API
- Yahoo Finance scraper API
- Yelp scraper API