npm
npm registry data for any Node.js package: metadata, dist-tags, versions, dependencies, download counts, search and maintainers.
/npm/v1/package1 creditfull package metadata (latest version normalized)
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| name | required | — | Exact npm package name, e.g. 'react'. Scoped names like '@scope/pkg' work. |
/npm/v1/versions1 creditpaginated version list for a package
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| name | required | — | Exact npm package name, e.g. 'react'. Scoped names like '@scope/pkg' work. |
| page = 1 | optional | 1– | 1-based page number for paginated lists (versions / search). |
| page_size = 50 | optional | 1–250 | Results per page (1-250, default 50). Larger values are clamped. |
/npm/v1/version1 creditsingle version metadata
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| name | required | — | Exact npm package name, e.g. 'react'. Scoped names like '@scope/pkg' work. |
| version | required | — | Exact version string to fetch (e.g. '18.2.0', '2.31.0'). |
/npm/v1/dependencies1 creditruntime + dev dependencies for a version (latest if omitted)
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| name | required | — | Exact npm package name, e.g. 'react'. Scoped names like '@scope/pkg' work. |
| version | optional | — | Optional exact version; omit to use the latest published version. |
/npm/v1/downloads1 creditdownload statistics (npm: period=last-day|week|month|year; pypi: recent day/week/month)
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| name | required | — | Exact npm package name, e.g. 'react'. Scoped names like '@scope/pkg' work. |
| period = last-month | optional | last-day · last-week · last-month · last-year | npm download window (rejects unknown values). Ignored for PyPI, which always returns recent last-day/last-week/last-month totals. |
/npm/v1/search2 creditssearch packages (npm: registry API; pypi: libraries.io→HTML→ranked simple-index+enrich)
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| query | required | — | Free-text search keywords matched against package name/description. |
| page = 1 | optional | 1– | 1-based page number for paginated lists (versions / search). |
| page_size = 20 | optional | 1–250 | Results per page (1-250, default 20). Larger values are clamped. |
| from | optional | 0– | npm search only: raw result offset (alternative to page). Page forward with meta.next_from. |
/npm/v1/maintainer1 creditmaintainer/author records for a package
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| name | required | — | Exact npm package name, e.g. 'react'. Scoped names like '@scope/pkg' work. |
curl -X POST https://api.reefapi.com/npm/v1/package \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"name":"react"}'{
"ok": true,
"data": { /* the result */ },
"meta": {
"latency_ms": 240,
"record_count": 12,
"completeness_pct": 100
},
"error": null
}Measured at 60 requests a second across the fleet, with no central bottleneck. Volume pricing is on request, and per-key limits are raised for high-volume accounts.
Tell us a site we do not cover yet and it becomes an engine. A customer asked for bestprice.gr on a Sunday and it was in the catalog the next day.
Median time from a question in the live chat to the first answer, measured across every answered conversation. Setup help included, no support tier to buy.
No per-site plans and no separate subscriptions. One key and one credit pool across the whole catalog, so adding a source costs nothing up front.
Planning something large? Tell us the volume and the sources and we will come back with what it costs and what we would have to build.