InsightSocial
GET /v1/npm/registry/packagesbeta

npm Registry Packages API

List npm package names in registry key order, with an opaque cursor.

20 credits a call · cursor pagination · failed calls free · 10 free calls to start

curl "https://api.insightsocial.app/v1/npm/registry/packages" \
-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
200 OKJSON
{
"success": true,
"platform": "npm",
"endpoint": "/v1/npm/registry/packages",
"schema_version": "2",
"data": {
"<field>": "<value>"
},
"pagination": {
"next_cursor": "<string | null>",
"has_more": "<boolean>"
},
"unavailable": [],
"credits_used": "<integer>"
}

Parameters

Query parameters for GET /v1/npm/registry/packages. Send your key in the x-api-key header.

NameRequiredDescription
afterNoInclusive start: the named package is the first row. Leave it out to start at the beginning.
limitNoNames per page, 1 to 1000. Default: 1000.
cursorNoPass pagination.next_cursor from the previous response to get the next page. Keep the other parameters the same.

Response

This endpoint is beta: data holds the platform's own fields under our naming rules (snake_case keys, string ids, ISO times where the platform gives a timestamp) rather than a unified post or profile, and those fields may change.

Every field, error and example is in the npm Registry Packages API reference.

How much does the npm Registry Packages API cost?

20 credits per successful call.

  • Failed calls are free

    A call that errors or finds nothing costs 0 credits.

  • Know the price first

    Add dry_run=1 and the response quotes the call without making it. Nothing is charged.

  • One balance

    API calls and Chrome extension exports share the same credits, on the free plan too.

npm Registry Packages API: frequently asked questions

Send GET /v1/npm/registry/packages with its query parameters and your key in the x-api-key header. List npm package names in registry key order, with an opaque cursor.