[Human view](https://apicontext.com/features/configuration-as-code) · [Markdown view](https://apicontext.com/features/configuration-as-code.md) · [APIContext home](https://apicontext.com)

# Configuration as Code

Canonical URL: https://apicontext.com/features/configuration-as-code
Source: static

Description: Define, manage, version, and update API monitoring configurations as part of your development workflow, using files your teams can review and change together\.

## Summary
Maintain monitoring in human\-readable YAML or JSON\. Define, manage, version, and update API monitoring configurations as part of your development workflow, using files your teams can review and change together\.

## Stats
- Git ready for version control
- YAML human\-readable monitoring
- CI/CD toolchain friendly
- full program configuration

## Page sections

### Change monitoring with every API change\.
Category: Make monitoring part of development
Configuration as Code lets developers edit application monitoring as part of normal development, keeping checks, schedules, workflows, and alerting aligned with production APIs\.

### Write monitoring in YAML or JSON\.
Category: Human\-readable config
Simplify API monitoring and resilience by letting developers define, manage, and update project configurations in files that are easy to read and review\.

- Define monitoring as YAML or JSON
- Keep configuration readable
- Review monitoring changes like code

### Track, roll back, and collaborate on monitoring changes\.
Category: Version control
Configuration is ready for Git or any version control system, enabling change tracking, rollbacks, collaborative updates, and repeatable project management\.

- Track monitoring changes in Git
- Roll back when needed
- Collaborate across development teams

### Manage calls, workflows, schedules, alerts, projects, and users\.
Category: Full monitoring program
Update API call configuration, workflows, schedules, alerting thresholds, projects, and users from a consistent configuration model\.

- Update API calls and workflows
- Manage schedules and alert thresholds
- Configure projects and users

### Configuration as Code fits Git, CI/CD, project automation, and developer review workflows
Developer workflow: Bring monitoring into the same process as API development\. Readable files: Use YAML or JSON that teams can inspect and review\. Project\-wide config: Cover API calls, workflows, schedules, alerting, projects, and users\. Consistency: Keep monitoring consistent across environments and teams\. CI/CD friendly: Integrate monitoring changes into existing toolchains\. Change visibility: Track rollbacks, reviews, and collaborative updates in version control\.

## Key facts
- YAML
- JSON
- Version control
- CI/CD
- Project export
- Git ready for version control
- YAML human\-readable monitoring
- CI/CD toolchain friendly
- full program configuration
- Developer workflow: Bring monitoring into the same process as API development\.
- Readable files: Use YAML or JSON that teams can inspect and review\.
- Project\-wide config: Cover API calls, workflows, schedules, alerting, projects, and users\.
- Consistency: Keep monitoring consistent across environments and teams\.

## Primary entities
- APIContext
- Features
- API monitoring
- OpenTelemetry
- YAML
- JSON
- Version control
- CI/CD
- Project export

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

## Primary links
- [Put API monitoring under version control\.](/contact)