canonical: https://jentic.com/apis/swaggerhub.ram.grandhi/wso2-api-manager---admin

# Ram Grandhi WSO2 API Manager - Admin

This document specifies a **RESTful API** for WSO2 **API Manager** - Admin Portal. It is written with [swagger 2](http://swagger.io/). The API exposes 29 endpoints.

## For AI agents

Programmatically upload a global mediation policy, retrieve/search apis
. Covers 29 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Upload a global mediation policy
- Retrieve/Search APIs
- Get a global mediation squence
- Update an mediation policy
- Delete an API
- Add a Blocking condition

## Use cases

### Developer Tools Operations

Use the WSO2 API Manager - Admin to perform developer tools operations programmatically. The API provides 29 endpoints covering core functionality including upload a global mediation policy, retrieve/search apis
, get a global mediation squence.

Example prompt: Call POST `/policies/mediation` to upload a global mediation policy

### Automated Policies Management

Automate policies operations by combining multiple WSO2 API Manager - Admin endpoints. Agents can retrieve/search apis
 and then get a global mediation squence in a single workflow.

Example prompt: Call GET `/policies/mediation` to retrieve/search apis
, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call WSO2 API Manager - Admin endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'upload a global mediation policy', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/policies/mediation` | Upload a global mediation policy |
| GET | `/policies/mediation` | Retrieve/Search APIs |
| GET | `/policies/mediation/{mediationPolicyId}` | Get a global mediation squence |
| PUT | `/policies/mediation/{mediationPolicyId}` | Update an mediation policy |
| DELETE | `/policies/mediation/{mediationPolicyId}` | Delete an API |
| POST | `/throttling/blacklist` | Add a Blocking condition |
| GET | `/throttling/blacklist` | Get all blocking condtions |
| GET | `/throttling/blacklist/{conditionId}` | Retrieve a Blocking Condition |

## Key resources

- **Policies** — Operations for policies
- **Throttling** — Operations for throttling

## Why Jentic

- **Setup:** Wiring the WSO2 API Manager Admin API by hand means pointing at its wso2.com admin host, coding the mediation-policy and throttling calls, and handling retries yourself even though it takes no credential here. Through Jentic you install once, import the WSO2 API Manager Admin API from the API Directory, and your agent calls it.
- **Permission scoping:** This API puts the policy id in the URL path (`/policies/mediation/{mediationPolicyId}`), so a rule can pin your agent to one mediation policy: it can read that policy and nothing else. You choose the operations it may call, so policy deletion is not included unless you add it.
- **Credential handling:** The WSO2 API Manager Admin API needs no credential in this spec, so there is nothing to store, and any host configuration is held by your own Jentic One instance and applied at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'upload a global mediation policy' or 'read a throttling blacklist condition', and Jentic returns the matching WSO2 API Manager Admin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the WSO2 API Manager - Admin use?

The WSO2 API Manager - Admin uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I upload a global mediation policy with the WSO2 API Manager - Admin?

Yes. Use the POST `/policies/mediation` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the WSO2 API Manager - Admin?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I upload a global mediation policy through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'upload a global mediation policy'. Jentic returns the matching WSO2 API Manager - Admin operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the WSO2 API Manager - Admin have?

The WSO2 API Manager - Admin exposes 29 endpoints covering policies, throttling operations.

### Can I limit what my agent is allowed to do with the WSO2 API Manager Admin API?

Yes. Because you run Jentic One yourself, your own rules decide which WSO2 API Manager Admin operations and host configuration the agent may use. Since the API puts the policy id in the URL path at `/policies/mediation/{mediationPolicyId}`, you can pin the agent to reading a single mediation policy while leaving update and delete out of its allowed set. You control the same way for throttling, so the agent can list blocking conditions at `/throttling/blacklist` without being able to add new ones.