---
title: "Policy Management APIs"
slug: "policy-management-apis-1"
updated: 2025-02-27T14:05:37Z
published: 2025-02-27T14:05:37Z
canonical: "docs.plainid.io/policy-management-apis-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plainid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Policy Authoring

## Management APIs for Policy Authoring
Management APIs for Policy Authoring help create, update, and promote Policies to Environments.

PlainID uses **Rego** for Policy as Code (PaC) and **JSON** for Config as Code (CaC) to optimize policy management and follow industry best practices. This approach separates business logic from system configuration, improving maintainability, scalability, and usability.

### Policy Authoring with Rego

**Rego** is a purpose-built language for policy definition, chosen for its expressiveness and compatibility with Open Policy Agent (OPA). Since Policies encapsulate the logic that dictates access control and decision making, using a purpose-built language like Rego provides several advantages, including:
- **Policy as Code (PaC):** Treating policies as code enables version control, peer reviews, and automated deployments. This aligns with modern DevOps practices, ensuring policies are auditable and robust.
- **Standard and Compatibility:** Rego is widely adopted and fully compatible with OPA, simplifying integration and fostering ecosystem support.
- **Expressiveness:** Rego’s design makes it ideal for defining complex policy logic with precision and efficiency.

### Configuration Management with JSON

**JSON** is the format for defining Templates, Applications, Mappers, and other dependencies — elements representing physical configurations rather than business logic. Key features include:

- **Standardization:** JSON is a widely recognized format, making it flexible enough to support different policy languages in the future.
- **Simplicity:** JSON is easy to read, write, and parse, making it ideal for defining data structures.
- **Separation of Concerns:** Keeping configuration separate from policy logic avoids coupling dynamic decision-making with static setups, enhancing clarity and adaptability.

This architecture leverages the strengths of both Rego and JSON, allowing policies and configurations to be easily deployed in OPA and potentially other engines. By adopting this best-practice approach, organizations gain a scalable, flexible, and future-proof policy management solution.



#### Environment Flow Migration
These APIs are designed to automate Policy Management by supporting API requests between different Environments like development, staging, and production:

![image](https://cdn.document360.io/726c7002-05a9-480e-b986-42c9e8824acd/Images/Documentation/a5ad8eb5-ddd2-429e-b20d-fd018575b37e.png){height="" width=""}