The CLI client exposes all of the functionality of the FileCatalyst Client API via a command prompt. This opens up some impressive and important functionality:

Command-Line Ad Hoc Transfers

Naturally, if a tool may be accessed through a command line, this means that you can use it in a GUI-less environment. Whether you are working on a machine that does not have and is not meant to have a GUI, or if you simply prefer doing many of your daily tasks through a shell prompt, you can initiate a FileCatalyst transfer.

Initiate Transfers From a Script

Although the collection of flags and settings is fairly extensive for our CLI, once you have created the best command for your scenario, it is easily stored in and recalled from a script. These scripts in turn can be executed on-demand, but the more common scenario is to include the command as part of a larger action. For example, perhaps you have a daily backup job that runs a script which first collects files together from a variety of locations and stores them on a local or mapped drive. Once this is done, the script fires a command to the FileCatalyst CLI to transfer the collected files to a redundant offsite backup location. It is no more difficult to fine-tune this command with our full range of flags and parameters than it is to execute a simple task.

Initiate Transfers From an Application

If you are developing applications in a language that does not have its own native or wrapped FileCatalyst API, you often still have the option to execute commands against the command prompt. Your method uses a combination of defaults and user or configured input to construct an appropriate command. At that point, it is stored and triggered from a method call within your application. Since the application may bundle the CLI, it becomes a transparent experience for the end user.