Sphinx AutoAPI
Sphinx AutoAPI is a Sphinx extension for generating complete API documentation without needing to load, run, or import the project being documented.
In contrast to the traditional Sphinx autodoc, which requires manual authoring and uses code imports, AutoAPI finds and generates documentation by parsing source code.
For more information, see the full documentation.
Getting Started
The following steps will walk through how to add AutoAPI to an existing Sphinx project. For instructions on how to set up a Sphinx project, see Sphinx’s documentation.
Installation
AutoAPI can be installed through pip:
pip install sphinx-autoapiNext, add and configure AutoAPI in your Sphinx project’s conf.py.
extensions.append('autoapi.extension')
autoapi_dirs = ['path/to/source/files', 'src']When the documentation is built, AutoAPI will now generate API documentation into an autoapi/ directory and add an entry to the documentation in your top level table of contents!
To configure AutoAPI behaviour further, see the Configuration documentation.
Contributing
Running the tests
Tests are executed through tox.
toxCode Style
Code is formatted using ruff.
You can check your formatting using ruff format’s check mode:
tox -e formatYou can also get ruff to format your changes for you:
ruff formatRelease Notes
Release notes are managed through towncrier. When making a pull request you will need to create a news fragment to document your change:
tox -e release_notes -- create --helpVersioning
We use SemVer for versioning. For the versions available, see the tags on this repository.
License
This project is licensed under the MIT License. See the LICENSE.rst file for details.
3 maintainers
Metadata
3 maintainers
Release files for sphinx-autoapi 3.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sphinx_autoapi-3.9.0.tar.gz | 61.3 kB | With provenance | Details for sphinx_autoapi-3.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_autoapi-3.9.0-py3-none-any.whl | Python 3 | none | any | Details for sphinx_autoapi-3.9.0-py3-none-any.whl |
Total release size: 97.8 kB
Release files / sphinx_autoapi-3.9.0.tar.gz
| Download URL | sphinx_autoapi-3.9.0.tar.gz |
|---|---|
| Size | 61.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b2a47beac401c5fe437fbcd41c650c6cdc072234e576f56ef04456805bddabf
|
|
BLAKE2b-256 checksum How to use checksums |
4be812412b8c25b7e22fc6677ce84aceb278e856a688478e0a3c6eb211281c75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / sphinx_autoapi-3.9.0-py3-none-any.whl
| Download URL | sphinx_autoapi-3.9.0-py3-none-any.whl |
|---|---|
| Size | 36.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ecba31815322b00e9fb01973c210ba651522d25f92705a4384fd6c429c5a28f
|
|
BLAKE2b-256 checksum How to use checksums |
3ac4d08333f57470065ca1e551d907f7cdd7ee873da436f6f352b773276e7720
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logSecurity for sphinx-autoapi 3.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sphinx_autoapi-3.9.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
