Visit APIToGo on LinkedIn
  • Documentation
  • Components
  • Themes
Quickstart
CLI
    Install the CLIWalkthrough: from an empty folder to a customer's first callCLI overviewShape with CLIGo live with CLICLI commands
MCP
Configuration
Look and feel
Writing
Guides
Deployment
powered by apitogo
CLI

Go live with CLI

Go live deploys everything in apitogo.config.json to APItoGo: the portal, the gateway, sign-in and plans.

Before you deploy

  1. Sign in to APItoGo once on this computer:

    TerminalCode
    apitogo login

    In CI, set APITOGO_API_KEY_ID and APITOGO_API_SECRET (an API key from the dashboard) instead.

  2. Check the config:

    TerminalCode
    apitogo check

Deploy

TerminalCode
apitogo deploy

On the first run, deploy creates the project: it asks for the hosting plan (Free, Starter or Professional) and writes the project's id into apitogo.config.json. Starter and Professional open the platform's checkout. To create the project without deploying, run apitogo project create --plan <plan>.

Then it sets up each service and prints what it did:

Code
identity: deployed (https://id.apitogo.com/<project>) gateway: deployed (https://<name>.api.apitogo.com/), 12 operation(s) plans: deployed, 2 plans, billing: stripe portal: deployed to production (https://<name>.apitogo.com) Deploy finished.

A step whose input has not changed since the last deploy is skipped. --force runs it anyway.

Secrets deploy asks for

Deploy asks, hidden, for the secrets the config needs and stores them as project secrets:

WhenIt asks for
plans.json has a plan with a priceYour Stripe secret key, then the webhook signing secret
identity.connections has a providerThat provider's client secret, under the name the config gives

Set up Stripe for paid plans shows where the Stripe values are. Set or change a secret yourself with apitogo secrets set <NAME>, and list them with apitogo secrets list.

Selling paid plans and using a custom domain need Starter or Professional. On Free, deploy stops at a paid plan and says so.

One service at a time

TerminalCode
apitogo deploy --only portal apitogo deploy --only gateway,plans

--only takes portal, gateway, identity and plans.

Other flags

FlagPurpose
--forceRedeploy even when nothing changed
--yesConfirm a change that cannot be undone, such as another sign-in provider
--verboseShow the build log and every platform step
--jsonPrint the result as JSON only
--project-idDeploy to this project for this run only

To move the folder to another project for good, use apitogo project use <id> (see Commands).

After deploy

TerminalCode
apitogo status # account, project and live checks apitogo teardown --yes # delete the project and everything in it

Your plans and APItoGo's

KindWhat it isWhere
Hosting planWhat you pay APItoGo: Free, Starter, ProfessionalChosen on the first deploy or project create --plan
Your plansWhat your users pay you for your APIapitogo/plans.json (Plans)

Related

  • Walkthrough
  • Commands
  • Configuration overview
  • MCP go live
Last modified on November 10, 2026
Shape with CLICLI commands
On this page
  • Before you deploy
  • Deploy
  • Secrets deploy asks for
  • One service at a time
  • Other flags
  • After deploy
  • Your plans and APItoGo's
  • Related