CLI

Manage your monitoring as code. Update monitoring, manage users, build API call workflows, and keep applications monitored as fast as your team can type.

feature source: static https://apicontext.com/features/cli

CLIdirect project control

3-10API calls in critical workflows

npmdeveloper-native install path

RBACuser and role operations

Build and monitor with the same tools

Keep active projects in sync from your terminal.

The APIContext CLI gives developers a direct connection to API monitoring, so local changes can be pushed into active projects without leaving the development workflow.

Developer-native monitoring

Build and update API monitoring from the CLI.

Use Node.js, npm, or tarballs to connect directly to your monitoring. Manage schedules, API call structures, projects, and alerting without a browser-only workflow.

Install through npm or tarballs
Make updates locally
Push changes into active projects

Advanced workflows

Keep multi-call journeys updated easily.

Critical application workflows often take 3 to 10 API calls. Use call-builder and workflow operations from the CLI to keep monitoring aligned with the journeys your users depend on.

Build multi-call workflows
Manage API call sequences
Keep critical journeys synchronized

Project controls

Manage projects, users, and access from one place.

Manage user access, role management, view/edit operations, new projects, and existing projects with granular controls.

Manage users and roles
Deploy and update projects
Control view/edit operations

CLI workflows fit into developer terminals, project automation, and operational control loops

Monitoring as code: Build and update API monitoring with developer tooling. Workflow operations: Create and manage multi-step API workflows directly from the terminal. Alerting controls: Manage alerting configuration alongside API call structures and schedules. Access management: Control users, roles, and permissions through CLI operations. Fast updates: Push local monitoring changes into active projects quickly. Docs-backed: Use documented operations for project and monitoring administration.

Raw Markdown

Agent-readable source

Browsers get this formatted Agent View. Agents can request the raw source with Accept: text/markdown.

[Human view](https://apicontext.com/features/cli) · [Markdown view](https://apicontext.com/features/cli.md) · [APIContext home](https://apicontext.com)

# CLI

Canonical URL: https://apicontext.com/features/cli
Source: static

Description: Update monitoring, manage users, build API call workflows, and keep applications monitored as fast as your team can type\.

## Summary
Manage your monitoring as code\. Update monitoring, manage users, build API call workflows, and keep applications monitored as fast as your team can type\.

## Stats
- CLI direct project control
- 3\-10 API calls in critical workflows
- npm developer\-native install path
- RBAC user and role operations

## Page sections

### Keep active projects in sync from your terminal\.
Category: Build and monitor with the same tools
The APIContext CLI gives developers a direct connection to API monitoring, so local changes can be pushed into active projects without leaving the development workflow\.

### Build and update API monitoring from the CLI\.
Category: Developer\-native monitoring
Use Node\.js, npm, or tarballs to connect directly to your monitoring\. Manage schedules, API call structures, projects, and alerting without a browser\-only workflow\.

- Install through npm or tarballs
- Make updates locally
- Push changes into active projects

### Keep multi\-call journeys updated easily\.
Category: Advanced workflows
Critical application workflows often take 3 to 10 API calls\. Use call\-builder and workflow operations from the CLI to keep monitoring aligned with the journeys your users depend on\.

- Build multi\-call workflows
- Manage API call sequences
- Keep critical journeys synchronized

### Manage projects, users, and access from one place\.
Category: Project controls
Manage user access, role management, view/edit operations, new projects, and existing projects with granular controls\.

- Manage users and roles
- Deploy and update projects
- Control view/edit operations

### CLI workflows fit into developer terminals, project automation, and operational control loops
Monitoring as code: Build and update API monitoring with developer tooling\. Workflow operations: Create and manage multi\-step API workflows directly from the terminal\. Alerting controls: Manage alerting configuration alongside API call structures and schedules\. Access management: Control users, roles, and permissions through CLI operations\. Fast updates: Push local monitoring changes into active projects quickly\. Docs\-backed: Use documented operations for project and monitoring administration\.

## Key facts
- Node\.js CLI
- npm or tarballs
- Workflow operations
- Project controls
- User management
- CLI direct project control
- 3\-10 API calls in critical workflows
- npm developer\-native install path
- RBAC user and role operations
- Monitoring as code: Build and update API monitoring with developer tooling\.
- Workflow operations: Create and manage multi\-step API workflows directly from the terminal\.
- Alerting controls: Manage alerting configuration alongside API call structures and schedules\.
- Access management: Control users, roles, and permissions through CLI operations\.

## Primary entities
- APIContext
- Features
- API monitoring
- OpenTelemetry
- Node\.js CLI
- npm or tarballs
- Workflow operations
- Project controls
- User management

## Audience
- API teams
- SRE teams
- platform teams

## Primary links
- [Manage API monitoring from the terminal\.](/contact)