100 free credits. No credit card required.Start building
Logo
PyPI logoPyPI API

Get PyPI project release data with one API

Read any PyPI project release with its dependencies, supported Python versions, links and every file's sha256 digest, as structured JSON with one SocialCrawl API key. Reads are priced in credits.

PyPI logo
/v1/pypi

1 active endpoint. Project release detail.

  • GET /v1/pypi/project

What PyPI endpoints does SocialCrawl ship?

One read endpoint for public PyPI projects. Read the latest release or any version in full.

/v1/pypi/project

One release of a project by name or link, the latest by default: summary, long description, version, supported Python versions, declared dependencies, project links, licence, yanked flag, and every file with its download link, size, sha256 digest, package type and upload time. A project or version PyPI does not have answers 404 and is not charged. Standard tier (1 credit).

project or url, version

PyPI API1 endpoint supported
View docs
Packages

Returns one release of a PyPI project with its dependencies, supported Python versions, links and every file with its sha256 digest.

Use it to check a Python dependency, see what a release requires, or verify the files you download.

1 credit

GET/v1/pypi/project?project=requests
$ curl https://www.socialcrawl.dev/v1/pypi/project?project=requests \
    -H "x-api-key: sc_YOUR_API_KEY"
idle
// Running this live needs your own API key. Hit "Try it" to see an example response

How the PyPI API works

PyPI is a normal SocialCrawl data surface. You call GET /v1/pypi/… with an API key, spend credits on live misses, and get a single JSON envelope back.

Authenticate every call

Send your key in the x-api-key header. No PyPI account is needed for public reads. The same key works across SocialCrawl platforms.

GET with query params

Project takes project or url, and version. Formats are validated before any charge.

Pay in credits, not seats

Every PyPI route costs 1 credit. Cache hits cost 0.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.

The usual integration chain

Most products read the releases they depend on, then check them again when a new one ships.

01Read the latest release
GET /v1/pypi/project?project=…

Post with the version, requires_dist and files

One call shows what the project needs and ships.

02Read a pinned version
GET /v1/pypi/project?project=…&version=…

Post for the exact release you install

Verify each file against its sha256 digest.

03Compare releases
GET /v1/pypi/project?url=…

Post for the next version

See changed dependencies before an upgrade.

request
GET /v1/pypi/project?project=requests
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

GET /v1/pypi/project?project=requests&version=2.31.0
response envelope
{
  "success": true,
  "data": {
    "post": {
      "id": "requests",
      "url": "https://pypi.org/project/requests/2.31.0/",
      "content": { "text": "Python HTTP for Humans." },
      "ext": {
        "title": "requests",
        "pypi": {
          "version": "2.31.0",
          "requires_python": ">=3.7",
          "files": [{ "filename": "requests-2.31.0-py3-none-any.whl", "sha256": "58cd2187…" }]
        }
      }
    }
  },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.

Postproject

post.id (name), ext.title, url, content.text (summary), ext.description, ext.pypi version, requires_python, requires_dist, files[] with sha256

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint. PyPI is not a sidecar.

  1. 01

    Edge receives the call

    Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).

  2. 02

    Validate, then debit

    Registry lookup finds the pypi route. Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before the read starts.

  3. 03

    Cache or fetch

    A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public data is read live, with retries on 5xx or network errors and a circuit breaker if the source is unhealthy.

  4. 04

    Normalize and return

    PyPI data is mapped to the Post archetype with the PyPI-only facts in ext.pypi, validated, then wrapped in the success envelope and logged for billing audit.

Billing rules that matter in production

  • project: 1 credit
  • Cache hit: 0 credits
  • Empty / hard fail: auto-refund
  • Bad params: 400, never charged
  • No credits: 402, never charged
  • Unknown project or version: 404, never charged
  • Every release file with its sha256
  • No author email addresses
  • No publishing or account data

How SocialCrawl gets PyPI data

PyPI data is public. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.

What PyPI is for this API

Public projects and releases on the Python Package Index, with their dependencies and release files.

How SocialCrawl reaches it

Public data is read on request and normalized server-side, within each source's published usage rules.

What leaves our edge

Post for a release, the shared shape. The PyPI-only facts sit in ext.pypi.

What we do not ship live

No publishing, private indexes, author email addresses or account data.

field map sketch
name, version, summary→ post.*name, version, summary, links
requires_python, requires_dist→ post.ext.pypirequires_python, requires_dist, licence
release files with sha256→ post.ext.pypi.filesrelease files with sha256

What this API is used for

The jobs this API is most often used for.

1active PyPI endpoints in the registry
1credit per call on every PyPI route

Dependency research, release monitoring and supply-chain checks

Callers read the releases their code depends on, and read them again when a new version ships. Releases with their declared dependencies and every file's sha256 digest in the shared Post schema, from the same key as the rest of the catalog.

Live misses read the public source on request. Repeat calls hit cache and cost 0 credits.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Dependency review

Python, CI jobs

read each release a project pins and check its supported Python versions and requires_dist.

Release monitoring

Node, scheduled jobs

read the latest release of each tracked project on a schedule to catch a new version.

Supply-chain checks

Go, security tooling

read a release's files and compare each sha256 digest with what was installed.

How to call the PyPI API

Every PyPI route is 1 credit. Cache hits are free.

curl "https://www.socialcrawl.dev/v1/pypi/project?project=requests" \
  -H "x-api-key: sc_your_api_key_here"
curl "https://www.socialcrawl.dev/v1/pypi/project?project=requests&version=2.31.0" \
  -H "x-api-key: sc_your_api_key_here"
PyPI logoPyPI on SocialCrawl

Same key as the rest of the catalog

Endpoints

What data does the PyPI API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

Contact us
What does the SocialCrawl PyPI API cover?
It covers 1 endpoint: Project. It reads one release of a PyPI project with its dependencies and files, in the same unified JSON as the other 94 platforms.
Can I read an older release?
Yes. Pass version, for example 2.31.0, or a release's PyPI link. The latest release is the default.
Can I verify the files?
Yes. Every file in post.ext.pypi.files carries its sha256 digest, size and download link.
Do I get the author's email address?
No. Author and maintainer email addresses are not returned.
How much does it cost?
Each call costs 1 credit, cache hits are free, and a project or version PyPI does not have answers 404 and is not charged. You start with 100 free credits.
Is scraping PyPI data legal?
SocialCrawl returns publicly available PyPI data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction. You are responsible for complying with PyPI's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.
PyPI scraping API vs the official PyPI API: what's the difference?
With SocialCrawl there is no app review or approval queue. Sign up and call PyPI endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Read the PyPI API reference in the docs

🤖 AI agent or LLM? Read this page as markdown