# Asking for clarification about the status of the APIs

**URL:** <https://discuss.python.org/t/asking-for-clarification-about-the-status-of-the-apis/18558>\
**Category:** Packaging\
**Created:** [August 29, 2022, 2:27pm UTC](https://discuss.python.org/t/asking-for-clarification-about-the-status-of-the-apis/18558 "2022-08-29T14:27:55Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [August 29, 2022, 6:26pm UTC](https://discuss.python.org/t/asking-for-clarification-about-the-status-of-the-apis/18558/6 "2022-08-29T18:26:51Z")

</div>

IMO, the `releases` key can’t be removed from the project page _until_ the simple API has a list of releases. I’m planning on writing a PEP to cover this:

> [@Backwards Incompatible Change to PyPI JSON API](https://discuss.python.org/t/backwards-incompatible-change-to-pypi-json-api/17154/10):
>
> If it helps, I’d be happy to write a PEP that updated PEP 691 to say:
> 
> 1. The `projects` element of the root URL should return `{"name": "Frob", "versions": ["0.1", "0.2"]}`, i.e. adding a “versions” key.
> 2. The elements of the `files` item in the project details value should add a new key, `upload_time` containing an ISO 8601 date string.
> 
> which are the two items we’ve now identified as not available except in the JSON API (if we ignore the project metadata).

---

_[View the full topic](https://discuss.python.org/t/asking-for-clarification-about-the-status-of-the-apis/18558)._