# PEP 691: JSON-based Simple API for Python Package Indexes

**URL:** <https://discuss.python.org/t/pep-691-json-based-simple-api-for-python-package-indexes/15553>\
**Category:** PEPs\
**Created:** [May 5, 2022, 10:48pm UTC](https://discuss.python.org/t/pep-691-json-based-simple-api-for-python-package-indexes/15553 "2022-05-05T22:48:25Z")\
**Posts on this page:** 1\
**Showing post:** 70

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [June 24, 2022, 11:06pm UTC](https://discuss.python.org/t/pep-691-json-based-simple-api-for-python-package-indexes/15553/70 "2022-06-24T23:06:14Z")

</div>

I touched up the PEP via [PEP 691: touch up (#2668) · python/peps@f1af4a7 · GitHub](https://github.com/python/peps/commit/f1af4a7c886cb9fb4bbb536923cccfd3b555a2ab) , but it was mostly grammar and formatting stuff.

After reading the PEP, I’m happy to pronounce my acceptance of the PEP as its delegate! While I expect some things will get added to the spec in the future (e.g. `application.json` is going to get debated pretty fast once this rolls out, an optional `url` key for each project in the index object), the PEP covers all the details in PEP 503 in a JSON encoding and in a way that code can gracefully handle the transition.

---

_[View the full topic](https://discuss.python.org/t/pep-691-json-based-simple-api-for-python-package-indexes/15553)._