Congressio CLI

Run it

npx @congressio/cli events list

https://www.npmjs.com/package/@congressio/cli

Commands

Commands marked with a key need an organization API key. The rest need no credentials at all.

• congressio events list [--all]

  Public conference directory

• congressio events get <slug>

  One public conference

• congressio my events [--all]key

  Your organization's events, drafts included

• congressio submissions list --event <id>key

  Submissions with status and track

• congressio registrations list --event <id>key

  Confirmed registrations

• congressio registrations create --event <id> --name <name> --email <email>key

  Register an attendee (comped — takes no payment)

• congressio docs [slug]

  Documentation as Markdown

• congressio openapi

  The OpenAPI 3.1 document

Options

• --jsonPrint the API response verbatim — for scripts and agents
• --allFollow pagination and return every item
• --retryOn a 429, wait Retry-After and try again
• --api-key <key>Override CONGRESSIO_API_KEY
• --base-url <url>Point at another deployment
• --quietSuppress progress and quota notes

Authentication

Create a key in Organization settings → API, choose its scopes, then export it. The secret is shown once and stored only as a hash — to rotate, create a new key and revoke the old one.

export CONGRESSIO_API_KEY=cong_live_…
congressio my events

Built to be scripted

• ·--json writes the API payload unchanged to stdout, so the OpenAPI schema describes exactly what you get.
• ·Progress, warnings and quota notes go to stderr, so --json output pipes straight into jq.
• ·Exit codes: 0 success, 1 API error, 2 usage error.
• ·It reads the rate-limit headers and, with --retry, waits exactly as long as Retry-After asks.
• ·If an endpoint is ever deprecated, its Deprecation and Sunset headers surface as a warning — a scripted integration hears about it before it breaks.

congressio events list --all --json | jq '.data[] | .slug'

apps/cli