# CLI reference

### `gitbook auth`

Authenticate the CLI with a GitBook Developer API token. You can generate a personal developer token in your [GitBook Developer settings](https://app.gitbook.com/account/developer).

The token can also be provided using the command line argument `--token=<token>`; If none is provided, it'll be prompted.

### `gitbook new <dir>`

Create and initialize a new integration locally. The program will prompt for information about the integration.

### `gitbook dev`

Create a live connection from your integration to your GitBook editor. Updates made locally while the connection is running will automatically be received in the editor.

See the [development section](https://gitbook-v2-q67etdj25-gitbook.vercel.app/url/gitbook.com/docs/developers/integrations/development) to learn more.

### `gitbook publish`

Publish the integration defined in the `gitbook-manifest.yaml` file. See the [GitBook Manifest reference](https://gitbook-v2-q67etdj25-gitbook.vercel.app/url/gitbook.com/docs/developers/integrations/configurations) documentation to learn more.

See the [publishing section](https://gitbook-v2-q67etdj25-gitbook.vercel.app/url/gitbook.com/docs/developers/integrations/publishing) to learn more about publishing your integration to GitBook.

### `gitbook unpublish <integration-name>`

Unpublish your integration from the GitBook integration platform. Pass the name of the integration as an argument to the command.

### `gitbook whoami`

Print information about the currently authenticated user.

### `gitbook help`

View the GitBook CLI commands and information on using them.

### `gitbook openapi publish <path_to_spec.yaml> --spec <spec_name> --organization <organization_id>`

Publish or update an OpenAPI spec in your organization. Read the docs on [documenting your API in GitBook](https://gitbook.com/docs/api-references/guides/support-for-ci-cd-with-api-blocks) to learn more.