Skip to main content

Command-Line Interface (CLI) Configuration

Appcircle CLI is a command-line interface designed to use Appcircle from the terminals. The Appcircle CLI tool, which is executed directly from the terminal, provides users with a streamlined command-driven experience for efficient management of Appcircle.

The Appcircle CLI is user-friendly and versatile, offering a range of commands to enhance backend control. You can start builds, download build artifacts, publish applications on the Enterprise App Store, and do more.

Additionally, its scriptable nature allows for easy automation through shell scripts, enabling users to automate tasks and integrate the CLI into existing workflows effortlessly.

For detailed usage, you can head over to the Appcircle CLI documentation.


To configure Appcircle CLI to use your self-hosted Appcircle, you need a Personal API Token for authentication. Also, you need the api and the auth URLs of the Appcircle server.

1. Create a Personal API Token

For the Appcircle CLI to authenticate to your self-hosted Appcircle, you need to create a Personal API Token and configure the Appcircle CLI to use it.

You can follow the Generating and Managing Personal API Tokens page to create one.

2. Find out the Appcircle server URLs

To find these URLs, you have two ways.

  1. Change the subdomain of an Appcircle URL and test if it is working.
  2. Get the URLs from the Appcircle server configuration.

Change the subdomain with api and auth for the default configuration

To find out the api and the auth URL, you can check the URL that you are using to access the Appcircle web UI (dashboard) and then change its subdomain according to the format.

For example, if you are using to access the Appcircle web UI,

  • Change my to api for the API_HOSTNAME.
    • It should be
  • Change my to auth for the AUTH_HOSTNAME.
    • It should be

You can test the API URL access by running the command below.

curl -v

If you are facing a connectivity error, there are two possible problems:

  1. There is no network access between the computer that runs the curl command above and the Appcircle server.
  2. Or the API URL is not correct. In order to get the correct URL, you can follow the title below.

Get the subdomains from the Appcircle server for any type of configuration

To get the api and the auth URL, you should login to the Appcircle server and follow the steps below:

  • Change the directory on the Appcircle server.
cd appcircle-server
  • Update the environment variable PATH with the required dependencies.
export PATH=$PATH:$(pwd)/deps/bin
  • Get the api and auth URL from the configuration file of your project.

spacetech in the example below is an example project name.

To find out your projects, list the content of the ./projects directory.

ls -l ./projects
yq '.apiGateway.external.url' ./projects/spacetech/export/.global.yaml && \
yq '.keycloak.external.url' ./projects/spacetech/export/.global.yaml

You can test the API URL access by running the command below.

curl -v

If you are still getting a connectivity error, you should check the network access between the host that runs curl and the Appcircle server.

Configure CLI to Use Your Self-Hosted Server

By default, Appcircle CLI is configured to interact with the Appcircle cloud. But with a few commands, you can change this behavior and use your own self-hosted Appcircle server with the CLI.


We are assuming that you have already installed the Appcircle CLI and that it is ready to use.

Follow the installation instructions here to install Appcircle CLI if it's not ready to use.

To test, you can open a terminal and run the command below in your terminal.

appcircle --version

If you see the Appcircle CLI version without any errors, you are ready to configure the tool.

To configure the Appcircle CLI to use with the self-hosted Appcircle server follow the steps below.

1. Add a new configuration with any desired name.

appcircle config add "${CONFIGURATION_NAME}"

For example;

appcircle config add "spacetech"

2. Set the required URLs to communicate with the self-hosted Appcircle server.

appcircle config set API_HOSTNAME ''
appcircle config set AUTH_HOSTNAME ''

3. Set the Personal API Token for authentication on the server.

appcircle login --pat "${PERSONAL_API_TOKEN}"

For example;

appcircle login --pat "TTk0...RhNw=="

If you face any self-signed certificate error, for example, "self-signed certificate in certificate chain", check the Trusting Certificate section for troubleshooting.

You can check the configuration with the command below.

appcircle config list

You should see the current (active) configuration, the path of the config.json file, and server URLs per configuration.

You can also configure the Appcircle CLI in interactive mode.

appcircle -i

You should use the relevant menu item and follow the instructions there that are similar to the steps above.

When you successfully log in with the Appcircle CLI, you can list the build profiles with the command below.

appcircle listBuildProfiles

For detailed usage information about the Appcircle CLI, you can refer to the Appcircle CLI documentation.

Self-Signed Certificates

If you are using a self-signed SSL certificate on the self-hosted Appcircle server and the certificate is not trusted on your host, you may face an error like below while trying to run the Appcircle CLI tool.

$ appcircle login --pat "TTk0...RhNw=="

self-signed certificate in certificate chain undefined

That error occurs when the root CA certificate or the self-signed certificate of the Appcircle server is not trusted on your host.

You can trust the SSL certificate of the Appcircle server to secure the network between the CLI and the server, or you can disable certificate verification.


Disabling certificate verification is risky and not recommended.

For secure and reliable communication, you should trust the SSL certificate.

You can trust the SSL certificate of the Appcircle server with the Appcircle CLI tool itself to make sure all the requests are secured and trusted.

You should already have configured the Appcircle CLI tool for the self-hosted Appcircle server.


This command is supported on MacOS and Linux operating systems only.

If you are a Windows user, you can download the SSL certificate and make it trusted under the MMC menu in Windows.


Trusting the SSL certificate is supported for Appcircle CLI version 1.1.1 or later.

For older versions, you should upgrade the Appcircle CLI, or although it's not recommended, you can disable the SSL verification.

To trust the SSL certificate of the configured Appcircle server, run the config trust subcommand of the Appcircle CLI.

appcircle config trust

The command may ask for the sudo password for some system-wide operations. You should be sudoer.

When the script successfully trusts the certificate, you will see an output like below.

[+] OS: Darwin
Appcircle URL is valid:
[-] Allowing addition of root certificates
[-] Getting root certificate of ''
Found cert that has same subject and issuer
[+] Certificate written to ''
[+] Subject: Crtforge ROOT CA,
[+] Expires on: Jan 31 10:12:39 2044 GMT
[-] Adding '' to Keychain
YES (0)
YES (0)
[-] Adding Certs to Nodejs
The line already exists in /Users/spacetech/.zshrc
[-] Verifying connection to ''
[+] Verification successful!
The root cert has been trusted successfully.
You must open a new terminal session for the changes to take effect.

Now you should open a new terminal for the changes to take effect.

In a new terminal session, you can run the appcircle commands securely without any certificate problems.

Disabling SSL certificate verification removes a critical layer of security, leaving the communication vulnerable to a variety of threats, including those associated with man-in-the-middle attacks, data integrity issues, and trustworthiness concerns.

Proper SSL certificate validation is essential for ensuring the authenticity and security of the communication between the Appcircle CLI and the Appcircle server.

It's crucial to prioritize security measures to protect sensitive data and maintain the integrity of your system.


While we do not recommend it, you have the choice to accept the mentioned risk by selectively disabling certificate verification specifically for the Appcircle CLI.

It can be used when you have problems trusting the SSL certificates.

To disable the SSL certificate verification just for the Appcircle CLI tool, you should add a prefix to the appcircle command.


SSL and TLS are the same concepts for this document. So, TLS certificates are also known as SSL certificates.

alias appcircle="NODE_TLS_REJECT_UNAUTHORIZED=0 appcircle"

After disabling SSL certificate verification, there will be a warning saying SSL verification is disabled.

$ appcircle listBuildProfiles

(node:74065) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)

You can ignore it. All the subcommands will work as they should.

Need help?

Get help from Appcircle's support team, or see how others are using Appcircle by joining our Slack Channel.

Preview of Slack