What you get#
Onekey exposes PyPI as 9 endpoints behind one API key: 4 endpoints return one record (data is an object) and 5 endpoints return a list (data is an array). Every answer uses the same envelope (success, data, metadata, error), the cost is reported in metadata.credits_charged, and fields are mapped onto the unified schema so the code you write for PyPI also works for the rest of the developer platforms category.
Endpoints#
| Endpoint | What it does | Parameters | Credits | Status |
|---|---|---|---|---|
downloads_overall | Daily PyPI download counts by category (overall) for a project (pypistats.org). | name* | 5 | stable |
downloads_python_major | Daily PyPI download counts by category (python_major) for a project (pypistats.org). | name* | 5 | stable |
downloads_recent | Last-day/week/month PyPI download totals for a project (pypistats.org). | name* | 1 | stable |
downloads_system | Daily PyPI download counts by category (system) for a project (pypistats.org). | name* | 5 | stable |
files | Distribution files (wheels/sdist) of a specific PyPI release. | name*, version* | 5 | stable |
package | Metadata of a PyPI package (latest release). | name* | 1 | stable |
version | Metadata of one specific PyPI release. | name*, version* | 1 | stable |
versions | All release version numbers of a PyPI project (PEP 691 simple index). | name* | 1 | stable |
vulnerabilities | Known vulnerabilities of a specific PyPI release (from OSV). | name*, version* | 5 | stable |
A * marks a required parameter. Each endpoint name links to its reference page with the full parameter table, caching window and a recorded response.
Make a request#
This calls pypi.downloads_recent (1 credit, stable). Replace YOUR_API_KEY with your key; sign up, no card. 1,000 free credits cover the open-platform endpoints. Hard-to-reach platforms (X, TikTok, Instagram, Reddit, and others marked on their page) need a verified email and a purchased pack.
curl "https://api.onekey.dev/v1/pypi/downloads_recent?name=requests" \
-H "x-api-key: YOUR_API_KEY"Fields you get back#
These unified fields come back from PyPI, with the same names as on every other platform. The count is how many of its 9 mapped endpoints return the field; a field the source lacks is null, never missing. 10 platform-specific fields (ext.<name>) come on top, documented on each endpoint page.
| Field | Type | Endpoints |
|---|---|---|
content.createdAt | ISO 8601 date | 4 |
content.category | string | 3 |
content.title | string | 3 |
content.url | URL | 3 |
engagement.views | integer | 3 |
entity.name | string | 3 |
author.displayName | string | 2 |
content.id | string | 2 |
content.text | string | 2 |
package.version | string | 2 |
entity.description | string | 1 |
entity.status | string | 1 |
entity.type | string | 1 |
entity.url | URL | 1 |
package.dependencies | list of strings | 1 |
package.homepageUrl | URL | 1 |
package.license | string | 1 |
package.yanked | boolean | 1 |
The full schema is in Unified schema.
Pricing#
PyPI calls cost 1 to 5 credits, flat per endpoint. Free when served from cache (0.2 credit for a cached response over 100 KB). Invalid, failed or not-found calls are not charged. See pricing for credit packs.