npm hub

npm Org API

An org or scope resolved to its stored profile, with the type npm keeps and the number of packages it can publish.

GET /v1/npm/org

1 credit Failed requests are free

About this endpoint

GET /v1/npm/org?name=babel returns data.org with name, type, fullName, githubUsername, description, requiresTwoFactor, createdAt, updatedAt, orgs and packagesTotal. The /org/ route can return a user scope as well as an org, and type says which record npm stores, so trust that field rather than the URL.

Names are case-sensitive. A name npm does not have returns lookupStatus: not_found with data.org: null. Use GET /v1/npm/org/packages for the package list. For a personal account, GET /v1/npm/user is the direct route, though both can resolve scopes.

npm Org API FAQ

What does the type field mean?

type is user or org, as stored by npm. The /org/ route accepts a scope name and can return a user scope, so read type instead of assuming every answer is an organisation.

Does an org profile include its packages?

No. This route returns the profile only. Call GET /v1/npm/org/packages to page the packages, 25 per page.

What does packagesTotal count?

The number of packages the org or scope can publish, when a count is available. It is null when no count is available. The package list route is the authoritative list.

What happens for an unknown org?

HTTP 200 with data.lookupStatus not_found and data.org null. A differently cased name can miss because lookup is case-sensitive.

What does the request cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.