> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/administration/security/apis.md).
# APIs
The "APIs Security" enables administrators to manage access to APIs. Only authorized users or roles can view or edit crawled API data. The administrator can view authorized roles and users accessing OvalEdge APIs and grant, deny, or modify access permissions for individual users and roles.
Based on the selected Data Source (Connection Name), the corresponding APIs are displayed along with the governance roles, users, and roles with metadata and data permissions on those APIs.
**API Security: Permissions and Governance**
OvalEdge provides granular control over API access through permission management and governance roles.
**Permissions (SGA & OE\_ADMIN only):**
* **Individual and Bulk Management:** Add, modify, or delete Metadata (view/edit) and Data access permissions for users and roles (including Governance Roles) on single or multiple APIs.
* **Role-Based Access Control:** Based on the license limitations, define the level of Metadata and Data access permissions for specific roles.
* **API Admin:** Assign a role as admin for an API, granting them the highest permissions.
**Governance Roles:**
* **Connector Creation:** Define mandatory Governance roles (Owner, Steward, Custodian) during API connector creation.
* **Updating Governance Roles:** Update Governance roles for individual or multiple APIs (with or without cascading changes to all API attributes).
* **Deleting Role Access:** Remove access permissions assigned to roles on individual or multiple APIs.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/release7.2/administration/security/apis.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
