orriven

Developer tools in a terminal

A single binary for macOS, Linux, and Windows. Authenticate with your console account to manage API keys, webhooks, request logs, and metrics for a Business Unit.

orriven login
orriven init
orriven keys create staging

Single binary. Commands execute in the scope of a configured Business Unit.

Installation

Install the standalone binary and verify the installation with `orriven --version`.

macOS and Linux.

Install via Homebrew tap

brew install orriven/tap/orriven

Authentication

Authenticate using your console account via browser verification. The terminal displays a one-time code for confirmation in the console.

orriven login
  • Sessions match console session lifetimes and can be revoked from Account Settings.
  • Run `orriven whoami` to display the authenticated account and active Business Unit.
  • Run `orriven logout` to terminate the session and remove local credentials.

Verify that the authorization code in the browser matches the code in your terminal before approving access.

Project configuration

Run orriven init to select an organization and Business Unit. The configuration is written to orriven.toml in the project root.

orriven init

Configuration file containing scope only. Contains no credentials.

organization = "…"
workspace = "…"

Specify organization and workspace non-interactively using flags.

orriven init --org acme --workspace "Field Marketing"

Credentials are stored in the user directory. Override scope per command with --workspace and --org, or run orriven init --force to reconfigure. Commands run non-interactively in CI environments.

Command reference

API keys

Manage secret and publishable keys for the selected Business Unit.

  • orriven keys list

    List active keys. Use --all to include revoked keys.

  • orriven keys create <name>

    Generate a secret key. Secret is displayed once. Use --expires-in to set expiration.

  • orriven keys create-publishable <name> --origin https://…

    Generate a publishable key restricted to specific origins.

  • orriven keys revoke <key>

    Revoke an API key immediately.

Webhooks

Configure endpoints, inspect signing secrets, send test events, and view delivery history.

  • orriven webhooks events

    List supported webhook event types.

  • orriven webhooks create --event registration.confirmed

    Register an endpoint and retrieve its signing secret.

  • orriven webhooks ping <id>

    Send a test delivery to verify endpoint connectivity.

  • orriven webhooks deliveries <id>

    View delivery history. Filter by status using --status.

Logs and metrics

Inspect Developer API request logs and traffic metrics for 1, 7, or 30 days.

  • orriven logs

    Display recent API requests. Use --follow for live streaming and --status to filter.

  • orriven logs get --latest --status 5xx

    Retrieve full request and response payloads for a specific request or latest error.

  • orriven metrics --days 7

    View request volume, error rate, and response latency across 1, 7, or 30 days.

Qué no hace

  • Does not manage event inventory, ticket types, or attendee registrations. Use the Developer API with generated keys for event operations.
  • Requires user account authentication. API keys cannot be used to log in to the CLI.
  • For environments without filesystem access or shell execution, use the orriven MCP server.

CLI and MCP

Access the same developer tools across local terminal environments and remote AI agents.

Terminal environments

Use the CLI when a local filesystem and shell are available. Commands execute against the local project configuration.

Remote AI agents

Use the MCP server for remote coding agents without filesystem access. Tools map directly to CLI capabilities over HTTPS.

View MCP documentation

Preguntas

Which roles can use the CLI?
Organization Owners and Admins have permission to manage keys, webhooks, and logs in the CLI. Other roles cannot access developer tools.
How does the CLI relate to the Developer API?
The CLI manages developer infrastructure, including API keys and webhooks. Event and registration data are managed via the Developer API at /v1 using keys issued by the CLI.
How are credentials managed and revoked?
Run `orriven logout` to remove local credentials. Sessions are also listed under Account Settings in the console and can be revoked remotely. CLI sessions expire after seven days of inactivity.

Get started with the CLI

Install the binary to manage API keys, webhooks, and logs directly from your terminal.

Contactar con el equipoView documentation