feincms3-api-cli
The feincms3 content API from the command line, for people and for agents with a shell. It talks HTTP with a token, so it works against any site with the API, without the site's code. Standard library only.
uvx feincms3-api-cli --help # or: pip install feincms3-api-cli
Sites
A site is the API's URL and a token (create one in the admin, or with
./manage.py f3api_token):
f3api site add example https://example.com/api/ # asks for the token
f3api site list
f3api --site other list pages # the first site is the default
F3API_URL and F3API_TOKEN override the configured site. Sites are kept
in ~/.config/f3api/sites.json (readable by you only).
Reading
Everything prints JSON:
f3api resources
f3api schema # region sets and the plugins allowed per region
f3api schema pages.page # one type's fields
f3api list pages -f language_code=de -q angebot --fields title,path
f3api get pages 17 --expand # with meta.references
f3api find /de/angebot/
f3api plugin pages 17 pages.button 103
Writing
Writes are dry runs unless --apply is given: run once, look at the
result and its meta.warnings, then run again with --apply.
Writes send the ETag of the object as it was last read with f3api
(get, find, list --content), so a write fails with exit code 4 if
someone changed the object since, instead of overwriting their change.
Read it again, or pass --etag or --force.
f3api get pages 17 > page.json
f3api update pages 17 <<'EOF'
{"fields": {"title": "Unser Angebot"}}
EOF
f3api update pages 17 changes.json --apply
f3api content pages 17 regions.json --apply # replace the regions given
f3api update-plugin pages 17 pages.button 103 --apply <<'EOF'
{"button_label": "Kontakt"}
EOF
f3api create pages new-page.json --apply
f3api delete articles 3 --apply
f3api cache-clear pages 17
f3api upload team.jpg # prints {"upload": "…"} to use in fields
f3api batch subtree.json --apply # several writes in one transaction
In a batch, operations without an etag get the one last read.
Errors
Errors go to stderr with their paths:
f3api: 422 The data isn't valid.
fields.slug: This field is required.
content.main[2].fields.text: …
Exit codes: 0 done, 1 failed, 2 usage, 3 invalid data, 4 conflict (ETag, references), 5 not found, 6 not allowed.
Metadata
Release files for feincms3-api-cli 0.0.1
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 |
|---|---|---|---|---|
| feincms3_api_cli-0.0.1.tar.gz | 7.6 kB | With provenance | Details for feincms3_api_cli-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| feincms3_api_cli-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for feincms3_api_cli-0.0.1-py3-none-any.whl |
Total release size: 17.1 kB
Release files / feincms3_api_cli-0.0.1.tar.gz
| Download URL | feincms3_api_cli-0.0.1.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bcbf4baec19bf60d4ac8b543e6e050126cec411ede68e6c1d974de0a36bd24b2
|
|
BLAKE2b-256 checksum How to use checksums |
c90f48afe433b09a62d96de82a2a102f8400497c5055ebe9801f64ada034af8b
|
| 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 Nov 17, 2026.
Transparency logRelease files / feincms3_api_cli-0.0.1-py3-none-any.whl
| Download URL | feincms3_api_cli-0.0.1-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46974a3b4b3435230446a434098fcafdd21b622f9c39059f2a5fbd226940a5d6
|
|
BLAKE2b-256 checksum How to use checksums |
1e9b66400423944396f36679b48a3ccec32982ba27b14973b78baec0f92343a5
|
| 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 Nov 17, 2026.
Transparency logSecurity for feincms3-api-cli 0.0.1
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
Both files in this release have been uploaded with provenance metadata.
Attestation for feincms3_api_cli-0.0.1.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 Nov 17, 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.