Command line interface to API Builder
No setup needed - just use the API Builder command directly (see below)
-
Create a token for your user account
-
Create a configuration file in ~/.apibuilder/config Example File:
[default] token = <your API token> -
Verify that your configuration file is valid:
bin/read-config
List all organizations that you have access to:
bin/apibuilder list organizations
List all applications that belong to a specific organization:
bin/apibuilder list applications <organization key>
List all versions of a particular application
bin/apibuilder list versions <organization key> <application key>
Note since the GET requests in API Builder are paginated, you might need to paginate. Where pagination is required, we use two environment variables: LIMIT, OFFSET
LIMIT=10 OFFSET=10 bin/apibuilder list organizations
Invoke a code generator from the command line
bin/apibuilder code <organization key> <application key> <version> <generator> <target dir> [<filename> ...]
For example, to generate a play 2.3 client for the latest version of apibuilder itself:
bin/apibuilder code apicollective apibuilder-api latest play_2_5_client .
Each code generator returns a list of files. To download a specific file:
bin/apibuilder code apicollective apibuilder-api latest play_2_5_client . [<filename> ...]
For example:
bin/apibuilder code apicollective apibuilder-api latest http4s_0_17 . ApicollectiveApibuilderApiV0Client.scala ApicollectiveApibuilderApiV0Server.scala
The file names support wildcard expansion (? for a single character, * for zero or more), e.g:
bin/apibuilder code apicollective apibuilder-api latest http4s_0_17 . *ApiV?Client*.scala
To view a list of available generators visit apibuilder.io/generators
Upload a new version of an api given the json descriptor.
bin/apibuilder upload <organization key> <application key> <file> --version <version> [--force] [--silent] [--update-config <optional path>]
For example:
bin/apibuilder upload apicollective apibuilder-api apibuilder-api/api.json --version 1.0.1
The --force flag will allow you to re-upload an api.json even if there are no changes since the previously uploaded version.
When using the --silent flag, the suggested tag will be automatically used. This is useful for automated uploading via git hooks and/or CD pipelines.
The --update-config flag tells the cli to update the local .apibuilder/config with the new version of the given api. It uses either the default path or the path given in the argument.
Invoke code generator based on configuration from a yaml configuration file
bin/apibuilder update [--path path]
path defaults to .apibuilder/config in the current directory.
The configuration file is a YAML file that follows the convention:
command:
org:
project:
version: <version>
generators:
<generator name 1>:
target: <path to directory or specific filename>
<generator name 2>:
target: <path to directory or specific filename>
files: <file name or file pattern>
<generator name 3>:
target: <path to directory or specific filename>
files:
- <file name or file pattern>
- <file name or file pattern>
Example File:
code:
apicollective:
apibuilder:
version: latest
generators:
play_2_5_client:
target: generated/app
play_2_x_routes:
target: api/conf/routes
files: apicollective*.*
apibuilder-spec:
version: latest
generators:
play_2_5_client:
target: generated/app
files:
- apicollective*.*
- '*client.rb'
apibuilder-generator:
version: latest
generators:
play_2_5_client: generated/app
Note: Previously the configuration file syntax did not specify any files and instead specified the path as the value of the generator name. While still supported, this syntax is deprecated:
command:
org:
project:
version: <version>
generators:
<generator name>: <path to directory or specific filename>
If the same generator needs to be invoked multiple times for different target directories, the YAML file can have the following alternate syntax:
command:
org:
project:
version: <version>
generators:
- generator: <generator name>:
target: <path 1>
files:
- <file name or file pattern>
- generator: <generator name>:
target: <path 2>
files:
- <file name or file pattern>
In addition, you can specify global settings for how the client behaves:
Example File w/ Settings:
settings:
code.create.directories: true
code:
apicollective:
apibuilder:
version: latest
generators:
play_2_5_client: generated/app
Supported settings include:
- code.create.directories: Defaults to false. If true, when you run
apibuilder update, we will create the subdirectories as specified by the code generator.
Delete versions in ApiBuilder that are not tagged in the source repo.
bin/apibuilder clean <organization key> <application key> [--branch <branch name>] [--silent] [--legacy]
For example:
bin/apibuilder clean apicollective apibuilder-api --branch dev
When using the --silent flag, the suggested versions will be automatically deleted without prompting. This is useful for automated cleanup via git hooks and/or CD pipelines.
If you have versions that use the legacy default naming (i.e. that match the pattern /^.*-\d+-g[0-9a-f]{7}$/) and belong on a non-master branch, use the --legacy flag to interactively move those versions to the proper branch. You only need to run this once, at the point of migrating from the legacy naming to the branch naming. Afterwards, simply run clean without the --legacy flag.
Display the current version of the CLI.
bin/apibuilder cli version
Display the latest available version of the CLI.
bin/apibuilder cli latest
Upgrade to the latest version
bin/apibuilder cli upgrade
PROFILE: Select a specific profile to use, read from the .apibuilder/config
configuration file
APIBUILDER_TOKEN: If specified, this is the apibuilder token we use
To setup a configuration profile, add a section to ~/.apibuilder/config for each profile:
[default]
token = xxx
[profile localhost]
api_uri = http://localhost:9001
token = yyy