Installation

forti-api is header-only. nlohmann/json 3.12.0 ships with it (installed under forti_api/third_party, so it never conflicts with a system nlohmann-json); libcurl is the only system dependency. A C++23 compiler is required; forti-api is tested with GCC 13 and 14 and with Apple Clang.

Debian and Ubuntu

libforti-api-dev is published to the ValkyrianLabs APT repository:

1sudo install -d -m 0755 /etc/apt/keyrings2sudo curl -fsSL https://apt.valkyrianlabs.com/pubkey.gpg \3  -o /etc/apt/keyrings/valkyrianlabs.gpg4sudo chmod 0644 /etc/apt/keyrings/valkyrianlabs.gpg5 6echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/valkyrianlabs.gpg] https://apt.valkyrianlabs.com stable main" | \7  sudo tee /etc/apt/sources.list.d/valkyrianlabs.list > /dev/null8 9sudo apt update10sudo apt install -y libforti-api-dev

The package installs the headers to /usr/include/forti_api and a pkg-config file:

1c++ -std=c++23 app.cpp $(pkg-config --cflags --libs forti-api)

With Meson, dependency('forti-api') finds it through pkg-config.

Homebrew (macOS and Linux)

1brew install valkyrianlabs/tap/forti-api

Recent Homebrew versions ask you to trust a third-party tap first (brew trust valkyrianlabs/tap). The formula installs the headers and forti-api.pc into the Homebrew prefix; libcurl comes from the system. Build with c++ -std=c++23 app.cpp $(pkg-config --cflags --libs forti-api).

Vendoring

Copy include/ and third_party/nlohmann/include/ from the repository into your project, add both to the include path and link libcurl (-lcurl). Meson projects can also use forti-api as a subproject: dependency('forti-api') resolves to it.

From source

1# Ubuntu: sudo apt install meson ninja-build g++ pkgconf libcurl4-openssl-dev2# macOS:  brew install meson ninja       (libcurl comes with the SDK)3meson setup build4meson install -C build

The headers install to <prefix>/include/forti_api and forti-api.pc to <prefix>/share/pkgconfig.