Blackfynn Configuration File

NOTE: The recommended way for managing settings is using the Blackfynn Command Line Tool ( )

Blackfynn stores settings and connection information in your Blackfynn configuration file. Advanced users might want to edit their Blackfynn configuration file directly for control of the client libraries.

This document outlines the configuration options shared between the various clients. For additional options specific to each client, see the relevant documentation:

  1. Python client


Your configuration file is located in your .blackfynn directory. The .blackfynn directory is found in the $HOME directory (Mac/Linux) or the User directory (Windows).

Full path: $HOME/.blackfynn/config.ini


The config file is in INI <>_ format. There are three types of sections: [global], [agent], and [<profile>]. You can have as many [<profile>] sections as you want

Example of the config.ini file:

# Global settings


    default_profile = default

    # Profiles


    api_token =  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

    api_secret = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx


    use_cache = true

    api_token = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

    api_secret = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx


    api_token = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

    api_secret = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

    # Settings for the Blackfynn CLI Agent


    uploader = true

    cache_page_size = 100000

    cache_soft_cache_size = 5000000000

    proxy_local_port = 8080

    timeseries_local_port = 9090

    proxy = true


Environment Variables

It is also possible to set configuration options using environment variables

Note: Environment variables (if present) override any profile-defined settings in your Blackfynn Configuration File. They are useful for terminal-specific settings.

To switch between profiles in a given terminal session, set the environment variable:

    BLACKFYNN_PROFILE="your profile name" 

Alternatively, you can specify your token/secret directly:



To control the verbosity of the client's logging, set `BLACKFYNN_LOG_LEVEL`:


Did this answer your question?