For the complete documentation index, see llms.txt. This page is also available as Markdown.

Profiles & regions

A profile is a named set of credentials — a token plus a base URL, plus per-profile defaults. One binary, many accounts.

Profiles live in ~/.celigo/config.json:

{
  "active_profile": "prod",
  "profiles": {
    "prod": {
      "api_token": "abc…xyz",
      "base_url": "https://api.integrator.io",
      "default_format": "table"
    },
    "eu": {
      "api_token": "def…qrs",
      "base_url": "https://api.eu.integrator.io"
    },
    "au": {
      "api_token": "ghi…tuv",
      "base_url": "https://api.au.integrator.io"
    },
    "qa": {
      "api_token": "jkl…wxy",
      "base_url": "https://api.integrator.io",
      "default_format": "json"
    }
  }
}

prod and qa share a base URL because environments do not get their own hostname. Every environment has its own token, so give each one its own profile.

File mode is 0600 on Unix. Tokens are redacted on any CLI output.

Managing profiles

All profile management happens through celigo profile <subcommand>. Full syntax and flags for each subcommand live in the command reference. In short: profile add creates one, profile use switches the active profile, profile list shows them, and profile rename / profile delete rename and delete them.

There is no profile edit. To change a field on an existing profile, either celigo config set <key> <value> against it (see the config command reference) or profile delete + profile add to rebuild it.

Selecting a profile

Regions

Region
API base URL

US

https://api.integrator.io

EU

https://api.eu.integrator.io

AU

https://api.au.integrator.io

CA

https://api.ca.integrator.io

Create one profile per region:

Tokens are not interchangeable — a token from one region authenticating against another region's base URL will return 401 Unauthorized.

See Environments & regions in the API section for the full context.

Per-profile config keys

Field
Typical use

api_token

Bearer token.

base_url

API base URL; defaults to https://api.integrator.io.

default_format

json for CI, table for humans.

mode

Permission mode: read, operate, or full (default).

Edit any of these with --profile <name> config set <key> <value>:

Permission modes

  • full (default) — create/update/set/delete all resources.

  • operate — read + edit a narrow allow-list of fields (disabled, debugUntil, schedule, autoResolveAt). Useful for operational profiles that can pause flows but not change their configuration.

  • read — read only. list, get, account, config, profile are allowed; any mutation is rejected before the request leaves your machine.

A few operations use POST but only read or transform data, so read mode allows them: marketplace browsing, export previews and exports invoke, connection pings, lookup-cache reads, execution-log and EDI transaction queries, signed download URLs, multi-select audit queries, and every processors transform. None of them create, run, or change anything on the account.

CI recipes

GitHub Actions

No profile file needed — pass the env vars.

GitLab CI

Set CELIGO_API_TOKEN as a masked CI variable.

Last updated

Was this helpful?