User Settings & Environment Variables
This page outlines configuring the OpenBB Platform with user settings and environment variables.
User Settings
User settings are stored locally, ~/.openbb_platform/
, as a JSON file, user_settings.json
. It is read upon initializing the Python client, or when the Fast API is authorized. If the file does not exist, it will be created on the first run.
This file stores:
This is an example of how it might look after setup:
{
"credentials": {
"fmp_api_key": "REPLACE",
"polygon_api_key": "REPLACE",
},
"preferences": {
"data_directory": "~/OpenBBUserData",
"export_directory": "~/OpenBBUserData/exports",
"request_timeout": 15,
"metadata": true,
"output_type": "OBBject"
},
"defaults": {
"commands": {
"equity.price.historical": {
"provider": "fmp"
},
"equity.fundamental.balance": {
"provider": [
"intrinio",
"fmp",
"polygon"
]
},
}
}
}
Preferences
Preference | Default | Options | Description |
---|---|---|---|
data_directory | /home/OpenBBUserData | Any path. | When launching the application for the first time this directory will be created. It serves as the default location where the application stores usage artifacts such as logs and exports. |
export_directory | /home/OpenBBUserData/exports | Any path. | The OpenBB Charting Extension provides the capability to export images in various formats. This is the directory where it attempts to save such exports. |
cache_directory | /home/OpenBBUserData/cache | Any path. | The directory where http requests and database caches are stored, for functions with caching. |
user_styles_directory | /home/OpenBBUserData/styles/user | Any path. | The OpenBB Charting Extension supports custom stylization. This directory is the location where it looks for user-defined styles. If no user styles are found in this directory the application will proceed with the default styles. |
charting_extension | openbb_charting | ["openbb_charting"] | Name of the charting extension to be used with the application. |
chart_style | dark | ["dark", "light"] | The default color style to use with the OpenBB Charting Extension plots. Options include "dark" and "light". |
plot_enable_pywry | True | [True, False] | Whether the application should enable PyWry. If PyWry is disabled the image will open in your default browser otherwise it will be displayed within your editor or in a separate PyWry window. |
plot_pywry_width | 1400 | Any positive integer. | PyWry window width. |
plot_pywry_height | 762 | Any positive integer. | PyWry window height. |
plot_open_export | False | [True, False] | Controls whether the "Save As" window should pop up as soon as the image is displayed." |
table_style | dark | ["dark", "light"] | "The default color style to use with the OpenBB Charting Extension tables. Options are "dark" and "light"" |
request_timeout | 15 | Any positive integer. | Specifies the timeout duration for HTTP requests. |
metadata | True | [True, False] | Enables or disables the collection of metadata which provides information about operations including arguments duration route and timestamp. Disabling this feature may improve performance in cases where contextual information is not needed or when the additional computation time and storage space are a concern. |
output_type | OBBject | ["OBBject", "dataframe", "numpy", "dict", "chart", "polars", "llm"] | Specifies the type of data the application will output when a command or endpoint is accessed. Note that choosing data formats only available in Python such as dataframe , numpy or polars will render the application's API non-functional. |
show_warnings | True | [True, False] | Enables or disables the display of warnings. |
- If a
OpenBBUserData
folder in not in the home directory, the application will create one on first run. The user preferences with paths all default to this folder, be it exports, styles or data - this can be changed at any time to suit. - The
OpenBBUserData
will still be created even if preferences are not pointing to it, this is because the application needs a place to store logs and other artifacts. - One way to export files or images from the OpenBB Platform is to leverage that functionality from the OpenBB Charting Extension. The
export_directory
preference is the location where the extension will attempt to save CSV and image files.
Defaults
Here you can define provider defaults for Python commands, if no provider
argument is explicitly sent when the command runs. You can choose from 2 options:
- Single provider: this provider will be selected by default for the given command.
- Priority list: the first provider in the list with all required credentials setup will be used.
{
...
"defaults": {
"commands": {
# single provider
"equity.price.historical": {
"provider": "fmp"
},
# priority list
"equity.fundamental.balance": {
"provider": [
"intrinio",
"fmp",
"polygon"
]
},
}
}
}
- If no configuration is specified the command will use the default priority list. This is the list of available providers for the command sorted alphabetically.
Environment Variables
Environment variables are defined in a .env
file. If this file does not exist, create it inside the same folder user_settings.json
is located.
OPENBB_DEBUG_MODE
: enables verbosity while running the programOPENBB_DEVELOP_MODE
: points hub service to .co or .devOPENBB_AUTO_BUILD
: enables automatic SDK package build on importOPENBB_CHARTING_EXTENSION
: specifies which charting extension to useOPENBB_API_AUTH_EXTENSION
: specifies which authentication extension to useOPENBB_API_AUTH
: enables API authentication for command endpointsOPENBB_API_USERNAME
: sets API usernameOPENBB_API_PASSWORD
: sets API password
Variables can be defined for current session only.
import os
os.environ["OPENBB_DEBUG_MODE"] = "True"
from openbb import obb
Proxy Networks
An environment variable can be set, in the .env
file, to direct the Requests library to a specific address and port.
HTTP_PROXY="<ADDRESS>" or HTTPS_PROXY="<ADDRESS>”
For example:
HTTP_PROXY="http://10.10.10.10:8000"