fmu-settings-api
fmu-settings-api is the FastAPI backend for the fmu-settings application.
Usage
This application is primarily invoked by
fmu-settings-cli and is meant
to be used together with
fmu-settings-gui. It depends
mostly on fmu-settings to work with
.fmu/ configuration directories within the FMU context.
With fmu-settings-cli installed, to run the API by itself just
fmu settings api
An authorization token is required to create a session. When developing you can print this token to the the terminal with
fmu settings api --print-token
It's useful to be able to reload while developing.
fmu settings api --print-token --reload
API Documentation
The routes have documentation on them. To view them, and work with the API go
to localhost:8000/docs (or whatever your port may end up being).
Configuration
Configuration should largely be handled by the GUI when they are being run
together. When developing you will want to be able to access different
endpoints. You can configure some of these values with .env and scripts in
the scripts/ directory.
A sample.env is included here. To get your own SMDA subscription
key you may go to the internal Equinor API self-service website. Copy
sample.env to .env and fill in the correct values.
Access token
Accessing services through this API requires a valid access token. You can
acquire one with the scripts/get_token.py script. This
script will open a small server, authenticate you with SSO, and store your
access token to .token. You may then use this as you need.
Developing
Clone and install into a virtual environment.
git clone git@github.com:equinor/fmu-settings-api.git
cd fmu-settings-api
# Create or source virtual/Komodo env
pip install -U pip
pip install -e ".[dev]"
# Make a feature branch for your changes
git checkout -b some-feature-branch
Run the tests with
pytest -n auto tests
Ensure your changes will pass the various linters before making a pull request. It is expected that all code will be typed and validated with mypy.
ruff check
ruff format --check
mypy src tests
See the contributing document for more.
3 maintainers
Metadata
3 maintainers
Release files for fmu-settings-api 1.5.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 | |
|---|---|---|---|
| fmu_settings_api-1.5.1.tar.gz | 273.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fmu_settings_api-1.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 367.5 kB
Release files / fmu_settings_api-1.5.1.tar.gz
| Download URL | fmu_settings_api-1.5.1.tar.gz |
|---|---|
| Size | 273.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e8decd67e28566a1642ce353b309fa0c64c24c2a029adf7613632ea0bb74979
|
|
BLAKE2b-256 checksum How to use checksums |
a75ce8ccaf405558b1b70793cd077756bac9b301cf245f6ec721f895f46a2d98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency logRelease files / fmu_settings_api-1.5.1-py3-none-any.whl
| Download URL | fmu_settings_api-1.5.1-py3-none-any.whl |
|---|---|
| Size | 94.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e0ded1995f16f5f09f1db753a76d31a1aca2f8d6b827a51b9852f9fc4e786a83
|
|
BLAKE2b-256 checksum How to use checksums |
4330297fda232ec7836509b991ab861997185f33a7b020ddf3459db66692750e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency log
